map-landscapelisted

## Repository context The current repository is both the CONSUMER, whose convention home declares where artifacts land, and the DEFAULT SUBJECT, the repository whose tracked files name the rest of the landscape. Collect with an **individual** Bash call, one command per call: the project root, `git rev-parse --show-toplevel`. Treat a failure (not a repository, git unavailable) as an unknown value and carry on; `${CLAUDE_PROJECT_DIR}` is the resolver's `--root` either way. ## Purpose Answer "what systems does this organization have, who owns them, what do they run on, and how do they relate" from what a repository already says about its neighbors. Every fact traces to a named file; every edge traces to a matched string in a tracked file; both are collected by scripts, never derived by hand. The committed record makes the answer re-runnable, so the second run reports what moved instead of quietly replacing the first. ## Resolve home and dialect Read `${CLAUDE_PLUGIN_ROOT}/reference/config.md` first; it owns the keys, the topic-doc location, and the resolution order. This skill reports against that contract rather than restating it. Run `bash "${CLAUDE_PLUGIN_ROOT}/lib/resolve-convention-home.sh" --root "${CLAUDE_PROJECT_DIR}"` and follow the exit code. Never parse the root instruction file yourself. Exit 0 means read `<home>/architecture/README.md` for `architecture_dir` and `landscape_dialect`; exit 1 (no pointer line), 2 (usage), and 3 (FAIL, surface the resolver's own