docs: land approved Plan: Gamma Dev Spec + phases-waves.json on main

[bakeb7j0]

Summary

Commit the approved Plan: Gamma Dev Spec (docs/ccwork-testtarget-devspec.md), the fresh phases-waves.json execution input, and the archived prior Plan #607 state to main. Pre-/prepwaves 641 landing — so the Dev Spec lives on main with its <!-- DEV-SPEC-APPROVAL approved=true --> metadata baked in, and /wavemachine has a stable on-disk reference when it spins up KAHUNA.

Target audience: Designers/developers about to run /prepwaves and /wavemachine for Plan: Gamma; auditors verifying the Dev Spec's approval metadata.

Source material: /devspec walk on Plan #641 in this session producing 61 ledger entries (D-001 through D-061); /devspec finalize 8/8 pass; /devspec approve by BJ on 2026-05-08T05:02:58Z; /devspec upshift creating 21 Story issues Wave-Engineering/ccwork-testtarget#1 through #21.

Implementation Steps

1. Branch off main: docs/<N>-plangamma-devspec where <N> is this issue's number.
2. Verify the working-tree artifacts to be committed:
   • docs/ccwork-testtarget-devspec.md (new, ~1700 lines, includes DEV-SPEC-APPROVAL block + §8 backfilled with (#1)–(#21))
   • .claude/status/phases-waves.json (new — plan_id: 641, slug: ccwork-testtarget, 21 Stories, both Phases marked cross_repo: true with target_repos: ["Wave-Engineering/ccwork-testtarget"])
   • .claude/status/.archive-20260508-011730-pre-gamma/phases-waves.json (archived prior Plan Plan: Beta — Wave-pattern reliability + autonomy hardening (operational backlog campaign B) #607 state)
3. Run /precheck (IBM gate, validation, code-reviewer, trivy).
4. After approval, run /scpmmr — auto-merge through merge queue, target main.

Test Procedures

Verification:

• Markdown lint passes on docs/ccwork-testtarget-devspec.md
• All cross-references in the Dev Spec resolve (Epic #626, Plan #641, sketchbook PR #640, memory files referenced in Appendix B)
• phases-waves.json validates as JSON (jq . .claude/status/phases-waves.json)
• phases-waves.json plan_id field equals 641 (jq .plan_id)
• phases-waves.json story count equals 21 (jq '[.phases[].waves[].stories[]] | length')
• Every Story in phases-waves.json has a depends_on field (no missing fields)
• Every Story in phases-waves.json has an issue field linking to a Wave-Engineering/ccwork-testtarget issue number
• mcp__sdlc-server__devspec_finalize 8/8 still passes against the on-main file
• mcp__sdlc-server__devspec_verify_approved returns approved: true, approved_by: BJ
• Archive directory .claude/status/.archive-20260508-011730-pre-gamma/ exists and contains the prior phases-waves.json unchanged

Acceptance Criteria

• docs/ccwork-testtarget-devspec.md exists on main with <!-- DEV-SPEC-APPROVAL block intact (verified by grep -c DEV-SPEC-APPROVAL)
• .claude/status/phases-waves.json exists on main with plan_id: 641
• No residual prior-Plan phases-waves.json at the active path (only Plan: Gamma's)
• Archive directory preserved on main so the Plan Plan: Beta — Wave-pattern reliability + autonomy hardening (operational backlog campaign B) #607 historical record is auditable
• §8 Story headings in the Dev Spec all carry (#N) issue-number suffixes (21 of them)
• Issue #N (this one) auto-closes via PR's Closes #N linkage

Dependencies

None. Prerequisite (/devspec approve completing) was already satisfied in this session — the approval metadata block is already in the working-tree Dev Spec.

Metadata

Wave: N/A
Plan: N/A — pre-/prepwaves landing artifact for Plan #641's execution state; not part of any Phase or Wave under Plan: Gamma. (Plan: Gamma's Stories live in Wave-Engineering/ccwork-testtarget#1 through #21.)
Related:

• Plan: #641 — anchored Plan tracking issue
• Epic: #626 — parent (Plan: Gamma elaborates sub-issue feat: complete repo scaffolding — CI, settings, MCP, sync, dogfooding, releases, uninstall #1)
• Sketchbook PR: #640 — input artifact to /devspec
• Target repo: Wave-Engineering/ccwork-testtarget — where Plan: Gamma's Stories execute