coilyco-flight-deck/agentic-os

Fork 0

Repoint the release test job off the stale pre-split agentic-os:latest monolith #483

New issue

Closed

opened 2026-07-13 01:23:54 +00:00 by coilyco-ops · 6 comments

coilyco-ops commented

2026-07-13 01:23:54 +00:00

Member

The test job in .forgejo/workflows/release.yml still runs in forgejo.coilysiren.me/coilyco-flight-deck/agentic-os:latest - the frozen pre-tier-split monolith tag, which nothing has published since aos#398. The same stale ref is the job container in ci.yml, dep-bump.yml, promote.yml, mirror-to-github.yml, freshness.yml, and release.yml (three jobs). They keep working (the old tag still resolves) but silently rot.

The publish scheme has since landed as: one agentic-os package, variants as tags (79713d9 restored a moving alias, b719e4f named it for the publishing branch, e6b28c3 dropped the -full suffix). After the next release lands, agentic-os:release and agentic-os:vX.Y.Z exist under the unsuffixed name. Follow-up work:

The agent repoints every workflow job container from agentic-os:latest to forgejo.coilysiren.me/coilyco-flight-deck/agentic-os:release, only after confirming the alias is pullable (chicken-and-egg: the release test job gates the publish that creates the alias, so the swap lands one release behind the scheme change).
The agent sweeps remaining doc references to the old suffixed agentic-os-<tier> names.
Kai or the agent deletes the retired registry leftovers once nothing references them: the suffixed agentic-os-<tier> packages (including any :latest/:release tags the interim v0.248.x-v0.249.x releases pushed) and the stale monolith agentic-os:latest tag.

Related: ward#1139 removes ward's own hardcoded aos image default.

Found while diagnosing ward agent director failing to pull the default image.

The `test` job in `.forgejo/workflows/release.yml` still runs in `forgejo.coilysiren.me/coilyco-flight-deck/agentic-os:latest` - the frozen pre-tier-split monolith tag, which nothing has published since aos#398. The same stale ref is the job container in `ci.yml`, `dep-bump.yml`, `promote.yml`, `mirror-to-github.yml`, `freshness.yml`, and `release.yml` (three jobs). They keep working (the old tag still resolves) but silently rot. The publish scheme has since landed as: one `agentic-os` package, variants as tags (79713d9 restored a moving alias, b719e4f named it for the publishing branch, e6b28c3 dropped the `-full` suffix). After the next release lands, `agentic-os:release` and `agentic-os:vX.Y.Z` exist under the unsuffixed name. Follow-up work: * The agent repoints every workflow job container from `agentic-os:latest` to `forgejo.coilysiren.me/coilyco-flight-deck/agentic-os:release`, only after confirming the alias is pullable (chicken-and-egg: the release test job gates the publish that creates the alias, so the swap lands one release behind the scheme change). * The agent sweeps remaining doc references to the old suffixed `agentic-os-<tier>` names. * Kai or the agent deletes the retired registry leftovers once nothing references them: the suffixed `agentic-os-<tier>` packages (including any `:latest`/`:release` tags the interim v0.248.x-v0.249.x releases pushed) and the stale monolith `agentic-os:latest` tag. Related: ward#1139 removes ward's own hardcoded aos image default. Found while diagnosing `ward agent director` failing to pull the default image.

coilyco-ops added the

headless

labels

2026-07-14 07:44:26 +00:00

coilysiren referenced this issue from coilyco-flight-deck/ward

2026-07-14 15:27:09 +00:00

director should emit colorized, space buffered, visually distinct messages about the categories of actions its performing on startup #1283

coilyco-ops commented

2026-07-15 01:03:50 +00:00

Author

Member

WARDED_WORKFLOW: reservation-held

reservation details

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

Accepted by ward agent --harness codex (reserved 2026-07-15T01:03:49Z). 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#483 · branch issue-483 · harness codex · workflow pull-request-and-merge
Run: engineer-codex-agentic-os-483 · ward v0.693.0 · dispatched 2026-07-15T01:03:41Z
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.693.0).

— Codex, via ward agent

WARDED_WORKFLOW: reservation-held <details><summary>reservation details</summary> Holder: launch intent for container `engineer-codex-agentic-os-483` on host `kais-macbook-pro-2.local`. Accepted by `ward agent --harness codex` (reserved 2026-07-15T01:03:49Z). 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#483` · branch `issue-483` · harness `codex` · workflow `pull-request-and-merge` - **Run:** `engineer-codex-agentic-os-483` · ward `v0.693.0` · dispatched `2026-07-15T01:03:41Z` - **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.693.0). </details> </details>  — Codex, via `ward agent`

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

