gabe-scope-additionlisted

# Gabe Scope Addition — additive scope evolution ## 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 additive scope changes. Inserts new content without touching primary user, success criteria, non-goals, architecture posture, or authoritative refs. All of those changes route to `/gabe-scope-pivot` instead. **Invariants:** - SCOPE.md `scope_version:` frontmatter stays the same (additions don't bump major version). - SCOPE.md `last_scope_event:` updates to today. - SCOPE.md `phases_version:` bumps by 1 (any `-change` bumps phases_version). - Change Log (§15) appends `addition` row — never rewrites existing rows. One log for both premise and phase-arc changes. - Prior phase IDs are immutable. New phases use decimal IDs (e.g., `2.1` between `2` and `3`). - Prior REQ IDs are immutable. New REQs append with the next sequential ID. > **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 (```jsonl) stay fenced. See `gabe-docs/SKILL.md` § "Runtime output rendering convention". ## Procedure ### Step 1: