030-wave-execution

Wave Execution (Cursor Adaptation)

CRITICAL: Cursor does NOT have an Agent() tool. All wave tasks execute sequentially in the current Composer session. You are both the coordinator AND the implementer. Agent dispatch (3-tier resolution: project > plugin > general-purpose) is NOT applicable — follow the role's agent-prompt patterns directly.

State directory: All state files live in .cursor/ (STATE.md, wave-scope.json).

Pre-Execution

Before starting Wave 1:

1. git status --short — commit or stash any uncommitted changes
2. Capture baseline: SESSION_START_REF=$(git rev-parse HEAD) — keep for the whole session
3. Confirm the agreed plan is still valid
4. Read persistence from Session Config (default: true)

Initialize STATE.md (if persistence enabled)

Create .cursor/STATE.md (mkdir -p .cursor if needed):

---
schema-version: 1
session-type: feature|deep|housekeeping
branch: <current branch>
issues: [<issue numbers from plan>]
started_at: <ISO 8601 timestamp>
status: active
current-wave: 0
total-waves: <from session plan>
---

## Current Wave

Wave 0 — Initializing

## Wave History

(none yet)

## Deviations

(none yet)

Wave Loop

For each wave in the session plan:

Step 1: Write Scope Manifest

Write .cursor/wave-scope.json before each wave. Set enforcement: warn unless .cursor/hooks.json is installed — then preToolUse can block via cursor-hook-bridge.mjs. afterFileEdit remains post-hoc (cannot unwrite):

{
  "wave": 1,
  "role": "<role>",
  "enforcement": "warn",
  "allowedPaths": ["<union of all task file scopes for this wave>"],
  "blockedCommands": ["rm -rf", "git push --force", "DROP TABLE", "git reset --hard", "git checkout -- ."]
}

Role-specific scope rules:

• Discovery: allowedPaths: [] — READ-ONLY, do not edit files
• Quality Phase 1 (Simplification): production files changed this session only (no test files)
• Quality Phase 2 (Tests): test file patterns only (**/*.test.*, **/*.spec.*, **/__tests__/**)