docs(11.1): create phase plan

Six plans (tracer generator, site UX and checkers, content A, content B,
acme/blog walkthrough, unit tests). SC4/DOCS-04 narrowed to docs/ pages per
D-18; README Go fence conversion logged as a todo.

.planning/phases/11.1-summercms-documentation-for-humans-and-ai-agents/11.1-CONTEXT.md

@@ -56,6 +56,7 @@ Not in this phase:
 - **D-15:** Syntax highlighting uses `github.com/alecthomas/chroma/v2`, approved by the user at this checkpoint (overrides the research's stdlib-only recommendation). It is called from a small custom goldmark `NodeRenderer`; `yuin/goldmark-highlighting` stays rejected. This is the only new dependency; `go.mod` gains chroma/v2 and its transitive `dlclark/regexp2`, and the phase gate asserts no other module is added.
 - **D-16:** The walkthrough code is an in-root package under `docs/examples/blog`, covered by root `go test ./...`, plus a scaffold-layout test.
 - **D-17:** Raw pages sit beside their HTML pages (`/x/page.html` and `/x/page.md`). Config-key checking is deferred and noted in CLAUDE.md. The wristband default that names the consuming application is logged as a follow-up todo; its API does not change in this phase.
+- **D-18:** (plan-check W1, 2026-09-30) The `src=` compile-and-run rule covers Go fences in `docs/` pages only. Go fences in the ingested module READMEs are rendered as written and covered by the identifier checker. DOCS-04 and ROADMAP SC4 are worded to match. Converting README fences to `src=` references is a follow-up todo (`.planning/todos/pending/readme-go-fences-src.md`).
 
 </decisions>