2026-07-15 01:07:00 +00:00

ci: repoint workflow containers to release alias #542

coilyco-ops commented

2026-07-15 01:08:53 +00:00

Author

Member

WARDED_WORKFLOW: #542

details

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

felt: small and mechanical

confidence: high

surprises: none

follow-ups: none

WARDED_WORKFLOW: https://forgejo.coilysiren.me/coilyco-flight-deck/agentic-os/pulls/542 <details><summary>details</summary> workflow: pull-request-and-merge; review summary: review gate intentionally skipped because the temporary ward default is pending brokered QA felt: small and mechanical confidence: high surprises: none follow-ups: none </details>

coilyco-ops commented

2026-07-15 01:11:24 +00:00

Author

Member

WARDED_WORKFLOW: reservation-held

reservation details

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

Accepted by ward agent --harness codex (reserved 2026-07-15T01:11:23Z). 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.

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

Resolved: coilyco-flight-deck/agentic-os#483 · branch issue-483 · harness codex · workflow pull-request-and-merge
Run: engineer-codex-agentic-os-483 · ward v0.693.0 · dispatched 2026-07-15T01:11:10Z
Comment thread: 1 included in the pre-flight read, 1 stripped (ward's own automated comments).
- included: @coilyco-ops (2026-07-15T01:08:53Z)
- stripped: @coilyco-ops (2026-07-15T01:03:50Z)

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

— Codex, via ward agent

WARDED_WORKFLOW: reservation-held <details><summary>reservation details</summary> Holder: launch intent for container `engineer-codex-agentic-os-483` on host `kais-macbook-pro-2.local`. Accepted by `ward agent --harness codex` (reserved 2026-07-15T01:11:23Z). 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#483` · branch `issue-483` · harness `codex` · workflow `pull-request-and-merge` - **Run:** `engineer-codex-agentic-os-483` · ward `v0.693.0` · dispatched `2026-07-15T01:11:10Z` - **Comment thread:** 1 included in the pre-flight read, 1 stripped (ward's own automated comments). - included: @coilyco-ops (2026-07-15T01:08:53Z) - stripped: @coilyco-ops (2026-07-15T01:03:50Z) Static container doctrine and seed boilerplate are identical every run and omitted here (they ride ward v0.693.0). </details> </details>  — Codex, via `ward agent`

coilyco-ops commented

2026-07-15 01:15:27 +00:00

Author

Member

WARDED_WORKFLOW: #542

details

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

felt: small and mechanical

confidence: high

surprises: none

follow-ups: none

coilyco-ops commented

2026-07-15 03:07:30 +00:00

Author

Member

WARDED_WORKFLOW: reservation-held

reservation details

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

Accepted by ward agent --harness codex (reserved 2026-07-15T03:07:29Z). 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.

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

Resolved: coilyco-flight-deck/agentic-os#483 · branch issue-483 · harness codex · workflow pull-request-and-merge
Run: engineer-codex-agentic-os-483 · ward v0.695.0 · dispatched 2026-07-15T03:07:18Z
Comment thread: 2 included in the pre-flight read, 2 stripped (ward's own automated comments).
- included: @coilyco-ops (2026-07-15T01:08:53Z), @coilyco-ops (2026-07-15T01:15:27Z)
- stripped: @coilyco-ops (2026-07-15T01:03:50Z), @coilyco-ops (2026-07-15T01:11:24Z)

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

— Codex, via ward agent

WARDED_WORKFLOW: reservation-held <details><summary>reservation details</summary> Holder: launch intent for container `engineer-codex-agentic-os-483` on host `kais-macbook-pro-2.local`. Accepted by `ward agent --harness codex` (reserved 2026-07-15T03:07:29Z). 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#483` · branch `issue-483` · harness `codex` · workflow `pull-request-and-merge` - **Run:** `engineer-codex-agentic-os-483` · ward `v0.695.0` · dispatched `2026-07-15T03:07:18Z` - **Comment thread:** 2 included in the pre-flight read, 2 stripped (ward's own automated comments). - included: @coilyco-ops (2026-07-15T01:08:53Z), @coilyco-ops (2026-07-15T01:15:27Z) - stripped: @coilyco-ops (2026-07-15T01:03:50Z), @coilyco-ops (2026-07-15T01:11:24Z) Static container doctrine and seed boilerplate are identical every run and omitted here (they ride ward v0.695.0). </details> </details>  — Codex, via `ward agent`

coilyco-ops commented

2026-07-15 03:11:31 +00:00

Author

Member

WARDED_WORKFLOW: #542

details

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

felt: small and mechanical

confidence: high

surprises: none

follow-ups: none

coilyco-ops closed this issue