@tekyzinc/gsd-t 3.12.15 → 3.13.10

package/commands/gsd-t-quick.md

@@ -26,6 +26,10 @@ Per `.gsd-t/contracts/model-selection-contract.md` v1.0.0.
 
 ## Step 0.1: Launch via Subagent
 
+```bash
+node scripts/gsd-t-watch-state.js advance --agent-id "$GSD_T_AGENT_ID" --parent-id "${GSD_T_PARENT_AGENT_ID:-null}" --command gsd-t-quick --step 0 --step-label ".1: Launch via Subagent" 2>/dev/null || true
+```
+
 To give this task a fresh context window and prevent compaction during consecutive quick runs, always execute via a Task subagent.
 
 **If you are the orchestrating agent** (you received the slash command directly):
@@ -127,6 +131,10 @@ Continue to Step 1 below.
 
 ## Step 1: Load Context (Fast)
 
+```bash
+node scripts/gsd-t-watch-state.js advance --agent-id "$GSD_T_AGENT_ID" --parent-id "${GSD_T_PARENT_AGENT_ID:-null}" --command gsd-t-quick --step 1 --step-label "Load Context (Fast)" 2>/dev/null || true
+```
+
 Read:
 1. `CLAUDE.md`
 2. `.gsd-t/progress.md` (if exists)
@@ -134,6 +142,10 @@ Read:
 
 ## Step 1.5: Graph-Enhanced Scope Check
 
+```bash
+node scripts/gsd-t-watch-state.js advance --agent-id "$GSD_T_AGENT_ID" --parent-id "${GSD_T_PARENT_AGENT_ID:-null}" --command gsd-t-quick --step 1 --step-label ".5: Graph-Enhanced Scope Check" 2>/dev/null || true
+```
+
 If `.gsd-t/graph/meta.json` exists (graph index is available):
 1. Query `getDomainOwner` for the target function/file to verify it belongs to the expected domain
 2. Query `getDomainBoundaryViolations` to check if the quick change would cross domain boundaries
@@ -143,6 +155,10 @@ If graph is not available, skip this step.
 
 ## Step 2: Scope Check
 
+```bash
+node scripts/gsd-t-watch-state.js advance --agent-id "$GSD_T_AGENT_ID" --parent-id "${GSD_T_PARENT_AGENT_ID:-null}" --command gsd-t-quick --step 2 --step-label "Scope Check" 2>/dev/null || true
+```
+
 Based on $ARGUMENTS, determine:
 - Which domain does this touch? (check `.gsd-t/domains/*/scope.md` if available)
 - Does it cross a domain boundary?
@@ -158,6 +174,10 @@ Proceed.
 
 ## Step 3: Execute
 
+```bash
+node scripts/gsd-t-watch-state.js advance --agent-id "$GSD_T_AGENT_ID" --parent-id "${GSD_T_PARENT_AGENT_ID:-null}" --command gsd-t-quick --step 3 --step-label "Execute" 2>/dev/null || true
+```
+
 ### Deviation Rules
 
 When you encounter unexpected situations:
@@ -190,6 +210,10 @@ When you encounter unexpected situations:
 
 ## Step 3.5: Emit Task Metrics
 
+```bash
+node scripts/gsd-t-watch-state.js advance --agent-id "$GSD_T_AGENT_ID" --parent-id "${GSD_T_PARENT_AGENT_ID:-null}" --command gsd-t-quick --step 3 --step-label ".5: Emit Task Metrics" 2>/dev/null || true
+```
+
 After committing, emit a task-metrics record for this quick task — run via Bash:
 `node bin/metrics-collector.js --milestone {current-milestone-or-none} --domain {domain-or-quick} --task quick-{timestamp} --command quick --duration_s {elapsed} --tokens_used {estimated} --context_pct ${CTX_PCT:-0} --pass {true|false} --fix_cycles {0|N} --signal_type {pass-through|fix-cycle} --notes "[quick] {description}" 2>/dev/null || true`
 
@@ -200,6 +224,10 @@ Emit task_complete event — run via Bash:
 
 ## Step 4: Document Ripple (if GSD-T is active)
 
+```bash
+node scripts/gsd-t-watch-state.js advance --agent-id "$GSD_T_AGENT_ID" --parent-id "${GSD_T_PARENT_AGENT_ID:-null}" --command gsd-t-quick --step 4 --step-label "Document Ripple (if GSD-T is active)" 2>/dev/null || true
+```
+
 If `.gsd-t/progress.md` exists, assess what documentation was affected and update ALL relevant files:
 
 ### Always update:
@@ -231,6 +259,10 @@ Skip scan docs not affected by this task. Skip analytical sections — those req
 
 ## Step 5: Test & Verify (MANDATORY)
 
+```bash
+node scripts/gsd-t-watch-state.js advance --agent-id "$GSD_T_AGENT_ID" --parent-id "${GSD_T_PARENT_AGENT_ID:-null}" --command gsd-t-quick --step 5 --step-label "Test & Verify (MANDATORY)" 2>/dev/null || true
+```
+
 Quick does not mean skip testing. Before committing:
 
 1. **Write/update tests for every new or changed code path**:
@@ -265,6 +297,10 @@ Note: Exploratory findings do NOT count against the scripted test pass/fail rati
 
 ## Step 5.25: Design Verification Agent (MANDATORY when design contract exists)
 
+```bash
+node scripts/gsd-t-watch-state.js advance --agent-id "$GSD_T_AGENT_ID" --parent-id "${GSD_T_PARENT_AGENT_ID:-null}" --command gsd-t-quick --step 5 --step-label ".25: Design Verification Agent (MANDATORY when design contract exists)" 2>/dev/null || true
+```
+
 After tests pass, check if `.gsd-t/contracts/design-contract.md` exists. If it does NOT, skip to Step 5.5.
 
 If it DOES exist and this task involved UI changes — spawn the Design Verification Agent. This agent's ONLY job is to open a browser, compare the built frontend against the original design, and produce a structured comparison table. It writes NO feature code.
@@ -338,6 +374,10 @@ After subagent returns — run observability Bash and append to token-log.md.
 
 ## Step 5.5: Red Team — Adversarial QA (MANDATORY)
 
+```bash
+node scripts/gsd-t-watch-state.js advance --agent-id "$GSD_T_AGENT_ID" --parent-id "${GSD_T_PARENT_AGENT_ID:-null}" --command gsd-t-quick --step 5 --step-label ".5: Red Team — Adversarial QA (MANDATORY)" 2>/dev/null || true
+```
+
 After tests pass, spawn an adversarial Red Team agent. Its success is measured by bugs found, not tests passed.
 
 ⚙ [opus] Red Team → adversarial validation of quick task
@@ -369,6 +409,10 @@ Append to `.gsd-t/token-log.md`:
 
 ## Step 6: Doc-Ripple (Automated)
 
+```bash
+node scripts/gsd-t-watch-state.js advance --agent-id "$GSD_T_AGENT_ID" --parent-id "${GSD_T_PARENT_AGENT_ID:-null}" --command gsd-t-quick --step 6 --step-label "Doc-Ripple (Automated)" 2>/dev/null || true
+```
+
 After all work is committed but before reporting completion:
 
 1. Run threshold check — read `git diff --name-only HEAD~1` and evaluate against doc-ripple-contract.md trigger conditions

package/commands/gsd-t-resume.md

@@ -4,6 +4,10 @@ You are resuming work after an interruption. This handles both same-session paus
 
 ## Step 0: Unattended Supervisor Auto-Reattach
 
+```bash
+node scripts/gsd-t-watch-state.js advance --agent-id "$GSD_T_AGENT_ID" --parent-id "${GSD_T_PARENT_AGENT_ID:-null}" --command gsd-t-resume --step 0 --step-label "Unattended Supervisor Auto-Reattach" 2>/dev/null || true
+```
+
 **This step runs FIRST, before reading any docs, contracts, or continue-here files.**
 
 **Worker bypass**: If the environment variable `GSD_T_UNATTENDED_WORKER=1` is set, this resume is being invoked by the unattended supervisor as a worker iteration. **SKIP this entire Step 0** — do NOT check for supervisor.pid, do NOT auto-reattach, do NOT schedule a watch tick. Fall through directly to Step 0.1. The worker's job is to do actual work, not watch itself.
