Name docs/ and notes/ in the root map, and test that the project's own tree stays named

[leaf-agent]

CLAUDE.md's repository map names seven of the nine directories in the project's own tree. The two it misses, docs/ and notes/, are both places sessions are actively sent — d4801b6a wrote notes/codex-integration.md, 8ac42a81 wrote notes/workspace-followups.md and the TODO.md section that links to it, and docs/ holds the five product documents scripts/site.py publishes as leaf.page. A session that lands in either has only the files in front of it to say what the directory is for.

What the map now says

Two paragraphs beside the existing examples/ / tests/ / scripts/ / worker/ one:

• docs/ is the site's own content — each product document there is a Leaf source, so changing what leaf.page says is a page edit rather than a template edit. That fact currently lives only in scripts/site.py's docstring, which is the wrong place for a session deciding where to make the change.
• TODO.md is the ordered priority list and notes/ holds what its items link out to, with the dating rule stated: where a note and the tree disagree, the tree is right.

The dating rule is scoped to what CI actually reads. ci.yaml's lint job runs pre-commit/action@v3.0.1 over the whole tree, and .pre-commit-config.yaml's exclude: carves out only the MCP App experiment captures — so ruff, shellcheck, typos, and the whitespace hooks all gate an authored note, and a session told otherwise would redden lint on the first one it writes. What holds is the narrower fact the rule rests on: nothing under tests/ reads notes/, so no test checks a note against the tree.

The test

test_the_root_instructions_name_every_directory_of_the_projects_own_tree derives the set from shipped_payload() rather than a list, so the next top-level directory added without a paragraph goes red instead of staying green — the same construction, and the same reason, as test_the_root_instructions_name_every_directory_ci_gates_on_its_own directly above it. Dotted directories are excluded: a session finds .github/ or .config/ through the host rather than through this map.

It matches the backticked prefix without a closing backtick, because a part is named at whatever depth it is owned at — bin/leaf is a launcher and skills/leaf/assets/ is a tree, and both name their directory. The existing test above requires the closing backtick because a working-directory: is always named as the bare directory.

Verification

• uv run pytest tests/test_interact_layer.py — 165 passed, 6 skipped.
• Bug-back: with the CLAUDE.md paragraphs stashed and the test kept, it fails with AssertionError: unnamed in CLAUDE.md: ['docs', 'notes'].
• uv run pre-commit run --files notes/mcp-apps/experiments/10/observe.py notes/mcp-apps/experiments/10/commands.sh — ruff, typos, shellcheck and the whitespace hooks each ran on those notes rather than skipping, which is the reading behind the scoped sentence above.
• uv run pre-commit run --files CLAUDE.md — passed.

This is prose plus its gate; there is no product path to regress.

[leaf-agent]

The notes/ paragraph's justification is false, and it is the one claim in this diff a session would act on directly. ci.yaml's lint job runs pre-commit/action@v3.0.1 — pre-commit run --all-files — and .pre-commit-config.yaml's exclude: carves out only notes/mcp-apps/experiments/[0-9]+/(results/|output\.txt$), with its own comment reading "lint the authored commands and findings, not the captures". So ruff gates notes/ask-placement-eval/outline.py and each experiment's observe.py and serve.py, shellcheck gates run.sh and commands.sh, and typos and the whitespace hooks gate every note. A session that reads notes/ as unchecked reddens lint on the first note it writes.

The narrower fact the dating rule actually rests on is true: nothing under tests/ reads notes/, so no test checks a note against the tree. Suggestion inline.