c41bf4f5b0
A planner had no machine-readable view of the tool set later stages would have, so it could emit acceptance checks that required tools (shell) the implementer was not permitted, causing a blocked run. modelPrompt now emits exactly one authoritative line naming the stage's permitted tools, derived from the definition via the new effectiveTools helper. effectiveTools reuses ToolNames: a present tools block, including an explicit empty one, is returned as parsed; an absent block yields the legacy mutating read/glob/grep/edit/shell bundle so it is never misrepresented as empty or read-only. The bundle is declared once as legacyTools and reused by tools.go, agent.go, pi.go and permissions.go. The redundant client-side strings.Replace of the tools line is removed from AgentClient.Generate and PiClient.Generate; the agent-only guidance sentence is preserved by appending it in agent.go, and Pi appends a short mapping line derived from piTools. Edit-scope and permitted-shell text, routing, review, budgets and retries are unchanged. Adds internal/stage/model_prompt_test.go covering explicit, absent and explicit-empty blocks plus derivation edge cases, and a guard that the agent prompt still carries the tools, edit-scope and shell-command text.