feat(forgejo): promote runner-token fetch overlay #537
No reviewers
Labels
No labels
burndown-2026-06
burndown-2026-08
autonomy
async-consult
autonomy
epic
autonomy
headless
autonomy
live-collab
coherence-core
priority
P0
priority
P1
priority
P2
priority
P3
priority
P4
qa-fixture
role/advocate
role/director
role/exec
role/frontend
role/gamedev
role/human
role/platform
role/qa
role/science
role/sysadmin
state
ambient
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
coilyco-flight-deck/agentic-os!537
Loading…
Reference in a new issue
No description provided.
Delete branch "issue-453-pr"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Replace the runner-token mint path with declarative fetch overlays and keep the scope router thin. This removes the raw curl surface from the guarded path while preserving the existing
ward ops forgejo actions generate-runner-tokenentrypoint.ward exec test -- tests/test_forgejo_runner_token.py tests/test_forgejo_actions_list_bridge.py tests/test_forgejo_actions_logs.py tests/test_release_actions.py.closes #453
ward.workflow: pull-request-and-merge
WARDED_WORKFLOW: #537
details
workflow: pull-request-and-merge; review summary: passed
head sha:
9f12c4033dreview gate intentionally skipped because the temporary ward default was pending brokered QA.