docs: close the drift the self-audit found, and state the trusted-host posture

[TheAmericanMaker]

Closes #265 (L4) and #267 (L6). Docs plus two tool-description strings and one generated-footer string; suite 847/847.

#265 — documentation drift (sem 5.4, 5.6, 5.7, 5.12, 5.17)

Was	Now
README: "No JavaScript." for the dashboard	"No external assets of any kind … inlines two <script> blocks of its own (a JSON data island and the search/filter code)" — what CLAUDE.md already says
README: "Activity timeline with session-file links"	"Activity timeline of phase runs" — the renderer refuses absolute hrefs and Pi session files are absolute, so those links never rendered (mech 1.14)
MANUAL: default is pipeline-full-with-audit.yaml (6 phases)	pipeline-full-with-deep-audit.yaml (7 phases), with the six-phase file named as the older variant
MANUAL: "four evidence levels" (listing five)	five
quickstart: mechanical scan = "logic, security, concurrency, API bugs"	mechanical = logic/error-handling/config (passes 1, 2, 6); semantic = concurrency/security/API-contract (3, 4, 5), per the two SKILL.md files
INDEX.md footer: "regenerate with codecarto library-reindex" (no such CLI)	"the codecarto_library_reindex MCP tool" — in core/library.ts and the spec's example
codecarto_complete description: "creates a closeout stub … if one does not yet exist"	also says a supplied closeout_content (plus decisions) overwrites the canonical closeout, which is what writeCompletionArtifacts does

Already fixed earlier: folded scalars in the library spec (#293), codecarto_next on a complete/stuck pipeline (#306), completion wording (#303).

#267 — trust posture

docs/client-surfaces.md gains Trust posture: the host is trusted: the server and the extension defend the repository from an LLM's mistakes, not the user from their host. Recorded so the port decides deliberately: any writable absolute cwd is valid with no allowlist or MCP confirmation; an api_key tool argument lands in host logs (the argument's description now says so, and points at the environment variable); a committed config.yaml's library.path widens the Pi write sandbox (relative values refused since #243); the Broad-Side config.yaml is deliberately tracked and has a key slot. Nothing here is a code change — a tool that second-guessed its host would be unusable from every client.

🤖 Generated with Claude Code