repo-maplisted

# Repository Map ## Overview Map stable workspace or repository semantics into a concise Markdown-first navigation layer rooted at `<map-root>/docs/project-map.md`, unless the project already defines an equivalent, or explicitly requested layered repository guidance in `AGENTS.md`. A map should let later work reach the correct working root, Git root when present, canonical owner, reusable contract, protocol authority, generated consumer, and verification source without rediscovering the project. Layered guidance should put shared rules at the map root and narrower commands or constraints at independently owned subproject boundaries. Source remains proof; neither artifact substitutes for task-time checks or judges changes for defects. ## Workflow 1. Resolve the requested scope, containing Git root, child/nested Git roots, map root, and `versioned` or `local-unversioned` persistence before reading broadly. Keep the deepest Git root as file owner unless current manifests prove otherwise; non-Git projects remain valid map targets. Use the root-resolution procedure in `references/checklist.md` only when boundaries are ambiguous. 2. Read effective repository guidance from the map root and each child Git root actually opened, including `AGENTS.md`, `CLAUDE.md`, and host-provided instructions when present. Run `git status --short` in every applicable Git root before editing a document there; do not run Git commands as if a non-Git container were a repository. 3. Select the reques