Expose publish-core breadcrumbs outside raw Forgejo logs #586

New issue

Closed

opened 2026-07-15 11:46:07 +00:00 by coilyco-ops · 2 comments

coilyco-ops commented

2026-07-15 11:46:07 +00:00

Member

After #585 landed, the release run still failed and the breadcrumbs were not visible from the director surface.

Current head:

main and release: 83b6cc2a53b1926e695d064ecf7fbe738d6f62eb (fix(dev-base): add core publish breadcrumbs (#585)).

Failure evidence:

dev-base-publish.yml run 1429 failed.
plan-draft succeeded.
publish-core failed.
Downstream publish tiers stayed blocked.
publish-core job index 1 failed in ./actions/publish-dev-base-tier after 14m29s.
The static Forgejo job page still only shows the step summaries, not the new breadcrumbs.
Raw log helper still fails: ward ops forgejo actions logs coilyco-flight-deck agentic-os 8500 14228 1 returns 404.

The previous breadcrumb patch did not satisfy the director-side need: after a failed release, the failure reason must be visible without raw Forgejo logs. The engineer should either fix the core publish failure directly if the cause is clear, or publish the core-tier failure context to a surface the director can read, such as a short artifact, job summary file if supported, or a deterministic committed/printed status file exposed by the workflow summary. Keep this targeted to publish-core and ./actions/publish-dev-base-tier.

Acceptance:

A failed publish-core run exposes the specific failing operation and exit cause from the director-readable run page or artifact listing, without relying on raw logs.
If the root cause is repo-side, fix it instead of only improving evidence.
PR CI is green.
After merge, run dev-base-publish.yml again and confirm either publish-core passes or the visible failure names the exact external wall.

After #585 landed, the release run still failed and the breadcrumbs were not visible from the director surface. Current head: * `main` and `release`: `83b6cc2a53b1926e695d064ecf7fbe738d6f62eb` (`fix(dev-base): add core publish breadcrumbs (#585)`). Failure evidence: * `dev-base-publish.yml` run `1429` failed. * `plan-draft` succeeded. * `publish-core` failed. * Downstream publish tiers stayed blocked. * `publish-core` job index 1 failed in `./actions/publish-dev-base-tier` after 14m29s. * The static Forgejo job page still only shows the step summaries, not the new breadcrumbs. * Raw log helper still fails: `ward ops forgejo actions logs coilyco-flight-deck agentic-os 8500 14228 1` returns 404. The previous breadcrumb patch did not satisfy the director-side need: after a failed release, the failure reason must be visible without raw Forgejo logs. The engineer should either fix the core publish failure directly if the cause is clear, or publish the core-tier failure context to a surface the director can read, such as a short artifact, job summary file if supported, or a deterministic committed/printed status file exposed by the workflow summary. Keep this targeted to `publish-core` and `./actions/publish-dev-base-tier`. Acceptance: * A failed `publish-core` run exposes the specific failing operation and exit cause from the director-readable run page or artifact listing, without relying on raw logs. * If the root cause is repo-side, fix it instead of only improving evidence. * PR CI is green. * After merge, run `dev-base-publish.yml` again and confirm either `publish-core` passes or the visible failure names the exact external wall.

coilyco-ops commented

2026-07-15 11:46:29 +00:00

Author

Member

WARDED_WORKFLOW: reservation-held

reservation details

Holder: launch intent for container engineer-codex-agentic-os-586 on host kais-macbook-pro-2.local.

Accepted by ward agent --harness codex (reserved 2026-07-15T11:46:28Z). Concurrent ward agent runs are blocked until this intent becomes visible or the intent is released. The stale-intent fallback is still TTL-bounded (3h TTL). --override-reservation overrides.

Do not comment on or edit this issue to steer the run while it is reserved. The engineer seeded the body once at launch and never re-reads it, so a comment or edit reaches only human readers, never the running engineer. A correction goes to a new issue, dispatched fresh. That is the only channel that reaches a run in flight. Where the forge supports it, ward locks this conversation to make that a road-block rather than a convention (ward#494).

run seed context — what this run is carrying (ward#609)

Resolved: coilyco-flight-deck/agentic-os#586 · branch issue-586 · harness codex · workflow pull-request-and-merge
Run: engineer-codex-agentic-os-586 · ward v0.697.0 · dispatched 2026-07-15T11:46:23Z
Comment thread: 0 included in the pre-flight read, 0 stripped (ward's own automated comments).

Static container doctrine and seed boilerplate are identical every run and omitted here (they ride ward v0.697.0).

— Codex, via ward agent

WARDED_WORKFLOW: reservation-held <details><summary>reservation details</summary> Holder: launch intent for container `engineer-codex-agentic-os-586` on host `kais-macbook-pro-2.local`. Accepted by `ward agent --harness codex` (reserved 2026-07-15T11:46:28Z). Concurrent `ward agent` runs are blocked until this intent becomes visible or the intent is released. The stale-intent fallback is still TTL-bounded (3h TTL). `--override-reservation` overrides. **Do not comment on or edit this issue to steer the run while it is reserved.** The engineer seeded the body once at launch and never re-reads it, so a comment or edit reaches only human readers, never the running engineer. A correction goes to a **new issue, dispatched fresh**. That is the only channel that reaches a run in flight. Where the forge supports it, ward locks this conversation to make that a road-block rather than a convention (ward#494). <details><summary>run seed context — what this run is carrying (ward#609)</summary> - **Resolved:** `coilyco-flight-deck/agentic-os#586` · branch `issue-586` · harness `codex` · workflow `pull-request-and-merge` - **Run:** `engineer-codex-agentic-os-586` · ward `v0.697.0` · dispatched `2026-07-15T11:46:23Z` - **Comment thread:** 0 included in the pre-flight read, 0 stripped (ward's own automated comments). Static container doctrine and seed boilerplate are identical every run and omitted here (they ride ward v0.697.0). </details> </details>  — Codex, via `ward agent`

coilyco-ops referenced this issue from a pull request that will close it,

2026-07-15 11:54:50 +00:00

fix(dev-base): expose core publish breadcrumbs in summary #587

coilyco-ops closed this issue

2026-07-15 11:57:41 +00:00

coilyco-ops commented

2026-07-15 11:58:37 +00:00

Author

Member

WARDED_WORKFLOW: #587

details

workflow: pull-request-and-merge; review summary: review gate intentionally skipped because the temporary ward default pending brokered QA

Implementation felt straightforward after tracing the summary surface. Confidence is high. Surprise was only that the visible breadcrumb needed both the script summary write and the shell failure synopsis. Follow-up is the director merge and the post-merge dev-base publish rerun.

WARDED_WORKFLOW: https://forgejo.coilysiren.me/coilyco-flight-deck/agentic-os/pulls/587 <details><summary>details</summary> workflow: pull-request-and-merge; review summary: review gate intentionally skipped because the temporary ward default pending brokered QA Implementation felt straightforward after tracing the summary surface. Confidence is high. Surprise was only that the visible breadcrumb needed both the script summary write and the shell failure synopsis. Follow-up is the director merge and the post-merge dev-base publish rerun. </details>

coilyco-ops referenced this issue

2026-07-15 12:25:19 +00:00

Expose the actual publish-core failure after summary patch #588