map-landscapelisted

## Repository context The repository context here is the CONSUMER repository, the one whose convention home declares where artifacts land. It is never a discovery scope: the set of repositories to chart comes from arguments only, and the session's working directory is never scanned. 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" with two artifacts written into the consumer's declared architecture home: a C4 System Landscape view, and an application-portfolio table. Every fact traces to a named file; every relationship traces to a matched string. ## 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**: read `<home>/architecture/README.md` for `architecture_dir` and `landscape_dialect`. - **Exit 1** (no pointer line), **exit 3** (FAIL, surface the resolver's own message), **exit 2** (usage): ther