Blocker: o2r Actions not dispatching + CI_RELEASE_TOKEN missing for flight-deck #9
Labels
No labels
burndown-2026-06
coherence-core
consult
headless
interactive
P0
P1
P2
P3
P4
No milestone
No project
No assignees
1 participant
No due date set.
Dependencies
No dependencies set.
Reference
coilyco-flight-deck/otel-a2a-relay-cli#9
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
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?
Blocker: o2r release pipeline merged but not firing
.forgejo/workflows/release.ymllanded on main (5413cc7, #3) but the push produced zero Actions tasks (coily ops forgejo actions task list --repo coilyco-flight-deck/otel-a2a-relay-cli-> no tasks). The flight-deck runner is healthy - coilyco-flight-deck/repo-recall and coilyco-bridge/coily both have recent task history - so this is o2r-specific. The repo was created 2026-06-02 and has never dispatched a run.Likely a runner-scope / first-run provisioning gap on this brand-new repo. coily exposes no runner-management verb, so this needs a look at the forgejo Actions runner config on kai-server (org vs repo scope, whether o2r is in scope).
Confirmed adjacent gap: CI_RELEASE_TOKEN missing for flight-deck
repo-recall's
bump-formulajob fails withHTTP 401: {"message":"token is required"}(task 245 log). The cross-repo formula bump needsCI_RELEASE_TOKENprovisioned as a secret for coilyco-flight-deck repos. o2r's #3 pipeline does not use it (release + assets only). The unblocked consumer is #14, the cross-repo precompiled-formula bump action - it is what readsCI_RELEASE_TOKENto commit the bumped formula into the monorepo tap. #6 wires #14 into the o2r pipeline, so provision the token before #14 runs. Once provisioned it also clears repo-recall's existingbump-formula401.To do
CI_RELEASE_TOKENfor coilyco-flight-deck repos (unblocks #14's cross-repo bump and repo-recall's existing bump-formula).Relates to coilysiren/inbox#28 (GitHub mirror + secrets). Blocks #14 (and therefore #6). Part of the o2r packaging epic (#5).
Reopening: the matrix fix (
12d0419) did not resolve this.I'd hypothesized o2r's include-only matrix expanded to zero jobs (a real Forgejo behavior - it can silently create no task and log only server-side). Fixed it to a base
goos x goarchcross product, valid YAML, now on main. Re-polled the task list three times: still (no tasks).So the YAML was a red herring. o2r dispatches no Actions at all - not a workflow-parse issue, a repo-level enablement / runner-scope gap on this 2026-06-02-created repo. The runner itself is healthy (repo-recall + coily both have task history).
The matrix fix stays (it's still the correct shape and matches coily/repo-recall), but it does not unblock dispatch.
Next: investigate the forgejo runner/Actions scope for this repo on kai-server - routed via o2r per Kai's steer, not raw ssh. CI_RELEASE_TOKEN gap (repo-recall 401) still stands for #6.
Update:
CI_RELEASE_TOKENprovisioned (one of two to-dos cleared).Set as an org-level Actions secret on
coilyco-flight-deck(PUT /api/v1/orgs/coilyco-flight-deck/actions/secrets/CI_RELEASE_TOKEN, HTTP 204, verified present). Org-level means o2r, repo-recall, ward, and every future flight-deck tool inherit it - no per-repo duplication. Awrite:repository-scoped Forgejo PAT is the value; a copy is stashed at SSM/forgejo/ci-release-tokenas the rotation source of truth (documented in agentic-os-kai SSM.md).This unblocks #14's cross-repo bump and clears repo-recall's existing
bump-formula401.Still open: the runner-scope half - o2r dispatches zero Actions runs (runner registration check on kai-server). That gates actually exercising the token end to end.
Closing. o2r is archived in the June 2026 surface reduction - an optional agent channel, unused autonomously. Handover doctrine moves to human-mediated.