packaging: add the warded -> ward symlink to the tap formula #277

New issue

Closed

opened 2026-06-24 08:52:14 +00:00 by coilysiren · 2 comments

coilysiren commented

2026-06-24 08:52:14 +00:00

Owner

Follow-up from ward#247 (shipped in dfa5610). The warded public-face shim works in two of three install paths:

In-binary: main.go rewrites argv when invoked as warded -> ward drive <args> (the multicall, not a second code path).
Container: the entrypoint symlinks warded -> ward next to the installed binary, so the launch demo runs warded claude "..." with no extra step.
Host brew install (this follow-up): the centralized tap's Formula/ward.rb still needs one line in its install method:

bin.install_symlink "ward" => "warded"

The tap repo (coilyco-flight-deck/homebrew-tap) was outside ward#247's run scope, so the host symlink is deferred here. Once added, brew install ward puts warded on PATH and the multicall rewrite does the rest. See docs/drive.md ("Shipping the warded symlink").

Follow-up from ward#247 (shipped in dfa5610). The `warded` public-face shim works in two of three install paths: - **In-binary**: `main.go` rewrites argv when invoked as `warded` -> `ward drive <args>` (the multicall, not a second code path). - **Container**: the entrypoint symlinks `warded -> ward` next to the installed binary, so the launch demo runs `warded claude "..."` with no extra step. - **Host brew install** (this follow-up): the centralized tap's `Formula/ward.rb` still needs one line in its `install` method: ```ruby bin.install_symlink "ward" => "warded" ``` The tap repo (`coilyco-flight-deck/homebrew-tap`) was outside ward#247's run scope, so the host symlink is deferred here. Once added, `brew install ward` puts `warded` on PATH and the multicall rewrite does the rest. See docs/drive.md ("Shipping the warded symlink").

coilyco-ops referenced this issue from coilyco-flight-deck/homebrew-tap

2026-06-24 15:37:59 +00:00

packaging: add the warded -> ward symlink to the tap formula #2

coilyco-ops commented

2026-06-24 15:38:00 +00:00

Member

🎯 ward pre-flight: WRONG-REPO

ward agent headless --driver claude ran a pre-flight read on this issue and judged the work belongs in coilyco-flight-deck/homebrew-tap, not here. Rather than burn cycles searching, it blind-fired a fresh issue there:

coilyco-flight-deck/homebrew-tap#2 - coilyco-flight-deck/homebrew-tap#2

add bin.install_symlink "ward" => "warded" to the install method in Formula/ward.rb so brew install ward puts warded on PATH for the multicall rewrite.

No container was launched here. If the routing is wrong, close coilyco-flight-deck/homebrew-tap#2 and re-dispatch this issue with ward agent headless --driver claude <ref> --no-preflight to skip the gate.

full pre-flight read

The issue's own text is explicit: the one-line change goes into Formula/ward.rb, which lives in coilyco-flight-deck/homebrew-tap ("the centralized tap"), and it even notes the tap was "outside ward#247's run scope." The detached run clones coilyco-flight-deck/ward, which won't contain the formula at all, so there's nothing to edit, commit, or merge here. This is a clean wrong-repo call from the issue text alone, not from anything missing in the local tree.

WRONG-REPO: coilyco-flight-deck/homebrew-tap - add bin.install_symlink "ward" => "warded" to the install method in Formula/ward.rb so brew install ward puts warded on PATH for the multicall rewrite.

Posted automatically by ward agent headless --driver claude pre-flight (ward#159).

— Claude (she/her), via ward agent

### 🎯 ward pre-flight: WRONG-REPO `ward agent headless --driver claude` ran a pre-flight read on this issue and judged the work belongs in **coilyco-flight-deck/homebrew-tap**, not here. Rather than burn cycles searching, it blind-fired a fresh issue there: - coilyco-flight-deck/homebrew-tap#2 - https://forgejo.coilysiren.me/coilyco-flight-deck/homebrew-tap/issues/2 > add `bin.install_symlink "ward" => "warded"` to the `install` method in `Formula/ward.rb` so `brew install ward` puts `warded` on PATH for the multicall rewrite. No container was launched here. If the routing is wrong, close coilyco-flight-deck/homebrew-tap#2 and re-dispatch this issue with `ward agent headless --driver claude <ref> --no-preflight` to skip the gate. <details><summary>full pre-flight read</summary> The issue's own text is explicit: the one-line change goes into `Formula/ward.rb`, which lives in `coilyco-flight-deck/homebrew-tap` ("the centralized tap"), and it even notes the tap was "outside ward#247's run scope." The detached run clones `coilyco-flight-deck/ward`, which won't contain the formula at all, so there's nothing to edit, commit, or merge here. This is a clean wrong-repo call from the issue text alone, not from anything missing in the local tree. WRONG-REPO: coilyco-flight-deck/homebrew-tap - add `bin.install_symlink "ward" => "warded"` to the `install` method in `Formula/ward.rb` so `brew install ward` puts `warded` on PATH for the multicall rewrite. </details> --- Posted automatically by `ward agent headless --driver claude` pre-flight (ward#159).  — Claude (she/her), via `ward agent`

coilyco-ops added the

headless

labels

2026-06-24 17:20:15 +00:00

coilyco-ops commented

2026-06-24 17:30:33 +00:00

Member

Re-triage (goose-triage method, claude-macos-kais-macbook-pro-2 as the judgment engine, 2026-06-24)

P3 - One-line packaging follow-up (warded->ward symlink in the tap formula), low but kept.
headless - Single well-specified line with exact code given, an agent can land it unattended.

**Re-triage** (goose-triage method, claude-macos-kais-macbook-pro-2 as the judgment engine, 2026-06-24) - **P3** - One-line packaging follow-up (warded->ward symlink in the tap formula), low but kept. - **headless** - Single well-specified line with exact code given, an agent can land it unattended.

coilysiren closed this issue

2026-06-25 04:56:46 +00:00