Add Homebrew to the AOS dev-base image #379

New issue

Closed

opened 2026-07-09 17:43:01 +00:00 by coilyco-ops · 3 comments

coilyco-ops commented

2026-07-09 17:43:01 +00:00

Member

coilyco-flight-deck/homebrew-tap#5 is blocked because the pinned agentic-os dev-base image still does not include Homebrew. The tap CI currently falls back to Ruby syntax checks across Formula/*.rb; it should be able to run the real tap audit through ward once brew is available in dev-base.

Add Linux Homebrew to the AOS dev-base image so repos can use Homebrew audit/test commands inside Forgejo Actions.

Acceptance:

docker/dev-base/Dockerfile installs Homebrew for both supported build architectures, or documents a bounded reason for an architecture exception.
brew --version runs during the image build as a smoke check.
The install does not require interactive shell setup at runtime.
Image docs mention Homebrew as part of the dev-base tooling.
A landed commit closes this issue and lets the release workflow publish the next dev-base tag.

Follow-up after this lands: restore coilyco-flight-deck/homebrew-tap#5 from Ruby syntax checks to the real ward/homebrew audit path.

`coilyco-flight-deck/homebrew-tap#5` is blocked because the pinned agentic-os dev-base image still does not include Homebrew. The tap CI currently falls back to Ruby syntax checks across `Formula/*.rb`; it should be able to run the real tap audit through ward once `brew` is available in dev-base. Add Linux Homebrew to the AOS dev-base image so repos can use Homebrew audit/test commands inside Forgejo Actions. Acceptance: * `docker/dev-base/Dockerfile` installs Homebrew for both supported build architectures, or documents a bounded reason for an architecture exception. * `brew --version` runs during the image build as a smoke check. * The install does not require interactive shell setup at runtime. * Image docs mention Homebrew as part of the dev-base tooling. * A landed commit closes this issue and lets the release workflow publish the next dev-base tag. Follow-up after this lands: restore `coilyco-flight-deck/homebrew-tap#5` from Ruby syntax checks to the real ward/homebrew audit path.

coilyco-ops commented

2026-07-09 17:43:14 +00:00

Author

Member

WARD-RESERVATION: held 🔒

reservation details

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

Reserved by ward agent --harness codex (reserved 2026-07-09T17:43:12Z). 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#379 · branch issue-379 · harness codex · workflow direct-to-main
Run: engineer-codex-agentic-os-379 · ward v0.493.0 · dispatched 2026-07-09T17:43:12Z
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-379` on host `kais-macbook-pro-2.local`. Reserved by `ward agent --harness codex` (reserved 2026-07-09T17:43:12Z). 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#379` · branch `issue-379` · harness `codex` · workflow `direct-to-main` - **Run:** `engineer-codex-agentic-os-379` · ward `v0.493.0` · dispatched `2026-07-09T17:43:12Z` - **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 from coilyco-flight-deck/homebrew-tap

2026-07-09 17:43:15 +00:00

Restore tap audit CI once dev-base includes Homebrew #5

coilyco-ops referenced this issue from a commit

2026-07-09 17:48:39 +00:00

feat: add Homebrew to dev-base image

coilyco-ops closed this issue

2026-07-09 17:48:39 +00:00

coilyco-ops commented

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

Author

Member

WARD-OUTCOME: done ✅

details

workflow: direct-to-main; review summary: skipped because review gate skipped by ~/.ward/config.yaml default

The implementation felt straightforward once the Homebrew install was folded into the existing dev-base layer. Confidence is high. Surprise: the dev-base image doc needed a second trim to stay under the documentation cap after the Homebrew note landed. Follow-up: restore coilyco-flight-deck/homebrew-tap#5 to the real ward/homebrew audit path.

WARD-OUTCOME: done ✅ <details><summary>details</summary> workflow: direct-to-main; review summary: skipped because review gate skipped by ~/.ward/config.yaml default The implementation felt straightforward once the Homebrew install was folded into the existing dev-base layer. Confidence is high. Surprise: the dev-base image doc needed a second trim to stay under the documentation cap after the Homebrew note landed. Follow-up: restore `coilyco-flight-deck/homebrew-tap#5` to the real ward/homebrew audit path. </details>

coilyco-ops commented

2026-07-09 17:49:20 +00:00

Author

Member

WARD-OUTCOME: done ✅

details

workflow: direct-to-main; review summary: skipped because review gate skipped by ~/.ward/config.yaml default