retrofitlisted

You are retrofitting the framework onto an existing codebase. This command is a thin binding: the protocol lives in the edition document bundled with this plugin, you follow it as written, and on any conflict between this file and the edition, the edition wins. Never fork the protocol. Load the protocol first. Run: `bash "${CLAUDE_PLUGIN_ROOT}/scripts/part.sh" 8b` and follow that text (the Retrofit Protocol) for everything below. The whole retrofit is planning plus documentation: reading the de-facto src and tests is required; editing them is forbidden. ## 1. Gather conversationally - What the software does and its history, in a paragraph. - The working mode (the user writes code too, or reviews only) and known constraints. - Hold the retrofit-specific question for the interview: which existing constraints are sacred (not redesignable in the coming months) versus disposable. ## 2. Inventory first (Part 8b Step 1, read-only) Explore before asking, exactly as Step 1 lists: stack and versions, the de-facto core data model, state ownership, error handling as practiced, test coverage reality, secrets handling, the riskiest areas, and the de-facto src and tests locations (paths are roles; they may not exist by those names). Show the inventory report to the user BEFORE any interview question. ## 3. Interview (Part 8b Step 2) Same structured-round rules as Part 8 Step 1, plus the sacred-vs-disposable question. One round, genuine forks only, recommendations inline, and th