v1.15.10

Feat: OpenSpec Alignment — Capabilities Mapping, Onboard, MODIFIED Fix

Three gaps identified by comparing against Fission-AI/OpenSpec are now closed.

Gap #1: Capabilities Section in Proposals

Problem: The sdd-spec agent had to infer which spec files to create from the vague "Affected Areas" table.

Fix: Added an explicit ## Capabilities section to the proposal template with two sub-sections:

• New Capabilities → each becomes openspec/specs/<name>/spec.md (full new spec)
• Modified Capabilities → each becomes a delta spec in the change folder

The sdd-spec agent now reads this as a direct contract. Zero guessing.

Gap #4: sdd-onboard Skill

New skill that guides users through a complete SDD cycle using their real codebase — not a toy example. Narrated 10-phase flow:

1. Codebase scan for a small, safe improvement
2. Explore — investigate the area
3. Propose — write the proposal
4. Specs — write requirements and scenarios
5. Design — architecture decisions
6. Tasks — implementation checklist
7. Apply — write the code (with TDD if enabled)
8. Verify — compliance matrix check
9. Archive — merge deltas, close the change
10. Summary — recap and next steps

Registered in all 7 tool orchestrators (claude, cursor, windsurf, gemini, codex, antigravity, generic) and included in the init guard.

Gap #8: MODIFIED Requirements Copy-Full-Then-Edit

Problem: When writing ## MODIFIED Requirements deltas, the agent would write only the changed parts — causing the archive step to lose unchanged scenarios.

Fix: Added explicit workflow instruction in sdd-spec:

1. Locate the requirement in main spec
2. COPY the ENTIRE block (requirement + all scenarios)
3. PASTE under MODIFIED
4. EDIT the copy
5. Add "(Previously: ...)" note

Also added a CRITICAL rule: "MODIFIED requirements MUST be the FULL block."