TODO: Agent access docs are contradictory
Problem
The
agent-dev note says dev agents have pal-e-docs in mcpServers with read-only access. Three other docs say agents have zero pal-e-docs access. The actual dev.md config file only has forgejo in mcpServers.Contradictions
| Source | Says |
|---|---|
| <code>agent-dev</code> note | mcpServers includes <code>pal-e-docs</code> (read-only) |
| <code>agent-spawn-conventions</code> | "Dev can't write docs — pal-e-docs removed from dev.md mcpServers — tools don't exist in agent context" |
| <code>agent-workflow</code> | "Dev and QA are repo-only. No pal-e-docs access. Period." |
| <code>dev.md</code> (actual file) | <code>mcpServers: [forgejo]</code> — no pal-e-docs |
| <code>inject-subagent-context.sh</code> | Tells dev agent to <code>get_note(slug="agent-dev")</code> — but agent can't because it doesn't have the MCP server |
Impact
Confusing. The agent-dev note is aspirational/stale. The hook tells agents to read a note they can't access. New sessions waste tokens on the contradiction.