v1.2.0 — Root Feature Map & nested roots (multi-VCS)

The root AGENTS.md now carries its own Feature Map, and the framework gains nested roots — first-class support for composing independently versioned projects (git submodules, SVN externals, Perforce mapped paths) that each have their own root DOX.

Root Feature Map

• The root AGENTS.md holds a Feature Map under exactly the same rules as child docs: it owns features whose lowest common subtree is the whole project, plus the project's primary system-wide features, pointing into the owning child docs when detail lives deeper.
• Ships with a "Not yet mapped" placeholder that the Initialization procedure fills, mirroring how "Not yet indexed" works for the Child DOX Index.

Nested roots

• A nested root is a sub-root that is also the root of its own independently versioned project. The marker is VCS-neutral and mechanical: any folder whose AGENTS.md carries the full DOX rules is a nested root — the same doc works whichever folder an engineer roots their workspace at.
• Five explicit rules: leave its doc as-is (never rewrite to Child Doc Shape or strip its rules), read it as a local root, never edit it to resolve a conflict (report instead), the parent records expectations in its own doc, and changes inside it belong to that project's own repository.
• Initialization, Read Before Editing, Update After Editing, and Closeout all reference nested roots at the point of action, so weaker models can't miss them.

Prompts synced

• The audit prompt marks nested roots and never flags them as shape violations; contract conflicts involving one are marked "decide with the owner."
• The auto-repair prompt gets a loud guard — "NESTED ROOTS ARE OFF-LIMITS" — before any fixing begins, plus catches for leftover "Not yet mapped" placeholders.
• Init, new-session, short forms, and scoped one-liners all updated; skip lists now include .svn.

Full changelog: v1.1.1...v1.2.0