coilyco-flight-deck/agentic-os

Watch

Split dev-base into named image targets and a builder stage #385

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: refactor docker/dev-base/Dockerfile into named targets for core, lang-node, lang-go, lang-dotnet, ops, agent, and full, while keeping the published default behavior on dev-base-full. Use a builder stage for ward and any other build-only binaries so runtime tiers stay narrower.\n\nDo not change downstream consumers in this slice.

coilyco-ops commented

2026-07-09 20:27:26 +00:00

Author

Member

WARD-RESERVATION: held 🔒

reservation details

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

Reserved by ward agent --harness codex (reserved 2026-07-09T20:27:24Z). 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#385 · branch issue-385 · harness codex · workflow direct-to-main
Run: engineer-codex-agentic-os-385 · ward v0.493.0 · dispatched 2026-07-09T20:27:24Z
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-385` on host `kais-macbook-pro-2.local`. Reserved by `ward agent --harness codex` (reserved 2026-07-09T20:27:24Z). 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#385` · branch `issue-385` · harness `codex` · workflow `direct-to-main` - **Run:** `engineer-codex-agentic-os-385` · ward `v0.493.0` · dispatched `2026-07-09T20:27:24Z` - **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 referenced this issue

2026-07-09 20:36:38 +00:00

Bump dev-base ward to a config-ref capable release #390

coilyco-ops referenced this issue from a commit

2026-07-09 20:45:26 +00:00

refactor(dev-base): split named targets and builder stage

coilyco-ops closed this issue

2026-07-09 20:45:26 +00:00

coilyco-ops commented

2026-07-09 20:46:07 +00:00

Author

Member

WARD-OUTCOME: done ✅

details

workflow: direct-to-main; review summary: skipped (review gate skipped by ~/.ward/config.yaml default) felt: the stage split was straightforward, but the container temp-space ceiling blocked full pre-commit and commit-hook installs. confidence: high on the Dockerfile refactor, medium on the unverifiable full hook suite in this container. surprises: the fresh hook caches still hit no-space errors in Go and Python hook environments. follow-ups: none for this slice.

WARD-OUTCOME: done ✅ <details><summary>details</summary> workflow: direct-to-main; review summary: skipped (review gate skipped by ~/.ward/config.yaml default) felt: the stage split was straightforward, but the container temp-space ceiling blocked full pre-commit and commit-hook installs. confidence: high on the Dockerfile refactor, medium on the unverifiable full hook suite in this container. surprises: the fresh hook caches still hit no-space errors in Go and Python hook environments. follow-ups: none for this slice. </details>

coilyco-ops referenced this issue

2026-07-09 20:51:47 +00:00

Fix dev-base publish-image failure after ward v0.529.0 and tier split #391

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#385

No description provided.

Rows
Columns