[Bakhomious]

The user dropped Homebrew on 2026-11-04 and chose, through nudge, GitHub releases installed with mise's github: backend, as nudge's releases were before it moved to Homebrew. This PR only updates the plan.

• Decision 5 is rewritten in place as the user's call. It replaces the lead's call for a formula in codedogapp/homebrew-tap:
  • A version tag starts a release workflow. It builds for darwin-arm64, checks the binary's version against the tag, packs an archive with the license and the notices, and attests its build provenance.
  • Users install with mise use -g github:codedogapp/baton. mise checks the digest and the attestation, and skips releases younger than 24 h.
• Step homebrew becomes release. The archive still carries the notices of the code built into baton, mvdan.cc/sh's BSD-3 license among them; decision 50 now points at release.
• New step pane-path (Todo). It answers what puts baton on a pane's PATH without Homebrew; today nothing does:
  • The agents run baton … by name. The guard needs a literal program name, so "$BATON_BIN" … would be denied as dynamic.
  • tmux gives a new pane the PATH of the client that made it, which is the baton that ran tmux new-session. I checked this in tmux's spawn.c and with an isolated probe.
  • So a baton started by its path, a go install with GOBIN off the PATH, or an older baton earlier on the PATH leaves the agents without this baton. That is what happened in the guard-orchestrator live check (fact 37).
  • baton pane will put its own program's folder first on its copilot's PATH, unless that PATH already finds this program as baton.
• Smaller edits: deliver-github → Done (feat(deliver): baton deliver pushes a ready feature and opens its pull request #45). The milestone line and the scope bullet no longer mention Homebrew.

Left as they are, per the orchestrator: decision 27, facts 11 and 30, decision 42, the tests' /opt/homebrew/bin strings and the g wrapper names.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud