Name the Carried Trees Exclusion Wherever the Hub-Only Set Is Defined #3543

Summary

spec/audit.py hub_only_paths builds the hub-only set as the hub's tracked paths minus three things: the spec/files.json baseline entries, every hub path a carried trees declaration covers, and every hub path below a repoOwnedTrees entry. The three prose statements of that set name only the first and the third.

• AUDIT.md "carried-scope" bullet: "the hub's git-tracked paths minus the spec/files.json baseline".
• RESYNC.md section 4, the detector sentence and its mermaid node.
• spec/project-types.json, the carried.hubonly.absent assertion.

Failure

A reader taking the prose at its word expects a hub path under a carried tree, such as a file below .github/skills/, to be reported as hub-only when a repository holds it. The audit never reports it, since the tree declaration excludes it. The prose and the code disagree on what the detector measures.

Expected

All three statements name the carried trees exclusion, or say the set excludes everything spec/files.json declares, so each reads the same as the code.

Found By

The local strict review of #3540 (issue #3528), which added the repoOwnedTrees sentence to all three and listed this as pre-existing in its body without filing it.

🤖 Generated with Claude Code