fix(w8): accept Forgejo dispatch event shape #515

Merged
pdurlej merged 1 commit from codex/w8-uptime-kuma-runtime-dispatch-fix into main 2026-05-27 08:59:33 +02:00
Collaborator

Canary status: missing — fire canary 3+3 manually before merge

Canary Context Pack

Product story

The W8 uptime-kuma runtime pilot workflow merged in #514, but Forgejo records manual dispatch runs with an empty run event in the Actions API. The workflow failed before touching runtime because it required github.event_name == workflow_dispatch.

What changed

Removed only that redundant event-name assertion. The remaining gates stay intact: trusted main, exact operator approval phrase, exact target image, and deploy-ready runner.

Why it changed

The workflow is already only declared on workflow_dispatch, so the event-name shell assertion is not the security boundary. It was incompatible with this Forgejo dispatch shape.

Files touched

  • .forgejo/workflows/w8-uptime-kuma-runtime-pilot.yml

Relevant context

  • Failed run #3044 stopped in 3s before runtime mutation.
  • Run metadata: workflow w8-uptime-kuma-runtime-pilot.yml, commit 6ba8d3b..., status failure, event empty.

Runtime evidence

No runtime mutation. The failed workflow never reached backup/recreate/smoke steps.

Known constraints

The workflow remains fixed to uptime-kuma and louislam/uptime-kuma:2.3.2.

Explicit out-of-scope

No runtime apply, no service restart, no broader workflow generalization.

Requested decision

Merge so the approved W8 runtime pilot can be dispatched again.

Merge blockers

Any widening beyond removing the incompatible event-name assertion.

Spec sources read

  • .forgejo/workflows/w8-uptime-kuma-runtime-pilot.yml — failed workflow gate.
  • Forgejo Actions run #3044 metadata via API — failure happened before runtime mutation.
Canary status: missing — fire canary 3+3 manually before merge ## Canary Context Pack ### Product story The W8 uptime-kuma runtime pilot workflow merged in #514, but Forgejo records manual dispatch runs with an empty run event in the Actions API. The workflow failed before touching runtime because it required `github.event_name == workflow_dispatch`. ### What changed Removed only that redundant event-name assertion. The remaining gates stay intact: trusted `main`, exact operator approval phrase, exact target image, and deploy-ready runner. ### Why it changed The workflow is already only declared on `workflow_dispatch`, so the event-name shell assertion is not the security boundary. It was incompatible with this Forgejo dispatch shape. ### Files touched - `.forgejo/workflows/w8-uptime-kuma-runtime-pilot.yml` ### Relevant context - Failed run #3044 stopped in 3s before runtime mutation. - Run metadata: workflow `w8-uptime-kuma-runtime-pilot.yml`, commit `6ba8d3b...`, status `failure`, event empty. ### Runtime evidence No runtime mutation. The failed workflow never reached backup/recreate/smoke steps. ### Known constraints The workflow remains fixed to `uptime-kuma` and `louislam/uptime-kuma:2.3.2`. ### Explicit out-of-scope No runtime apply, no service restart, no broader workflow generalization. ### Requested decision Merge so the approved W8 runtime pilot can be dispatched again. ### Merge blockers Any widening beyond removing the incompatible event-name assertion. ## Spec sources read - `.forgejo/workflows/w8-uptime-kuma-runtime-pilot.yml` — failed workflow gate. - Forgejo Actions run #3044 metadata via API — failure happened before runtime mutation.
fix(w8): accept Forgejo dispatch event shape
Some checks failed
base-is-main / guard (pull_request) Successful in 1s
canary-required / collect-diff (pull_request) Successful in 5s
infra-docs-drift / docs-drift (pull_request) Successful in 5s
patchwarden-client-dry-run / collect-diff (pull_request) Successful in 4s
patchwarden-pr-sanity / collect-diff (pull_request) Successful in 3s
workflow-lint / lint (pull_request) Successful in 5s
canary-required / canary (pull_request) Successful in 14s
patchwarden-client-dry-run / dry-run (pull_request) Successful in 21s
patchwarden-pr-sanity / sanity (pull_request) Failing after 23s
70c11c5e29
Sign in to join this conversation.
No reviewers
No labels
W6d-automerge-calibration
agent/claude-code
agent/codex
agent/hermes
agent/iskra
agent/ollama
agent/patchwarden
automerge-candidate
class/security-sensitive
cutover-gate
dependency/blocked
dependency/blocks-others
dependency/cross-repo
dependency/needs-confirmation
domain:agents
domain:ci
domain:docs
domain:forgejo
domain:infra
domain:memory
domain:runtime
domain:signal
domain:ux
flow/architecture
flow/blocked
flow/deployed
flow/done
flow/implementation
flow/intake
flow/maintained
flow/observed
flow/ready
flow/refining
flow/retired
flow/review
iterating
judge/codex-candidate
judge/hermes-candidate
judge/low-confidence
judge/needs-refinement
judge/operator-needed
judge/p0
judge/p1
judge/p2
judge/p3
judge/park
judge/patchwarden-candidate
judge/stale-priority
kind/adr
kind/bug
kind/chore
kind/feature
kind/infra
kind/ops
kind/refactor
kind/research
large-impact
merge/auto
merge/manual
merge/manual-dependency-conflict
merge/manual-failing-tests
merge/manual-merge-conflict
merge/manual-missing-review
merge/manual-operator-preference
merge/manual-red-zone
merge/manual-security-sensitive
merge/manual-unclear-scope
merge/manual-unknown
meta
mode:operator-only
mode:patchwarden-iskra-approved
mode:safe-auto
needs-operator-decision
needs-triage
not-ready
observed/erroring
observed/needs-followup
observed/pending
observed/retire-candidate
observed/unused
observed/used
operator-emotional
owner-attention
phase/02
phase/03
priority:p0
priority:p1
priority:p2
priority:p3
proposed
ready-for-agent
ready-for-operator
recovery
review:claude-reviewed
review:codex-reviewed
review:dziadek-reviewed
review:needs-human
risk/exposure
risk/process
risk/product
risk/runtime
safety:external-write
safety:no-prod-mutation
safety:prod-impact
safety:secret-touch
size/large
size/medium
size/small
size/tiny
size/unknown
source/adr
source/agent-generated
source/manual
source/operator-chat
source/voice-note
status:blocked
status:codex-ready
status:merged:pending-evidence
status:needs-evidence
status:operator-needed
status:parked
tier/full
tier/lite
tier/stacked
tier:0-platform-substrate
tier:1-iskra-value-layer
tier:2-tools-products-modules
type:bug
type:chore
type:docs
type:feat
type:policy
type:research
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
pdurlej/platform!515
No description provided.