llm-wiki-changelisted

# LLM Wiki — Standard Change Process Every change to the engine (`scripts/`, `hooks/`, `lib/`, `prompts/`, configs) follows these 5 phases in order. Do NOT skip phases. Do NOT implement before the concept is verified. ## Phase 1: Concept Write the concept as a section in the relevant document (AGENTS.md, docs/concept.md, or a new doc in `.ytstack/backlog/`). The concept must describe: - **What** changes (which scripts, flows, data) - **Why** (what problem does it solve) - **How** it integrates with existing flows (which scripts are affected) - **Edge cases** and failure modes Present the concept to the user for review. ## Phase 2: Verify Integration Before writing any code, verify the concept against the existing system: 1. Read all affected scripts and identify exact code locations 2. Check that the concept doesn't break existing flows 3. Verify naming conventions match (file paths, frontmatter fields, etc.) 4. Check for gaps: does the concept cover all code paths? 5. Present the verification to the user: "Here's what I'll change in which files" Get explicit user approval before proceeding. ## Phase 3: Implement Write the code. For each file changed: - Read the file first - Make targeted edits (don't rewrite entire files) - Test if possible (--dry-run, quick validation) ## Phase 4: Document Update ALL affected documentation: 1. **docs/PROCESS.md** — Update the relevant process section (Mermaid + Prosa + Tables + Edge Cases) 2. **README.md** — Update usage examp