cleargate 0.14.0 → 0.15.1

package/dist/templates/cleargate-planning/.cleargate/scripts/write_dispatch.sh

@@ -1,172 +0,0 @@
-#!/usr/bin/env bash
-# write_dispatch.sh — write a dispatch marker JSON file before each Task() spawn.
-#
-# The token-ledger.sh SubagentStop hook reads this file (keyed by session_id) to
-# get explicit attribution (work_item_id + agent_type) rather than relying on
-# transcript-grep heuristics.
-#
-# Usage:
-#   bash .cleargate/scripts/write_dispatch.sh <work_item_id> <agent_type>
-#
-# FALLBACK PATH (CR-026): The primary dispatch-marker path is the PreToolUse:Task hook
-# at `.claude/hooks/pre-tool-use-task.sh`, which auto-writes the marker on every Task()
-# spawn without manual orchestrator intervention. This script is retained for one-off
-# Architect dispatches or spawns whose Task() prompt does not contain a parseable
-# work-item marker. Use it only when the PreToolUse:Task hook cannot determine the
-# work_item_id from the prompt (e.g., a generic Architect spawn not tied to a sprint item).
-#
-# Args:
-#   $1  work_item_id  — e.g. STORY-020-02, CR-016, BUG-021
-#   $2  agent_type    — one of: developer|architect|qa|reporter|devops|cleargate-wiki-contradict
-#
-# Env (optional):
-#   CLAUDE_SESSION_ID         — session UUID of the orchestrator session
-#   ORCHESTRATOR_PROJECT_DIR  — override for repo root (cross-project routing)
-#
-# Exit codes:
-#   0  success
-#   1  missing required args
-#   2  no .active sprint sentinel found
-#
-# Output: .cleargate/sprint-runs/<sprint>/.dispatch-<session-id>.json
-# Log:    .cleargate/hook-log/write_dispatch.log
-
-set -u
-
-# ─── Resolve repo root ──────────────────────────────────────────────────────
-REPO_ROOT="${ORCHESTRATOR_PROJECT_DIR:-${CLAUDE_PROJECT_DIR:-$(git rev-parse --show-toplevel 2>/dev/null || pwd)}}"
-LOG_DIR="${REPO_ROOT}/.cleargate/hook-log"
-mkdir -p "${LOG_DIR}"
-LOG="${LOG_DIR}/write_dispatch.log"
-
-# ─── Validate args ──────────────────────────────────────────────────────────
-if [[ $# -lt 2 || -z "${1:-}" || -z "${2:-}" ]]; then
-  printf '[%s] error: usage: write_dispatch.sh <work_item_id> <agent_type>\n' "$(date -u +%FT%TZ)" >> "${LOG}"
-  printf 'Usage: write_dispatch.sh <work_item_id> <agent_type>\n' >&2
-  exit 1
-fi
-
-WORK_ITEM_ID="${1}"
-AGENT_TYPE="${2}"
-
-# ─── Validate agent_type ────────────────────────────────────────────────────
-case "${AGENT_TYPE}" in
-  developer|architect|qa|reporter|devops|cleargate-wiki-contradict)
-    ;;
-  *)
-    printf '[%s] error: invalid agent_type: %s\n' "$(date -u +%FT%TZ)" "${AGENT_TYPE}" >> "${LOG}"
-    printf 'error: invalid agent_type: %s (expected developer|architect|qa|reporter|devops|cleargate-wiki-contradict)\n' "${AGENT_TYPE}" >&2
-    exit 3
-    ;;
-esac
-
-# ─── Resolve active sprint ──────────────────────────────────────────────────
-ACTIVE_SENTINEL="${REPO_ROOT}/.cleargate/sprint-runs/.active"
-if [[ ! -f "${ACTIVE_SENTINEL}" ]]; then
-  printf '[%s] error: no .active sentinel at %s\n' "$(date -u +%FT%TZ)" "${ACTIVE_SENTINEL}" >> "${LOG}"
-  printf 'error: no active sprint sentinel at %s\n' "${ACTIVE_SENTINEL}" >&2
-  exit 2
-fi
-
-SPRINT_ID="$(tr -d '[:space:]' < "${ACTIVE_SENTINEL}")"
-if [[ -z "${SPRINT_ID}" ]]; then
-  printf '[%s] error: .active sentinel is empty\n' "$(date -u +%FT%TZ)" >> "${LOG}"
-  printf 'error: .active sentinel is empty\n' >&2
-  exit 2
-fi
-
-SPRINT_DIR="${REPO_ROOT}/.cleargate/sprint-runs/${SPRINT_ID}"
-mkdir -p "${SPRINT_DIR}"
-
-# ─── Fallback guard (CR-026 / STORY-043-09) ─────────────────────────────────
-# If the PreToolUse:Task hook already wrote a same-session auto-marker for THIS
-# EXACT SPAWN (same work_item_id + agent_type + session_id), this script is a
-# no-op fallback. Exit 0 without writing a duplicate marker.
-#
-# SPAWN-SCOPED: a stale auto-marker from a DIFFERENT prior spawn (different
-# work_item_id or different agent_type) must NOT trigger a skip — it is not a
-# duplicate for this spawn. Fail toward writing: when no exact same-spawn match
-# is found, always write. (A duplicate is harmless; a missing marker loses
-# attribution — bias toward writing.)
-if [[ -n "${CLAUDE_SESSION_ID:-}" ]]; then
-  for _marker in "${SPRINT_DIR}"/.dispatch-*.json; do
-    [[ -f "${_marker}" ]] || continue
-    _session_id="$(jq -r '.session_id // ""' "${_marker}" 2>/dev/null || true)"
-    _writer="$(jq -r '.writer // ""' "${_marker}" 2>/dev/null || true)"
-    _work_item_id="$(jq -r '.work_item_id // ""' "${_marker}" 2>/dev/null || true)"
-    _agent_type="$(jq -r '.agent_type // ""' "${_marker}" 2>/dev/null || true)"
-    if [[ "${_session_id}" == "${CLAUDE_SESSION_ID}" \
-       && "${_writer}" == pre-tool-use-task.sh* \
-       && "${_work_item_id}" == "${WORK_ITEM_ID}" \
-       && "${_agent_type}" == "${AGENT_TYPE}" ]]; then
-      printf '[%s] fallback: same-spawn auto-marker present for session=%s work_item=%s agent=%s (writer=%s), no-op\n' \
-        "$(date -u +%FT%TZ)" "${CLAUDE_SESSION_ID}" "${WORK_ITEM_ID}" "${AGENT_TYPE}" "${_writer}" >> "${LOG}"
-      exit 0
-    fi
-  done
-fi
-
-# ─── Resolve session_id ─────────────────────────────────────────────────────
-SESSION_ID="${CLAUDE_SESSION_ID:-}"
-
-if [[ -z "${SESSION_ID}" ]]; then
-  # Fall back to scanning the most recent transcript filename (UUID) under
-  # ~/.claude/projects/-*-ClearGate/ pattern.
-  TRANSCRIPT_DIR="${HOME}/.claude/projects"
-  if [[ -d "${TRANSCRIPT_DIR}" ]]; then
-    SESSION_ID="$(find "${TRANSCRIPT_DIR}" -maxdepth 2 -name '*.jsonl' 2>/dev/null \
-      | sort -t '/' -k1 2>/dev/null | tail -1 \
-      | xargs -I{} basename {} .jsonl 2>/dev/null || true)"
-  fi
-fi
-
-if [[ -z "${SESSION_ID}" ]]; then
-  # Final fallback: generate a pseudo-id from timestamp
-  SESSION_ID="fallback-$(date -u +%s)"
-  printf '[%s] warn: no CLAUDE_SESSION_ID and no transcript found; using %s\n' "$(date -u +%FT%TZ)" "${SESSION_ID}" >> "${LOG}"
-fi
-
-# ─── Resolve cleargate version ───────────────────────────────────────────────
-# Read from cleargate-cli/package.json if available; otherwise use "unknown"
-PKG_JSON="${REPO_ROOT}/cleargate-cli/package.json"
-CG_VERSION="unknown"
-if [[ -f "${PKG_JSON}" ]]; then
-  CG_VERSION="$(jq -r '.version // "unknown"' "${PKG_JSON}" 2>/dev/null || echo "unknown")"
-fi
-
-# ─── Write dispatch file atomically ─────────────────────────────────────────
-# BUG-029 fix: uniquify the dispatch filename so that two parallel Task()
-# spawns from the same orchestrator session (same SESSION_ID) do NOT collide
-# on the same target path. Pattern matches pre-tool-use-task.sh:115.
-# Old: .dispatch-${SESSION_ID}.json  ← second parallel write silently overwrites first.
-# New: .dispatch-${TS}-${PID}-${RAND}.json  ← each spawn gets a distinct file.
-TS_EPOCH="$(date -u +%s)"
-DISPATCH_TARGET="${SPRINT_DIR}/.dispatch-${TS_EPOCH}-$$-${RANDOM}.json"
-SPAWNED_AT="$(date -u +%FT%TZ)"
-
-DISPATCH_JSON="$(jq -cn \
-  --arg work_item_id "${WORK_ITEM_ID}" \
-  --arg agent_type "${AGENT_TYPE}" \
-  --arg spawned_at "${SPAWNED_AT}" \
-  --arg session_id "${SESSION_ID}" \
-  --arg writer "write_dispatch.sh@cleargate-${CG_VERSION}" \
-  --arg run_id "${RUN_ID:-}" \
-  '{
-    work_item_id: $work_item_id,
-    agent_type: $agent_type,
-    spawned_at: $spawned_at,
-    session_id: $session_id,
-    writer: $writer
-  }
-  | if $run_id == "" then . else .run_id = $run_id end')"
-
-# Atomic write via mktemp + mv (rename is atomic on POSIX same-fs)
-TMP="$(mktemp "${SPRINT_DIR}/.dispatch-tmp-XXXXXX")"
-printf '%s\n' "${DISPATCH_JSON}" > "${TMP}"
-mv "${TMP}" "${DISPATCH_TARGET}"
-
-printf '[%s] wrote dispatch: sprint=%s session=%s work_item=%s agent=%s\n' \
-  "${SPAWNED_AT}" "${SPRINT_ID}" "${SESSION_ID}" "${WORK_ITEM_ID}" "${AGENT_TYPE}" >> "${LOG}"
-
-printf '%s\n' "${DISPATCH_TARGET}"
-exit 0

package/dist/templates/cleargate-planning/.cleargate/templates/Bug.md

@@ -1,126 +0,0 @@
-<instructions>
-FOLLOW THIS EXACT STRUCTURE. Output sections in order 1-5.
-YAML Frontmatter: Bug ID, Parent Ref, Status, Severity, Reporter, Approved gate.
-§1 The Anomaly: Expected vs. Actual behavior.
-§2 Reproduction Protocol: Deterministic steps to recreate.
-§3 Evidence & Context: Raw logs, stack traces, payloads — no paraphrasing.
-§4 Execution Sandbox: Exact file paths to investigate. Restrict scope to prevent unrelated refactoring.
-§5 Verification Protocol: The failing test that proves the bug exists and proves the fix resolves it.
-Output location: .cleargate/delivery/pending-sync/BUG-{ID}.md
-
-POST-WRITE BRIEF
-After Writing this document, render a Brief in chat with the following sections,
-mechanically extracted from the document's own structure:
-
-  - Prior work    ← cleargate-wiki-query result (cite [[IDs]] or write "none found")
-  - Summary        ← §1 The Anomaly (repro)
-  - Open Questions ← §0.5 Open Questions
-  - Edge Cases     ← §2 Impact (edge conditions)
-  - Risks          ← §2 Impact
-  - Ambiguity      ← bottom-of-doc ambiguity gate block
-
-Halt for human review. When ambiguity reaches 🟢, proceed to call cleargate_push_item.
-Do NOT ask separately for push confirmation — Brief approval covers it.
-
-Do NOT output these instructions.
-</instructions>
-
----
-bug_id: "BUG-{ID}"
-parent_ref: "EPIC-{ID} | STORY-{ID}"
-parent_cleargate_id: null  # canonical cleargate-id of parent work item; null for top-level
-sprint_cleargate_id: null  # canonical cleargate-id of owning sprint; null for off-sprint items
-carry_over: false  # set true to skip lifecycle reconciliation at sprint close
-status: "Draft | Triaged | In Fix | Completed"
-severity: "P0-Critical | P1-High | P2-Medium | P3-Low"
-reporter: "{name}"
-approved: false
-context_source: "approved Epic / verified codebase grounding + recorded direct approval"
-created_at: "2026-04-17T00:00:00Z"
-updated_at: "2026-04-17T00:00:00Z"
-created_at_version: "strategy-phase-pre-init"
-updated_at_version: "strategy-phase-pre-init"
-server_pushed_at_version: null
-draft_tokens:
-  input: null
-  output: null
-  cache_read: null
-  cache_creation: null
-  model: null
-  sessions: []
-cached_gate_result:
-  pass: null
-  failing_criteria: []
-  last_gate_check: null
-# Sync attribution. Optional; stamped by `cleargate push` / `cleargate pull`.
-pushed_by: null            # set by push: which user pushed
-pushed_at: null            # set by push: ISO-8601 timestamp
-last_pulled_by: null       # set by pull: which user pulled
-last_pulled_at: null       # set by pull: ISO-8601 timestamp
-last_remote_update: null   # set by pull: server's last-modified timestamp
-source: "local-authored"   # flips to "remote-authored" on intake
-last_synced_status: null   # required for conflict-detector; status at last sync
-last_synced_body_sha: null # sha256 of body at last sync
----
-
-# BUG-{ID}: {Bug Name}
-
-### Open Questions
-
-> Populate during drafting. Resolve every entry before flipping ambiguity to 🟢.
-
-- **Question:** {edge case, contradiction, or missing detail}
-- **Recommended:** {agent's proposed answer}
-- **Human decision:** {populated during Brief review}
-
-## 1. The Anomaly (Expected vs. Actual)
-**Expected Behavior:** {What the system should do under normal conditions.}
-
-**Actual Behavior:** {What it is doing right now.}
-
-## 2. Reproduction Protocol
-*(AI agents need strict, deterministic steps. "If it can't be reproduced reliably, it can't be fixed safely.")*
-
-- Go to...
-- Click...
-- Observe...
-
-## 3. Evidence & Context
-*(Provide the raw truth: stack traces, terminal errors, network payloads. Do not paraphrase.)*
-
-```
-[Paste exact logs or error messages here]
-```
-
-## 4. Execution Sandbox (Suspected Blast Radius)
-*(Restrict the agent's focus to prevent unrelated refactoring.)*
-
-**Investigate / Modify:**
-- `src/...`
-
-## 5. Verification Protocol (The Failing Test)
-*(The agent must write or run a specific test that proves the bug exists, then prove the fix resolves it.)*
-
-**Command:** `npm test ...`
-
----
-
-## Context Source
-
-> Discovery audit. Populated from the approved Epic, verified codebase grounding, and recorded direct approval.
-
-**context_source:** {approved Epic / verified codebase grounding + recorded direct approval}
-
----
-
-## ClearGate Ambiguity Gate (🟢 / 🟡 / 🔴)
-**Current Status: 🔴 High Ambiguity**
-
-*Evaluate each criterion against its literal text. If you substituted an interpretation, leave the box unchecked and surface the substitution in the Brief.*
-
-Requirements to pass to Green (Ready for Fix):
-- [ ] Reproduction steps are 100% deterministic.
-- [ ] Actual vs. Expected behavior is explicitly defined.
-- [ ] Raw error logs/evidence are attached.
-- [ ] Verification command (failing test) is provided.
-- [ ] `approved: true` is set in the YAML frontmatter.

package/dist/templates/cleargate-planning/.cleargate/templates/CR.md

@@ -1,130 +0,0 @@
-<instructions>
-FOLLOW THIS EXACT STRUCTURE. Output sections in order 1-4.
-YAML Frontmatter: CR ID, Parent Ref (Epic or Story being changed), Status, Approved gate.
-Use this template when CHANGING an existing feature. For net-new functionality, use story.md instead.
-§1 The Context Override: What to remove/forget + the new truth. AI agents hallucinate when old context conflicts with new requests.
-§2 Blast Radius & Invalidation: Which downstream items does this CR break? A CR acts as a "Gate Reset" on affected items.
-§3 Execution Sandbox: Exact file paths to modify.
-§4 Verification Protocol: How to confirm new logic works and old logic is fully evicted.
-Output location: .cleargate/delivery/pending-sync/CR-{ID}.md
-
-POST-WRITE BRIEF
-After Writing this document, render a Brief in chat with the following sections,
-mechanically extracted from the document's own structure:
-
-  - Prior work    ← cleargate-wiki-query result (cite [[IDs]] or write "none found")
-  - Summary        ← §1 The Context Override
-  - Open Questions ← §0.5 Open Questions
-  - Edge Cases     ← §2 Blast Radius & Invalidation
-  - Risks          ← §2 Blast Radius (downstream invalidation = risk)
-  - Ambiguity      ← bottom-of-doc ambiguity gate block
-
-Halt for human review. When ambiguity reaches 🟢, proceed to call cleargate_push_item.
-Do NOT ask separately for push confirmation — Brief approval covers it.
-
-Do NOT output these instructions.
-</instructions>
-
----
-cr_id: "CR-{ID}"
-parent_ref: "EPIC-{ID} | STORY-{ID}"
-parent_cleargate_id: null  # canonical cleargate-id of parent work item; null for top-level
-sprint_cleargate_id: null  # canonical cleargate-id of owning sprint; null for off-sprint items
-carry_over: false  # set true to skip lifecycle reconciliation at sprint close
-status: "Draft | In Review | Approved | Completed"
-approved: false
-context_source: "approved Epic / verified codebase grounding + recorded direct approval"
-created_at: "2026-04-17T00:00:00Z"
-updated_at: "2026-04-17T00:00:00Z"
-created_at_version: "strategy-phase-pre-init"
-updated_at_version: "strategy-phase-pre-init"
-server_pushed_at_version: null
-draft_tokens:
-  input: null
-  output: null
-  cache_read: null
-  cache_creation: null
-  model: null
-  sessions: []
-cached_gate_result:
-  pass: null
-  failing_criteria: []
-  last_gate_check: null
-# Sync attribution. Optional; stamped by `cleargate push` / `cleargate pull`.
-pushed_by: null            # set by push: which user pushed
-pushed_at: null            # set by push: ISO-8601 timestamp
-last_pulled_by: null       # set by pull: which user pulled
-last_pulled_at: null       # set by pull: ISO-8601 timestamp
-last_remote_update: null   # set by pull: server's last-modified timestamp
-source: "local-authored"   # flips to "remote-authored" on intake
-last_synced_status: null   # required for conflict-detector; status at last sync
-last_synced_body_sha: null # sha256 of body at last sync
----
-
-# CR-{ID}: {Change Request Name}
-
-## 0.5 Open Questions
-
-> Populate during drafting. Resolve every entry before flipping ambiguity to 🟢.
-
-- **Question:** {edge case, contradiction, or missing detail}
-- **Recommended:** {agent's proposed answer}
-- **Human decision:** {populated during Brief review}
-
-## 1. The Context Override (Old vs. New)
-*(AI agents hallucinate when old context conflicts with new requests. Explicitly declare what to evict.)*
-
-**Obsolete Logic (What to Remove / Forget):**
-- {e.g., We no longer use Stripe for this flow.}
-
-**New Logic (The New Truth):**
-- {e.g., Route all payments through PayPal.}
-
-## 2. Blast Radius & Invalidation
-*(A CR acts as a "Gate Reset" — all affected downstream items revert to 🔴 High Ambiguity.)*
-
-- [ ] Invalidate/Update Story: [Link]
-- [ ] Invalidate/Update Epic: [Link]
-- [ ] Database schema impacts? {Yes/No — describe}
-
-## Existing Surfaces
-
-> L1 reuse audit. List source-tree implementations this CR extends or modifies. Cite file:line.
-> Cite paths with at least one '/' separator; root files use './name.ext'. Bare filenames and dotted code references are ignored.
-
-- **Surface:** `path/to/file.ext:NN` — {what it does today}
-- **Why this CR extends rather than rebuilds:** {one paragraph — required when the change names a capability that already exists somewhere in the tree}
-
-## 3. Execution Sandbox
-*(Restrict the agent's scope to prevent unrelated refactoring.)*
-
-**Modify:**
-- `src/...`
-
-## 4. Verification Protocol
-*(How do we confirm new logic works and old logic is completely removed?)*
-
-**Command/Test:** `npm test ...`
-
----
-
-## Context Source
-
-> Discovery audit. Populated from the approved Epic, verified codebase grounding, and recorded direct approval.
-
-**context_source:** {approved Epic / verified codebase grounding + recorded direct approval}
-
----
-
-## ClearGate Ambiguity Gate (🟢 / 🟡 / 🔴)
-**Current Status: 🔴 High Ambiguity**
-
-*Evaluate each criterion against its literal text. If you substituted an interpretation, leave the box unchecked and surface the substitution in the Brief.*
-
-Requirements to pass to Green (Ready for Execution):
-- [ ] "Obsolete Logic" to be evicted is explicitly declared.
-- [ ] All impacted downstream Epics/Stories are identified and reverted to 🔴 High Ambiguity.
-- [ ] Execution Sandbox contains exact file paths.
-- [ ] Verification command is provided.
-- [ ] `approved: true` is set in the YAML frontmatter.
-- [ ] Existing Surfaces cites at least one source-tree path the CR extends.

package/dist/templates/cleargate-planning/.cleargate/templates/Sprint Plan Template.md

@@ -1,137 +0,0 @@
-<instructions>
-This template is actively authored during the Prepare phase.
-
-WHAT TO GATHER
-  - Sprint number — read .cleargate/wiki/active-sprint.md, scan pending-sync/SPRINT-*.md, emit max(N) + 1
-  - Available work items — pending-sync/{EPIC,STORY,CR,BUG,HOTFIX}-*.md filtered ambiguity:🟢 + status:Ready
-  - Human-set priorities — frontmatter `priority` field per item
-  - Cross-item dependencies — `parent_epic_ref:` + shared file-surface analysis
-
-HOW TO GATHER
-  - Read for sprint-runs/, Grep for pending-sync/, scripts/wiki-query for awareness layer
-  - cleargate-cli/src/lib/admin-url.ts for any admin-link references
-
-ANALYSIS REQUIRED
-  - Propose priority reordering for technical reasons (dep chains, shared-surface conflicts, fast-lane bundling). One-line rationale per change.
-  - Flag missing decomposition (epics with no child stories) — must resolve before Gate 2 passes.
-  - Trigger Architect Sprint Design Review (writes §2 Execution Strategy) once scope is locked.
-
-WHERE TO WRITE
-  - .cleargate/delivery/pending-sync/SPRINT-<#>_<name>.md
-
-POST-WRITE BRIEF
-  Render in chat with these sections:
-    - Sprint Goal (1 sentence)
-    - Selected items (table: id / type / lane / milestone / parallel? / bounce-exposure)
-    - Recommended priority changes (with one-line rationale per change)
-    - Open questions for human (with recommended answers)
-    - Risks (with mitigations)
-    - Current ambiguity + Gate 2 readiness checklist (decomposed? all 🟢? SDR §2 written?)
-  Halt for human review. When ambiguity reaches 🟢 AND Gate 2 conditions satisfy, proceed to call cleargate_push_item.
-
-DUAL-AUDIENCE STRUCTURE
-  Top of body: Stakeholder/Sponsor view (Sprint Goal, Business Outcome, Risks/Mitigations, Metrics).
-  Bottom of body: AI-execution view (Phase Plan, Merge Ordering, Lane Audit, ADR-Conflict Flags, Decomposition Status).
-
-Do NOT output these instructions.
-</instructions>
-
----
-sprint_id: "SPRINT-{ID}"
-parent_cleargate_id: null  # canonical cleargate-id of parent work item; null for top-level
-sprint_cleargate_id: null  # canonical cleargate-id of owning sprint; null for off-sprint items
-carry_over: false  # set true to skip lifecycle reconciliation at sprint close
-lifecycle_init_mode: "warn"  # "warn" | "block" — controls sprint-init lifecycle gate (§10.4); use "block" for SPRINT-16+
-remote_id: "{PM_TOOL_SPRINT_ID}"
-source_tool: "linear | jira"
-status: "Draft | Active | Completed"
-start_date: "{YYYY-MM-DD}"
-end_date: "{YYYY-MM-DD}"
-synced_at: "{ISO-8601 timestamp}"
-created_at: "2026-04-17T00:00:00Z"
-updated_at: "2026-04-17T00:00:00Z"
-created_at_version: "strategy-phase-pre-init"
-updated_at_version: "strategy-phase-pre-init"
-draft_tokens:
-  input: null
-  output: null
-  cache_read: null
-  cache_creation: null
-  model: null
-  sessions: []
-cached_gate_result:
-  pass: null
-  failing_criteria: []
-  last_gate_check: null
----
-
-# SPRINT-{ID}: {Sprint Number / Name}
-
-## 0. Stakeholder Brief
-*(Sponsor-readable summary. Pushed via cleargate push. Pair with §3 Risks below.)*
-
-- **Sprint Goal:** {1 sentence}
-- **Business Outcome:** {what the user / sponsor gets}
-- **Risks (top 3):** {bullet list, see §3 for full table}
-- **Metrics:** {expected impact / KPIs}
-
-## Sprint Goal
-{One clear sentence describing the primary objective of this sprint, as defined in the PM tool.}
-
-## 1. Consolidated Deliverables
-*(Pulled from PM tool. IDs are the remote PM entity IDs.)*
-
-| Story ID | Title | Lane | Milestone | Parallel? | Bounce Exposure |
-|---|---|---|---|---|---|
-| `{STORY-NNN-NN}` | {Title} | standard / fast | M{N} | y / n | low / med / high |
-
-## 2. Execution Strategy
-*(Written by Architect during Sprint Design Review. Required before sprint start.)*
-
-### 2.1 Phase Plan
-{Parallel vs sequential story groups. List which stories run concurrently in each wave and which must be serialized.}
-Example:
-- Wave 1 (sequential): STORY-NNN-01 → STORY-NNN-02 (02 depends on 01's schema)
-- Wave 2 (parallel): STORY-NNN-03 ‖ STORY-NNN-04
-
-### 2.2 Merge Ordering (Shared-File Surface Analysis)
-{List files touched by more than one story. For each shared file, specify which story lands first and why.}
-
-| Shared File | Stories Touching It | Merge Order | Rationale |
-|---|---|---|---|
-| `.cleargate/knowledge/cleargate-enforcement.md` | STORY-NNN-01, STORY-NNN-02 | 01 → 02 | 01 adds §2; 02 amends §2 |
-
-### 2.3 Shared-Surface Warnings
-{Explicit conflict risks. One bullet per risk. Cite file + story pair.}
-- None identified. (Replace with actual warnings if applicable.)
-
-### 2.4 Lane Audit
-{Architect populates one row per fast-lane story during Sprint Design Review. Empty by default — rows added only for non-`standard` lanes.}
-
-| Story | Lane | Rationale (≤80 chars) |
-|---|---|---|
-| `STORY-NNN-NN` | fast | <one-line rationale> |
-
-### 2.5 ADR-Conflict Flags
-{Any story whose implementation conflicts with an Architectural Decision Record in `.cleargate/knowledge/` or prior sprint decisions. One bullet per flag.}
-- None identified. (Replace with actual flags if applicable.)
-
-## Risks & Dependencies
-*(As defined in the PM tool.)*
-
-| Risk | Mitigation |
-|---|---|
-| {Description} | {Action} |
-
-## Metrics & Metadata
-- **Expected Impact:** {e.g., performance improvement %, specific user outcome}
-- **Priority Alignment:** {Notes on prioritization from the PM tool}
-
----
-
-## Execution Guidelines (Local Annotation — Not Pushed)
-*(Vibe Coder: Fill this in locally to direct Claude Code during the Execution Phase. This section never syncs to the PM tool.)*
-
-- **Starting Point:** {Which deliverable to tackle first and why}
-- **Relevant Context:** {Key documentation or codebase areas to reference}
-- **Constraints:** {Specific technical boundaries or "out of scope" rules for this sprint}