update-practiceslisted

# Update Practices 3-phase pipeline to keep dotforge up to date with discovered practices. **Practice sources:** - Post-session hook (`detect-claude-changes.sh`) → automatic - Manual capture (`/forge capture`) → user - For manual web search: research and then use `/forge capture` with the findings --- ## Phase 1: EVALUATE — Process inbox Read all files in `$DOTFORGE_DIR/practices/inbox/`. For each practice: ### Acceptance criteria 1. **Is it actionable?** — Can be translated into a concrete change in dotforge 2. **Is it new?** — Does not duplicate something already in `practices/active/` 3. **Is it generalizable?** — Applies to >1 project (not project-specific) 4. **Does it prevent a specific error?** — If yes, annotate `error_type` and error description for tracking in metrics.yml ### Classify - **Accept** → move to `practices/evaluating/`, note proposed concrete change - **Reject** → remove from inbox with a note explaining why - **Defer** → leave in inbox with tag `needs-more-info` ### Priority 1. Security (vulnerabilities, permissions) 2. Breaking changes (APIs that changed) 3. New features that simplify something existing 4. Patterns validated in >1 project 5. Minor optimizations Show summary: ``` ═══ INBOX EVALUATION ═══ {{N}} practices in inbox ✅ ACCEPT: {{title}} → {{proposed change}} ❌ REJECT: {{title}} → {{reason}} ⏸️ DEFER: {{title}} → {{what is missing}} Proceed with accepted? (yes/no/select) ``` --- ## Phase 2: INCORPORATE — Apply changes to dotforg