update-architecturelisted

# Update Architecture Documentation Maintain the project's architecture docs, wherever they live. Keep updates surgical, compact, and useful. Throughout this skill, `{architecture}` means the resolved architecture documentation root (see below) — never a hardcoded directory. Open with one sentence saying what you are about to do and what it will produce. ## Modes Use one of two modes: 1. **Maintenance mode** — architecture docs already exist and code changed. Make surgical updates only. 2. **Current-state mode** — user explicitly asks to establish, initialize, map, or review current architecture. Create or refresh a compact architecture baseline. When invoked by `/session-post-implementation`, default to maintenance mode. ## Architecture Doc Discovery Resolve `{architecture}` before doing anything else, using the same order every other session-flow skill uses: 1. Read `.session-flow.json` and use `paths.architecture` if set. 2. Otherwise detect, in order: `architecture/`, `_devdocs/architecture/`, `docs/architecture/`. 3. Use whichever resolved first as `{architecture}` for the rest of the session, and state the resolved path in your first message. Once resolved, treat `{architecture}` as the single architecture documentation location for this project — do not scatter architecture docs across other roots, and do not migrate an existing root to a different one without asking. If `.session-flow.json` is missing and no candidate directory exists, suggest running `/se