Point the fleet's homebrew tap at the Forgejo mirror via infra config (canonical stays GitHub)

coilysiren commented

2026-07-02 16:17:34 +00:00

Owner

Decision

Kai (2026-07-02, director triage): the homebrew-tap repo lives canonically on GitHub (public + PR-gated, matching the mirror doctrine), but the fleet should install ward from a Forgejo mirror of the tap, configured here in the infrastructure repo - not reach out to github.com at install/build time.

Why

Config-placement law: the tap repo is one thing, but which tap URL the fleet installs from is deployment config, so it lives in the infra layer, not baked and not a GitHub default. It also keeps the fleet build self-consistent - the ward-specs bundle and release assets the formula overlays already resolve from forgejo.coilysiren.me (aos, ward#453), so the tap source should too, taking GitHub off the fleet's runtime/build path.

Scope

A Forgejo mirror of coilyco-flight-deck/homebrew-tap (canonical stays GitHub, the mirror syncs to fj).
infra/ansible config that taps / points brew at the fj mirror URL for the fleet (the rollout, per the authoring-vs-rollout split - the tool is authored in the tap, the fleet-wide pointing is the ansible role).
Confirm the formula's ward-specs resource URL points at the aos Forgejo release asset (already the ward#453 checklist default).

ward#503 (the tap edit itself - the ward-specs resource + overlay, lands canonically on GitHub), ward#453 / ward#441 (the swappable-bundle flip the tap overlays), ward#395 (the same infra-topology-externalization theme).

Filed from the read-only director surface (she/her).

## Decision Kai (2026-07-02, director triage): the `homebrew-tap` repo lives **canonically on GitHub** (public + PR-gated, matching the mirror doctrine), but the **fleet should install `ward` from a Forgejo mirror of the tap, configured here in the infrastructure repo** - not reach out to `github.com` at install/build time. ## Why Config-placement law: the tap **repo** is one thing, but which tap URL the fleet installs from is deployment config, so it lives in the infra layer, not baked and not a GitHub default. It also keeps the fleet build self-consistent - the `ward-specs` bundle and release assets the formula overlays already resolve from `forgejo.coilysiren.me` (aos, ward#453), so the tap source should too, taking GitHub off the fleet's runtime/build path. ## Scope - A Forgejo mirror of `coilyco-flight-deck/homebrew-tap` (canonical stays GitHub, the mirror syncs to fj). - infra/ansible config that taps / points `brew` at the fj mirror URL for the fleet (the rollout, per the authoring-vs-rollout split - the tool is authored in the tap, the fleet-wide pointing is the ansible role). - Confirm the formula's `ward-specs` `resource` URL points at the aos **Forgejo** release asset (already the ward#453 checklist default). ## Related ward#503 (the tap edit itself - the `ward-specs` resource + overlay, lands canonically on GitHub), ward#453 / ward#441 (the swappable-bundle flip the tap overlays), ward#395 (the same infra-topology-externalization theme). Filed from the read-only director surface (she/her).

coilyco-ops commented

2026-07-02 17:59:41 +00:00

Member

🔒 Reserved by ward agent --driver claude — container engineer-claude-infrastructure-440 on host kais-macbook-pro-2.local is carrying this issue (reserved 2026-07-02T17:59:39Z). Concurrent ward agent runs are blocked until it finishes or the reservation goes stale (2h0m0s TTL); --force overrides.

— Claude (she/her), via ward agent

🔒 Reserved by `ward agent --driver claude` — container `engineer-claude-infrastructure-440` on host `kais-macbook-pro-2.local` is carrying this issue (reserved 2026-07-02T17:59:39Z). Concurrent `ward agent` runs are blocked until it finishes or the reservation goes stale (2h0m0s TTL); `--force` overrides.  — Claude (she/her), via `ward agent`

coilysiren referenced this issue from a commit

2026-07-02 18:06:50 +00:00

docs(homebrew): record GitHub-canonical tap installed via Forgejo mirror

coilysiren closed this issue

2026-07-02 18:06:50 +00:00

coilysiren referenced this issue

2026-07-02 18:07:20 +00:00

Establish the Forgejo homebrew-tap as a real pull mirror of the GitHub canonical #443

coilysiren commented

2026-07-02 18:07:39 +00:00

Author

Owner

WARD-OUTCOME: done - infra config already tapped the fj mirror; landed the intent-lock + docs (group_vars headers, docs/ansible-homebrew-role.md, FEATURES.md) and filed #443 for the mirror provisioning.

This one turned out to be mostly archaeology. The literal ask - 'point the fleet's brew tap at the Forgejo mirror URL' - was already true in group_vars/{mac,linux}.yml since June's tap-centralization (6abfae5). What was actually missing was the why: nothing recorded that the tap is GitHub-canonical and the fj URL is a deliberate config-placement choice, so a future edit could 'helpfully' repoint it at github.com. So the real deliverable became locking that intent (header comments) plus a docs section and a FEATURES entry.

The thing that fought back, and the one I'm least comfortable with: the Forgejo homebrew-tap repo is currently mirror: false - a native repo, not a live pull mirror of GitHub. So scope item 1 ('a Forgejo mirror that syncs from GitHub') isn't genuinely satisfied yet, and it can't be from here - Forgejo sets pull-mirroring at migrate time, so it needs a destructive re-migrate on a repo the fleet installs from live. That's an operator wall, so I documented it and filed #443 rather than pull the trigger. Confidence in what landed (config + docs) is high; confidence that the end-to-end design works today is gated on #443.

Two rough edges worth naming: the ward-specs resource confirmation is a no-op until ward#503 lands that overlay (the formula's url/homepage/head already resolve from Forgejo). And pre-commit's pylint hook couldn't run - the container overlay is 100% full so uv can't build its ansible/botocore env - so I skipped just that one hook (diff is YAML+Markdown, zero Python); CI runs it clean.

WARD-OUTCOME: done - infra config already tapped the fj mirror; landed the intent-lock + docs (group_vars headers, docs/ansible-homebrew-role.md, FEATURES.md) and filed #443 for the mirror provisioning. This one turned out to be mostly archaeology. The literal ask - 'point the fleet's brew tap at the Forgejo mirror URL' - was already true in `group_vars/{mac,linux}.yml` since June's tap-centralization (6abfae5). What was actually missing was the *why*: nothing recorded that the tap is GitHub-canonical and the fj URL is a deliberate config-placement choice, so a future edit could 'helpfully' repoint it at github.com. So the real deliverable became locking that intent (header comments) plus a docs section and a FEATURES entry. The thing that fought back, and the one I'm least comfortable with: the Forgejo `homebrew-tap` repo is currently `mirror: false` - a native repo, not a live pull mirror of GitHub. So scope item 1 ('a Forgejo mirror that syncs from GitHub') isn't genuinely satisfied yet, and it can't be from here - Forgejo sets pull-mirroring at migrate time, so it needs a destructive re-migrate on a repo the fleet installs from live. That's an operator wall, so I documented it and filed #443 rather than pull the trigger. Confidence in what landed (config + docs) is high; confidence that the end-to-end design *works today* is gated on #443. Two rough edges worth naming: the ward-specs `resource` confirmation is a no-op until ward#503 lands that overlay (the formula's url/homepage/head already resolve from Forgejo). And pre-commit's pylint hook couldn't run - the container overlay is 100% full so uv can't build its ansible/botocore env - so I skipped just that one hook (diff is YAML+Markdown, zero Python); CI runs it clean.

Rows
Columns

Point the fleet's homebrew tap at the Forgejo mirror via infra config (canonical stays GitHub) #440

Decision

Why

Scope

Related