drift-analysis

# Drift Analysis Knowledge and patterns for analyzing project state, detecting plan drift, and creating prioritized reconstruction plans. ## Architecture Overview ``` /drift-detect │ ├─→ collectors.js (pure JavaScript) │ ├─ scanGitHubState() │ ├─ analyzeDocumentation() │ └─ scanCodebase() │ └─→ plan-synthesizer (Opus) └─ Deep semantic analysis with full context ``` **Data collection**: Pure JavaScript (no LLM overhead) **Semantic analysis**: Single Opus call with complete context ## Drift Detection Patterns ### Types of Drift **Plan Drift**: When documented plans diverge from actual implementation - PLAN.md items remain unchecked for extended periods - Roadmap milestones slip without updates - Sprint/phase goals not reflected in code changes **Documentation Drift**: When documentation falls behind implementation - New features exist without corresponding docs - README describes features that don't exist - API docs don't match actual endpoints **Issue Drift**: When issue tracking diverges from reality - Stale issues that no longer apply - Completed work without closed issues - High-priority items neglected **Scope Drift**: When project scope expands beyond original plans - More features documented than can be delivered - Continuous addition without completion - Ever-growing backlog with no pruning ### Detection Signals ``` HIGH-CONFIDENCE DRIFT INDICATORS: - Milestone 30+ days overdue with op...