@@ -33,6 +37,10 @@ Contract reference: `unattended-supervisor-contract.md` §9 (Resume Auto-Reattac
 
 ## Step 0.1: Detect Resume Mode
 
+```bash
+node scripts/gsd-t-watch-state.js advance --agent-id "$GSD_T_AGENT_ID" --parent-id "${GSD_T_PARENT_AGENT_ID:-null}" --command gsd-t-resume --step 0 --step-label ".1: Detect Resume Mode" 2>/dev/null || true
+```
+
 **Same-session** (conversation context still available — you can see prior messages about the active phase/task):
 - Skip to Step 2 — you already have the context loaded
 - Do NOT re-read all state files
@@ -42,6 +50,10 @@ Contract reference: `unattended-supervisor-contract.md` §9 (Resume Auto-Reattac
 
 ## Step 0.2: Handoff Lock Wait (headless resume only)
 
+```bash
+node scripts/gsd-t-watch-state.js advance --agent-id "$GSD_T_AGENT_ID" --parent-id "${GSD_T_PARENT_AGENT_ID:-null}" --command gsd-t-resume --step 0 --step-label ".2: Handoff Lock Wait (headless resume only)" 2>/dev/null || true
+```
+
 Before reading any continue-here file or state file, check if a parent process wrote a handoff lock for this session:
 
 ```bash
@@ -64,6 +76,10 @@ This prevents the child side of a headless spawn from reading a partial continue
 
 ## Step 0.5: Headless Read-Back Banner (MANDATORY)
 
+```bash
+node scripts/gsd-t-watch-state.js advance --agent-id "$GSD_T_AGENT_ID" --parent-id "${GSD_T_PARENT_AGENT_ID:-null}" --command gsd-t-resume --step 0 --step-label ".5: Headless Read-Back Banner (MANDATORY)" 2>/dev/null || true
+```
+
 Before loading full state, surface any completed headless sessions the user hasn't seen yet. Run this once at the start of every resume invocation:
 
 ```bash
@@ -76,6 +92,10 @@ Contract: `.gsd-t/contracts/headless-default-contract.md` v1.0.0
 
 ## Step 0.6: Context Meter Health Check (MANDATORY, v3.10.12+)
 
+```bash
+node scripts/gsd-t-watch-state.js advance --agent-id "$GSD_T_AGENT_ID" --parent-id "${GSD_T_PARENT_AGENT_ID:-null}" --command gsd-t-resume --step 0 --step-label ".6: Context Meter Health Check (MANDATORY, v3.10.12+)" 2>/dev/null || true
+```
+
 Before loading any other state, verify the Context Meter (M34) is actually alive. A dead meter was the root cause of the M36 `/compact` regression (2026-04-15) — `checkCount=2102` but every hook call failed fail-open because `ANTHROPIC_API_KEY` was unset, and the gate silently reported `pct=0` forever.
 
 Run via Bash:
@@ -105,6 +125,10 @@ Contract: `context-meter-contract.md` v1.1.0 (v3.10.12) — §"Stale Band and Re
 
 ## Step 1: Load Full State (cross-session only)
 
+```bash
+node scripts/gsd-t-watch-state.js advance --agent-id "$GSD_T_AGENT_ID" --parent-id "${GSD_T_PARENT_AGENT_ID:-null}" --command gsd-t-resume --step 1 --step-label "Load Full State (cross-session only)" 2>/dev/null || true
+```
+
 Read in this exact order:
 1. `CLAUDE.md` — project context and conventions
 2. **Check for continue-here files first**: List `.gsd-t/continue-here-*.md` files. If any exist, read the most recent one (highest timestamp). It contains exact position, next action, and open items — use this as the primary resume point.
@@ -118,6 +142,10 @@ Read in this exact order:
 
 ## Step 2: Determine Current Position
 
+```bash
+node scripts/gsd-t-watch-state.js advance --agent-id "$GSD_T_AGENT_ID" --parent-id "${GSD_T_PARENT_AGENT_ID:-null}" --command gsd-t-resume --step 2 --step-label "Determine Current Position" 2>/dev/null || true
+```
+
 From the continue-here file (if present) OR progress.md (or conversation context if same-session), identify:
 - Current milestone and status
 - Which phase we're in
@@ -129,6 +157,10 @@ From the continue-here file (if present) OR progress.md (or conversation context
 
 ## Step 3: Report and Continue
 
+```bash
+node scripts/gsd-t-watch-state.js advance --agent-id "$GSD_T_AGENT_ID" --parent-id "${GSD_T_PARENT_AGENT_ID:-null}" --command gsd-t-resume --step 3 --step-label "Report and Continue" 2>/dev/null || true
+```
+
 **Level 3 (Full Auto)**: Log a brief status line and auto-resume from the current task/phase. Do NOT wait for user input.
 
 ```
@@ -154,6 +186,10 @@ Ready to continue? Or run /gsd-t-status for full details.
 
 ## Step 4: Continue
 
+```bash
+node scripts/gsd-t-watch-state.js advance --agent-id "$GSD_T_AGENT_ID" --parent-id "${GSD_T_PARENT_AGENT_ID:-null}" --command gsd-t-resume --step 4 --step-label "Continue" 2>/dev/null || true
+```
+
 If $ARGUMENTS specifies what to do next, proceed with that.
 Otherwise, pick up from the logical next action based on current state:
 - Mid-execution → Continue with next unblocked task
@@ -163,6 +199,10 @@ Otherwise, pick up from the logical next action based on current state:
 
 ## Step 5: Auto-Advance Through End of Milestone (MANDATORY)
 
+```bash
+node scripts/gsd-t-watch-state.js advance --agent-id "$GSD_T_AGENT_ID" --parent-id "${GSD_T_PARENT_AGENT_ID:-null}" --command gsd-t-resume --step 5 --step-label "Auto-Advance Through End of Milestone (MANDATORY)" 2>/dev/null || true
+```
+
 **Resume does NOT stop at the end of a wave or phase. It must chain all the way to `COMPLETED` status.**
 
 When the resumed work reaches a natural handoff point, do NOT print a "Next Up" hint and wait for the user. At Level 3 Full Auto, keep going. The successor mapping in CLAUDE-global.md is the contract — resume honors it exactly like any other command:

package/commands/gsd-t-scan.md

@@ -17,6 +17,10 @@ Default path is `autoSpawnHeadless({command, spawnType, watch: WATCH_FLAG, proje
 
 ## Step 0: Launch via Subagent
 
+```bash
+node scripts/gsd-t-watch-state.js advance --agent-id "$GSD_T_AGENT_ID" --parent-id "${GSD_T_PARENT_AGENT_ID:-null}" --command gsd-t-scan --step 0 --step-label "Launch via Subagent" 2>/dev/null || true
+```
+
 Scans are long-running and context-heavy. Always execute via a Task subagent for a fresh context window.
 
 **If you are the orchestrating agent** (you received the slash command directly):
@@ -36,6 +40,10 @@ Continue to Step 1 below. At Step 2, use team mode — spawn the 5 teammates in
 
 ## Step 1: Load Existing Context
 
+```bash
+node scripts/gsd-t-watch-state.js advance --agent-id "$GSD_T_AGENT_ID" --parent-id "${GSD_T_PARENT_AGENT_ID:-null}" --command gsd-t-scan --step 1 --step-label "Load Existing Context" 2>/dev/null || true
+```
+
 Read:
 1. `CLAUDE.md` (if exists)
 2. `.gsd-t/progress.md` (if exists)
@@ -45,6 +53,10 @@ Read:
 
 ## Step 1.5: Graph Index (if available)
 
+```bash
+node scripts/gsd-t-watch-state.js advance --agent-id "$GSD_T_AGENT_ID" --parent-id "${GSD_T_PARENT_AGENT_ID:-null}" --command gsd-t-scan --step 1 --step-label ".5: Graph Index (if available)" 2>/dev/null || true
+```
+
 Before scanning, check if `bin/graph-indexer.js` exists in the GSD-T installation or if `.gsd-t/graph/meta.json` exists in the project. If so:
 
 ```bash
@@ -63,6 +75,10 @@ Pass the graph query results to each teammate in their prompt context so they ca
 
 ## Step 2: Full Codebase Scan
 
+```bash
+node scripts/gsd-t-watch-state.js advance --agent-id "$GSD_T_AGENT_ID" --parent-id "${GSD_T_PARENT_AGENT_ID:-null}" --command gsd-t-scan --step 2 --step-label "Full Codebase Scan" 2>/dev/null || true
+```
+
 **Always use Team Mode** unless the codebase is trivially small (< 5 files) or agent teams are explicitly disabled. Each dimension is fully independent — parallel scanning is faster and produces better results.
 
 ```
@@ -283,6 +299,10 @@ Produce: `.gsd-t/scan/contract-drift.md`
 
 ## Step 2.5: Schema Extraction
 
+```bash
+node scripts/gsd-t-watch-state.js advance --agent-id "$GSD_T_AGENT_ID" --parent-id "${GSD_T_PARENT_AGENT_ID:-null}" --command gsd-t-scan --step 2 --step-label ".5: Schema Extraction" 2>/dev/null || true
+```
+
 Run schema extraction on the scanned project to detect ORM/database schema files and parse entity definitions. This data feeds the database schema diagram in Step 3.5.
 
 Using Bash tool:
@@ -298,6 +318,10 @@ If `schemaData.detected === false`, note: "No ORM/schema files detected — data
 
 ## Step 2.9: Archive Previous Tech Debt Register
 
+```bash
+node scripts/gsd-t-watch-state.js advance --agent-id "$GSD_T_AGENT_ID" --parent-id "${GSD_T_PARENT_AGENT_ID:-null}" --command gsd-t-scan --step 2 --step-label ".9: Archive Previous Tech Debt Register" 2>/dev/null || true
+```
+
 Before building the new register, archive the existing one so the file stays small. Each scan is a complete snapshot — the archive preserves history.
 
 If `.gsd-t/techdebt.md` exists:
@@ -309,6 +333,10 @@ The new `techdebt.md` created in Step 3 will contain only the current scan's fin
 
 ## Step 3: Build Tech Debt Register
 
+```bash
+node scripts/gsd-t-watch-state.js advance --agent-id "$GSD_T_AGENT_ID" --parent-id "${GSD_T_PARENT_AGENT_ID:-null}" --command gsd-t-scan --step 3 --step-label "Build Tech Debt Register" 2>/dev/null || true
+```
+
 Synthesize ALL findings into a **fresh** `.gsd-t/techdebt.md` (the previous version was archived in Step 2.9). This file contains only the current scan's findings — no resolved items table, no scan history. Previous scans are preserved in `techdebt_YYYY-MM-DD.md` archives.
 
 **Between scans:** when an item is fixed, change its `**Status**:` field to `[RESOLVED] — {brief reason/milestone}`. Do not delete the item — it stays visible until the next scan replaces the file.
@@ -399,6 +427,10 @@ Nice-to-haves and cleanup.
 
 ## Step 3.5: Diagram Generation
 
+```bash
+node scripts/gsd-t-watch-state.js advance --agent-id "$GSD_T_AGENT_ID" --parent-id "${GSD_T_PARENT_AGENT_ID:-null}" --command gsd-t-scan --step 3 --step-label ".5: Diagram Generation" 2>/dev/null || true
+```
+
 Generate all 6 architectural diagrams using analysis data from Step 2 and schema data from Step 2.5.
 
 Using Bash tool:
@@ -418,6 +450,10 @@ Capture the full array as `diagrams`. Log:
 
 ## Step 4: Suggest Milestone Promotions
 
+```bash
+node scripts/gsd-t-watch-state.js advance --agent-id "$GSD_T_AGENT_ID" --parent-id "${GSD_T_PARENT_AGENT_ID:-null}" --command gsd-t-scan --step 4 --step-label "Suggest Milestone Promotions" 2>/dev/null || true
+```
+
 Review all items marked `Milestone candidate: YES` and group them into logical milestones:
 
 ```markdown
@@ -447,6 +483,10 @@ Note: Use `/gsd-t-partition` Step 1.6 to design the SharedCore domain
 
 ## Step 5: Update Living Documents
 
+```bash
+node scripts/gsd-t-watch-state.js advance --agent-id "$GSD_T_AGENT_ID" --parent-id "${GSD_T_PARENT_AGENT_ID:-null}" --command gsd-t-scan --step 5 --step-label "Update Living Documents" 2>/dev/null || true
+```
+
 The scan produces deep analysis in `.gsd-t/scan/`. Now cross-populate findings into the living docs so knowledge persists across milestones.
 
 ### docs/architecture.md
@@ -505,6 +545,10 @@ If `README.md` exists, merge — update tech stack and setup sections but preser
 
 ## Step 6: Test Verification
 
+```bash
+node scripts/gsd-t-watch-state.js advance --agent-id "$GSD_T_AGENT_ID" --parent-id "${GSD_T_PARENT_AGENT_ID:-null}" --command gsd-t-scan --step 6 --step-label "Test Verification" 2>/dev/null || true
+```
+
 After updating living documents, verify nothing was broken:
 
 1. **Run existing tests**: Execute the full test suite to establish a baseline — document what passes and what was already failing
@@ -513,6 +557,10 @@ After updating living documents, verify nothing was broken:
 
 ## Step 6.5: Generate Scan Freshness Cache
 
+```bash
+node scripts/gsd-t-watch-state.js advance --agent-id "$GSD_T_AGENT_ID" --parent-id "${GSD_T_PARENT_AGENT_ID:-null}" --command gsd-t-scan --step 6 --step-label ".5: Generate Scan Freshness Cache" 2>/dev/null || true
+```
+
 After the scan completes and living docs are updated, generate a hash cache so downstream commands can detect staleness without re-scanning.
 
 Create `.gsd-t/scan/.cache.json` with this structure:
@@ -557,6 +605,10 @@ This cache enables downstream commands (`partition`, `feature`, `gap-analysis`)
 
 ## Step 7: Update Project State
 
+```bash
+node scripts/gsd-t-watch-state.js advance --agent-id "$GSD_T_AGENT_ID" --parent-id "${GSD_T_PARENT_AGENT_ID:-null}" --command gsd-t-scan --step 7 --step-label "Update Project State" 2>/dev/null || true
+```
+
 If `.gsd-t/progress.md` exists:
 - Log scan in Decision Log
 - Note critical findings
@@ -570,6 +622,10 @@ If `CLAUDE.md` exists:
 
 ## Step 8: Report to User
 
+```bash
+node scripts/gsd-t-watch-state.js advance --agent-id "$GSD_T_AGENT_ID" --parent-id "${GSD_T_PARENT_AGENT_ID:-null}" --command gsd-t-scan --step 8 --step-label "Report to User" 2>/dev/null || true
+```
+
 Present a summary:
 1. Architecture overview (brief)
 2. Business rules found (count + any undocumented ones)

package/commands/gsd-t-test-sync.md

@@ -15,6 +15,10 @@ This command is:
 
 ## Step 1: Load Context
 
+```bash
+node scripts/gsd-t-watch-state.js advance --agent-id "$GSD_T_AGENT_ID" --parent-id "${GSD_T_PARENT_AGENT_ID:-null}" --command gsd-t-test-sync --step 1 --step-label "Load Context" 2>/dev/null || true
+```
+
 Read:
 1. `CLAUDE.md` — testing conventions, test locations
 2. `.gsd-t/progress.md` — what just changed
@@ -30,6 +34,10 @@ Identify:
 
 ## Step 1.5: Graph-Enhanced Test Discovery
 
+```bash
+node scripts/gsd-t-watch-state.js advance --agent-id "$GSD_T_AGENT_ID" --parent-id "${GSD_T_PARENT_AGENT_ID:-null}" --command gsd-t-test-sync --step 1 --step-label ".5: Graph-Enhanced Test Discovery" 2>/dev/null || true
+```
+
 If `.gsd-t/graph/meta.json` exists (graph index is available):
 1. Query `getTestsFor` each changed entity to find stale or missing tests more precisely than filesystem search
 2. Query `getTransitiveCallers` for changed functions to find indirectly affected tests that may need updating
@@ -39,6 +47,10 @@ If graph is not available, skip this step.
 
 ## Step 2: Contract Coverage Audit
 
+```bash
+node scripts/gsd-t-watch-state.js advance --agent-id "$GSD_T_AGENT_ID" --parent-id "${GSD_T_PARENT_AGENT_ID:-null}" --command gsd-t-test-sync --step 2 --step-label "Contract Coverage Audit" 2>/dev/null || true
+```
+
 Perform inline contract testing and gap analysis:
 
 1. Read all contracts in `.gsd-t/contracts/` — identify the interface each one defines
@@ -51,6 +63,10 @@ Test-sync cannot complete if critical contract gaps remain unaddressed.
 
 ## Step 3: Map Code to Tests
 
+```bash
+node scripts/gsd-t-watch-state.js advance --agent-id "$GSD_T_AGENT_ID" --parent-id "${GSD_T_PARENT_AGENT_ID:-null}" --command gsd-t-test-sync --step 3 --step-label "Map Code to Tests" 2>/dev/null || true
+```
+
 For each file changed in recent tasks:
 
 ### A) Find Existing Tests
@@ -73,6 +89,10 @@ find . -name "*.spec.*" | xargs grep -l "{class_name}"
 
 ## Step 4: Detect Test Issues
 
+```bash
+node scripts/gsd-t-watch-state.js advance --agent-id "$GSD_T_AGENT_ID" --parent-id "${GSD_T_PARENT_AGENT_ID:-null}" --command gsd-t-test-sync --step 4 --step-label "Detect Test Issues" 2>/dev/null || true
+```
+
 ### A) Stale Tests
 Tests that reference old behavior:
 - Function signatures that changed
@@ -107,6 +127,10 @@ Tests that sometimes fail:
 
 ## Step 5: Run Affected Tests
 
+```bash
+node scripts/gsd-t-watch-state.js advance --agent-id "$GSD_T_AGENT_ID" --parent-id "${GSD_T_PARENT_AGENT_ID:-null}" --command gsd-t-test-sync --step 5 --step-label "Run Affected Tests" 2>/dev/null || true
+```
+
 ### A) Unit/Integration Tests
 Execute tests that cover changed code:
 
@@ -187,6 +211,10 @@ For all test types:
 
 ## Step 6: Produce Test Coverage Report
 
+```bash
+node scripts/gsd-t-watch-state.js advance --agent-id "$GSD_T_AGENT_ID" --parent-id "${GSD_T_PARENT_AGENT_ID:-null}" --command gsd-t-test-sync --step 6 --step-label "Produce Test Coverage Report" 2>/dev/null || true
+```
+
 Create/update `.gsd-t/test-coverage.md`:
 
 ```markdown
@@ -274,6 +302,10 @@ Create/update `.gsd-t/test-coverage.md`:
 
 ## Step 7: Generate Test Tasks
 
+```bash
+node scripts/gsd-t-watch-state.js advance --agent-id "$GSD_T_AGENT_ID" --parent-id "${GSD_T_PARENT_AGENT_ID:-null}" --command gsd-t-test-sync --step 7 --step-label "Generate Test Tasks" 2>/dev/null || true
+```
+
 If issues found, add to current domain's tasks:
 
 ```markdown
@@ -297,6 +329,10 @@ If issues found, add to current domain's tasks:
 
 ## Step 8: Integration with Workflow
 
+```bash
+node scripts/gsd-t-watch-state.js advance --agent-id "$GSD_T_AGENT_ID" --parent-id "${GSD_T_PARENT_AGENT_ID:-null}" --command gsd-t-test-sync --step 8 --step-label "Integration with Workflow" 2>/dev/null || true
+```
+
 ### During Execute Phase (auto-invoked):
 After each task completes:
 1. Scan changed files and map to existing tests
@@ -331,6 +367,10 @@ Full sync:
 
 ## Step 9: Report to User
 
+```bash
+node scripts/gsd-t-watch-state.js advance --agent-id "$GSD_T_AGENT_ID" --parent-id "${GSD_T_PARENT_AGENT_ID:-null}" --command gsd-t-test-sync --step 9 --step-label "Report to User" 2>/dev/null || true
+```
+
 ### Quick Mode (during execute):
 ```
 🧪 Test sync: 3 tests affected, 3 passing

package/commands/gsd-t-unattended-watch.md

@@ -347,7 +347,7 @@ const fs = require('fs');
 let state = {};
 try { state = JSON.parse(fs.readFileSync('.gsd-t/.unattended/state.json','utf8')); } catch(_){}
 const { events, newCursor } = es.readSinceCursor('.');
-console.log(wf.formatWatchTick({ events, state }));
+console.log(wf.formatWatchTick({ events, state, withWatchProgress: true }));
 es.advanceCursor('.', newCursor);
 "
 ```

package/commands/gsd-t-unattended.md

@@ -10,6 +10,10 @@ See `unattended-supervisor-contract.md` §7 (Launch Handshake), §4 (Status Enum
 
 ## Step 1: Pre-Flight Checks
 
+```bash
+node scripts/gsd-t-watch-state.js advance --agent-id "$GSD_T_AGENT_ID" --parent-id "${GSD_T_PARENT_AGENT_ID:-null}" --command gsd-t-unattended --step 1 --step-label "Pre-Flight Checks" 2>/dev/null || true
+```
+
 ### 1a: Verify GSD-T Project
 
 Run via Bash:
@@ -247,6 +251,10 @@ If `WARNINGS` were emitted, print them as a non-blocking advisory before proceed
 
 ## Step 2: Spawn the Detached Supervisor
 
+```bash
+node scripts/gsd-t-watch-state.js advance --agent-id "$GSD_T_AGENT_ID" --parent-id "${GSD_T_PARENT_AGENT_ID:-null}" --command gsd-t-unattended --step 2 --step-label "Spawn the Detached Supervisor" 2>/dev/null || true
+```
+
 ⚙ [sonnet] gsd-t-unattended → spawning detached supervisor
 
 **Before spawn — read starting context tokens (observability bracket):**
@@ -323,6 +331,10 @@ fs.appendFileSync(LOG, row);
 
 ## Step 3: Verify Supervisor Liveness
 
+```bash
+node scripts/gsd-t-watch-state.js advance --agent-id "$GSD_T_AGENT_ID" --parent-id "${GSD_T_PARENT_AGENT_ID:-null}" --command gsd-t-unattended --step 3 --step-label "Verify Supervisor Liveness" 2>/dev/null || true
+```
+
 Wait up to 2 seconds for the supervisor to write its PID file and transition out of `initializing`:
 
 ```bash
@@ -400,6 +412,10 @@ End the turn without scheduling a watch tick.
 
 ## Step 4: Display Initial Status Block
 
+```bash
+node scripts/gsd-t-watch-state.js advance --agent-id "$GSD_T_AGENT_ID" --parent-id "${GSD_T_PARENT_AGENT_ID:-null}" --command gsd-t-unattended --step 4 --step-label "Display Initial Status Block" 2>/dev/null || true
+```
+
 Print the launch confirmation block:
 
 ```
@@ -421,6 +437,10 @@ Print the launch confirmation block:
 
 ## Step 5: Schedule the First Watch Tick
 
+```bash
+node scripts/gsd-t-watch-state.js advance --agent-id "$GSD_T_AGENT_ID" --parent-id "${GSD_T_PARENT_AGENT_ID:-null}" --command gsd-t-unattended --step 5 --step-label "Schedule the First Watch Tick" 2>/dev/null || true
+```
+
 Call the harness `ScheduleWakeup` tool with these exact parameters:
 
 - `delaySeconds`: `270` (fixed — inside the 5-minute prompt-cache TTL)

package/commands/gsd-t-verify.md

@@ -23,6 +23,10 @@ Per `.gsd-t/contracts/model-selection-contract.md` v1.0.0.
 
 ## Step 1: Load State
 
+```bash
+node scripts/gsd-t-watch-state.js advance --agent-id "$GSD_T_AGENT_ID" --parent-id "${GSD_T_PARENT_AGENT_ID:-null}" --command gsd-t-verify --step 1 --step-label "Load State" 2>/dev/null || true
+```
+
 Read:
 1. `CLAUDE.md`
 2. `.gsd-t/progress.md` — confirm status is INTEGRATED
@@ -33,6 +37,10 @@ Read:
 
 ## Step 1.5: Graph-Enhanced Traceability Check
 
+```bash
+node scripts/gsd-t-watch-state.js advance --agent-id "$GSD_T_AGENT_ID" --parent-id "${GSD_T_PARENT_AGENT_ID:-null}" --command gsd-t-verify --step 1 --step-label ".5: Graph-Enhanced Traceability Check" 2>/dev/null || true
+```
+
 If `.gsd-t/graph/meta.json` exists (graph index is available):
 1. Query `getRequirementFor` on implemented entities to build a requirement-to-code traceability chain — flag entities with no requirement mapping
 2. Query `getDomainBoundaryViolations` to verify no cross-domain boundary violations exist in the final codebase
@@ -42,6 +50,10 @@ If graph is not available, skip this step.
 
 ## Step 2: Full Test Audit (Inline)
 
+```bash
+node scripts/gsd-t-watch-state.js advance --agent-id "$GSD_T_AGENT_ID" --parent-id "${GSD_T_PARENT_AGENT_ID:-null}" --command gsd-t-verify --step 2 --step-label "Full Test Audit (Inline)" 2>/dev/null || true
+```
+
 Run the full test audit directly:
 
 1. Run the full test suite: `npm test` (or project equivalent) — record pass/fail counts
@@ -54,6 +66,10 @@ Verification cannot complete if any test fails or critical contract gaps remain.
 
 ## Step 2.5: High-Risk Domain Gate (MANDATORY — Categories 2 and 7)
 
+```bash
+node scripts/gsd-t-watch-state.js advance --agent-id "$GSD_T_AGENT_ID" --parent-id "${GSD_T_PARENT_AGENT_ID:-null}" --command gsd-t-verify --step 2 --step-label ".5: High-Risk Domain Gate (MANDATORY — Categories 2 and 7)" 2>/dev/null || true
+```
+
 Before running standard verification dimensions, check whether this milestone involves any high-risk domain:
 
 **High-risk domains**: audio capture/playback, GPU/WebGPU/WebGL, ML/inference/model loading, background workers, native APIs (camera, bluetooth, filesystem), IPC, WebAssembly, real-time data streams.
@@ -85,6 +101,10 @@ For each such feature:
 
 ## Step 3: Define Verification Dimensions
 
+```bash
+node scripts/gsd-t-watch-state.js advance --agent-id "$GSD_T_AGENT_ID" --parent-id "${GSD_T_PARENT_AGENT_ID:-null}" --command gsd-t-verify --step 3 --step-label "Define Verification Dimensions" 2>/dev/null || true
+```
+
 Standard dimensions (adjust based on project):
 
 1. **Functional Correctness**: Does it work per requirements?
@@ -115,6 +135,10 @@ Standard dimensions (adjust based on project):
 
 ## Step 4: Execute Verification
 
+```bash
+node scripts/gsd-t-watch-state.js advance --agent-id "$GSD_T_AGENT_ID" --parent-id "${GSD_T_PARENT_AGENT_ID:-null}" --command gsd-t-verify --step 4 --step-label "Execute Verification" 2>/dev/null || true
+```
+
 ### Solo Mode (default)
 Work through each dimension sequentially. For each:
 1. Define what you're checking
@@ -188,6 +212,10 @@ Collect all reports, synthesize, create remediation plan.
 
 ## Step 5: Compile Verification Report
 
+```bash
+node scripts/gsd-t-watch-state.js advance --agent-id "$GSD_T_AGENT_ID" --parent-id "${GSD_T_PARENT_AGENT_ID:-null}" --command gsd-t-verify --step 5 --step-label "Compile Verification Report" 2>/dev/null || true
+```
+
 Create or update `.gsd-t/verify-report.md`:
 
 ```markdown
@@ -226,6 +254,10 @@ Create or update `.gsd-t/verify-report.md`:
 
 ## Step 5.25: Metrics Quality Budget Check
 
+```bash
+node scripts/gsd-t-watch-state.js advance --agent-id "$GSD_T_AGENT_ID" --parent-id "${GSD_T_PARENT_AGENT_ID:-null}" --command gsd-t-verify --step 5 --step-label ".25: Metrics Quality Budget Check" 2>/dev/null || true
+```
+
 Check task-metrics for the current milestone to detect quality budget violations:
 
 1. Run via Bash:
@@ -241,6 +273,10 @@ Check task-metrics for the current milestone to detect quality budget violations
 
 ## Step 5.5: Goal-Backward Verification (Post-Gate Behavior Check)
 
+```bash
+node scripts/gsd-t-watch-state.js advance --agent-id "$GSD_T_AGENT_ID" --parent-id "${GSD_T_PARENT_AGENT_ID:-null}" --command gsd-t-verify --step 5 --step-label ".5: Goal-Backward Verification (Post-Gate Behavior Check)" 2>/dev/null || true
+```
+
 This step runs **after all 8 quality gates pass**. It verifies that milestone goals are actually achieved end-to-end — not just structurally present. It catches placeholder implementations that pass all structural gates.
 
 Refer to `.gsd-t/contracts/goal-backward-contract.md` for the full verification flow, placeholder patterns, and findings report format.
@@ -315,6 +351,10 @@ Add a `Goal-Backward:` line to the Step 5 verification report summary:
 
 ## Step 6: Handle Remediation
 
+```bash
+node scripts/gsd-t-watch-state.js advance --agent-id "$GSD_T_AGENT_ID" --parent-id "${GSD_T_PARENT_AGENT_ID:-null}" --command gsd-t-verify --step 6 --step-label "Handle Remediation" 2>/dev/null || true
+```
+
 If there are CRITICAL findings:
 1. Create remediation tasks in the affected domain's `tasks.md`
 2. Execute fixes (solo — don't spawn teams for remediation)
@@ -323,6 +363,10 @@ If there are CRITICAL findings:
 
 ## Step 7: Update State
 
+```bash
+node scripts/gsd-t-watch-state.js advance --agent-id "$GSD_T_AGENT_ID" --parent-id "${GSD_T_PARENT_AGENT_ID:-null}" --command gsd-t-verify --step 7 --step-label "Update State" 2>/dev/null || true
+```
+
 Update `.gsd-t/progress.md`:
 - If all PASS: Set status to `VERIFIED`
 - If CONDITIONAL PASS: Set status to `VERIFIED-WITH-WARNINGS`, list warnings
@@ -353,6 +397,10 @@ Update `.gsd-t/progress.md`:
 
 ## Step 8: Auto-Invoke Complete-Milestone
 
+```bash
+node scripts/gsd-t-watch-state.js advance --agent-id "$GSD_T_AGENT_ID" --parent-id "${GSD_T_PARENT_AGENT_ID:-null}" --command gsd-t-verify --step 8 --step-label "Auto-Invoke Complete-Milestone" 2>/dev/null || true
+```
+
 **This step is MANDATORY and runs at ALL autonomy levels.** Completing a verified milestone is a mechanical operation (archive, tag, bump version, update docs). There is no decision that benefits from user review — the decision was made when verification passed.
 
 If status is VERIFY-FAILED: