gabe-scope-pivotlisted

# Gabe Scope Pivot — direction-change rewrite **Usage:** `/gabe-scope-pivot <description>` ## Gabe execution contract (E1–E7) This skill runs under the suite execution contract — E1 EVIDENCE · E2 RUN-BEFORE-✅ · E3 NO SILENT DOWNGRADE · E4 REUSE FIRST · E5 STATE SYNC · E6 MISSING ANCHOR = STOP · E7 REPORT WHERE — floors, not ceilings; a skill's own gate may be stricter, never looser. Full text: `../gabe-docs/references/execution-contract.md` (if that file is missing, E6 applies — STOP). Handles direction-shifting scope changes. Unlike addition, a pivot restructures the premise — downstream SCs, REQs, phases, and refs all need re-evaluation. The old SCOPE is archived (never deleted); a new v{N+1} is derived. **Invariants:** - Old SCOPE.md v{N} + scope-references.yaml v{N} archived to `.kdbp/archive/vN/` (a legacy standalone `.kdbp/ROADMAP.md`, if the project still has one from before A2, is archived alongside it) - New SCOPE.md `scope_version:` bumps to {N+1}; `last_scope_event:` updates - New SCOPE.md `phases_version:` resets to 1 (new scope = new phase-arc history) - Pivot rationale recorded in Change Log with reference to archived v{N} - Research directory re-archived if regenerating (optional prompt) > **Rendering note.** Output templates in this spec wrapped in bare triple-backtick fences are spec-meta delimiters — render their contents as plain markdown at runtime. Tagged fences (```yaml, ```diff) stay fenced. See `gabe-docs/SKILL.md` § "Runtime output rendering con