coilyco-flight-deck/agentic-os

Watch

Parallelize dev-base release publishing by image tier #386

New issue

Closed

opened 2026-07-09 19:50:27 +00:00 by coilyco-ops · 2 comments

coilyco-ops commented

2026-07-09 19:50:27 +00:00

Member

Derived from issue #377 and docs/dev-base-image-tiering.md.\n\nScope: update .forgejo/workflows/release.yml so core publishes first, the independent tier targets publish in parallel, and dev-base-full fans in only after prerequisites pass. Keep one repo release tag across all image refs and keep smoke checks per target.\n\nDo not change app rollout files in this slice.

coilyco-ops commented

2026-07-09 21:33:52 +00:00

Author

Member

WARD-RESERVATION: held 🔒

reservation details

Holder: container engineer-codex-agentic-os-386 on host kais-macbook-pro-2.local.

Reserved by ward agent --harness codex (reserved 2026-07-09T21:33:49Z). Concurrent ward agent runs are blocked until it finishes or the reservation goes stale (1h TTL). --force 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#386 · branch issue-386 · harness codex · workflow direct-to-main
Run: engineer-codex-agentic-os-386 · ward v0.493.0 · dispatched 2026-07-09T21:33:49Z
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.493.0).

— Codex, via ward agent

WARD-RESERVATION: held 🔒 <details><summary>reservation details</summary> Holder: container `engineer-codex-agentic-os-386` on host `kais-macbook-pro-2.local`. Reserved by `ward agent --harness codex` (reserved 2026-07-09T21:33:49Z). Concurrent `ward agent` runs are blocked until it finishes or the reservation goes stale (1h TTL). `--force` 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#386` · branch `issue-386` · harness `codex` · workflow `direct-to-main` - **Run:** `engineer-codex-agentic-os-386` · ward `v0.493.0` · dispatched `2026-07-09T21:33:49Z` - **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.493.0). </details> </details>  — Codex, via `ward agent`

coilyco-ops added the

priority

autonomy

headless

labels

2026-07-09 21:41:57 +00:00

coilyco-ops referenced this issue from a commit

2026-07-09 21:56:17 +00:00

feat(release): fan out dev-base publishing by tier

coilyco-ops closed this issue

2026-07-09 21:56:17 +00:00

coilyco-ops commented

2026-07-09 21:56:54 +00:00

Author

Member

WARD-OUTCOME: done ✅

details

workflow: direct-to-main; review summary: skipped by ~/.ward/config.yaml default
felt: merge-heavy, then straightforward
confidence: high
surprises: origin/main moved and the docs size caps needed a second pass
follow-ups: none

WARD-OUTCOME: done ✅ <details><summary>details</summary> workflow: direct-to-main; review summary: skipped by ~/.ward/config.yaml default felt: merge-heavy, then straightforward confidence: high surprises: origin/main moved and the docs size caps needed a second pass follow-ups: none </details>

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

coilyco-flight-deck/agentic-os#386

No description provided.

Rows
Columns