update-docslisted

# Update Docs > Relies on BDK foundation (STARTUP_INSTRUCTIONS.md) for project context and MCP tool preference. !`python3 ${CLAUDE_PLUGIN_ROOT}/scripts/inject.py --chain ${CLAUDE_PLUGIN_ROOT}/fragments/tool-tiers/explore.chain.json` Refresh existing architecture documentation by comparing it against current code, merging updates while preserving accurate manual prose. The result is uniform text — no changelog, no diff markers, no "updated on" annotations. ## Workflow ### 1. Parse Existing Doc Read the documentation file at `$ARGUMENTS` and extract: - **Sections**: Split by `##` headers into top-level sections - **Module root**: From the file tree code block (e.g., `src/data_migrator/processors/loaders/xml/`) - **Code references**: Class/function names from `### Class:` patterns and code blocks - **File list**: Parse file tree to get documented files - **Diagram references**: Collect ALL diagram assets: - `` image links → note the SVG path - `Source: [...](*.dot)` links → note the `.dot` source path - Inline ` ```dot ` / ` ```graphviz ` blocks → note content Do this in main context — no subagent needed. Use regex and string matching. **Fallback**: If the doc lacks a clear file tree or module root, ask the user which code path the doc covers. ### 2. Explore Current Code **Step 2.1 — Discover Current State** ```python mcp__plugin_bdk_serena__list_dir(relative_path="<module_root>", recursive=True) mcp__plugin_bdk_serena__get_symbols_overview(relativ