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

Closed
opened 2026-06-24 15:37:59 +00:00 by coilyco-ops · 1 comment
Member

Routed here from coilyco-flight-deck/ward#277 by ward agent headless --driver claude pre-flight (ward#159): the feasibility read judged this work belongs in this repo, not coilyco-flight-deck/ward.

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.

This was filed blind from the source issue's text - nobody searched this repo first, so confirm it fits before working it.


Source issue (coilyco-flight-deck/ward#277)

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").


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

— Claude (she/her), via ward agent

Routed here from coilyco-flight-deck/ward#277 by `ward agent headless --driver claude` pre-flight (ward#159): the feasibility read judged this work belongs in this repo, not coilyco-flight-deck/ward. > 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. This was filed blind from the source issue's text - nobody searched this repo first, so confirm it fits before working it. --- ### Source issue (coilyco-flight-deck/ward#277) 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"). --- Filed automatically by `ward agent headless --driver claude` pre-flight (ward#159). <!-- ward-agent-signature --> — Claude (she/her), via `ward agent`
Author
Member

🔒 Reserved by ward agent --driver claude — container ward-homebrew-tap-issue-2-claude-1059d833 on host kais-macbook-pro-2.local is carrying this issue (reserved 2026-06-24T15:38:37Z). Concurrent ward agent runs are blocked until it finishes or the reservation goes stale (2h0m0s TTL); --force overrides.

— Claude (she/her), via ward agent

<!-- ward-agent-reservation --> 🔒 Reserved by `ward agent --driver claude` — container `ward-homebrew-tap-issue-2-claude-1059d833` on host `kais-macbook-pro-2.local` is carrying this issue (reserved 2026-06-24T15:38:37Z). Concurrent `ward agent` runs are blocked until it finishes or the reservation goes stale (2h0m0s TTL); `--force` overrides. <!-- ward-agent-signature --> — Claude (she/her), via `ward agent`
Sign in to join this conversation.
No description provided.