v0.11.1 — fix VERSION drift + prompts/skills alignment

v0.11.1 — fix VERSION drift + prompts/skills alignment (patch)

🐛 Fix: VERSION-file drift (shipped in v0.11.0)

v0.11.0 shipped with VERSION stuck at 0.10.0 while all other version files read 0.11.0 — sync-version.js omitted VERSION from its sync TARGETS, so every bump left it stale (failing the version-agreement invariant test). Fixed: VERSION is now a sync target (6 files synced); all version strings now agree at 0.11.1.

Align prompts 00-07 ↔ skills (closing the v3.13.0 gaps)

• Findings fixed status (07-reviewer, 06-verify-ship, standalone-artifact-writeback) — finding enum gains fixed (with fixed_in commit/task + fixed_at); 05/06 now write back fixed when code resolves a finding, and 06 reconciliation verifies fixed findings against actual code. Fixes "fixed in code but PRD/findings still show pending".
• Ship → ROADMAP sync (06-verify-ship, roadmap.md, csp-full P7, csp-shipping-and-launch) — release now syncs docs/strategy/ROADMAP.md status planned→released + backfills 实际交付 + manifest. Fixes ROADMAP/version milestone drift.
• Audit/lint scope ↔ PRD violation alignment (audit.md, csp-codebase-audit) — audit reconciles its detection scope with the PRD's violation definitions; mismatches surface as 口径漂移 findings instead of silently reporting under a different taxonomy. Fixes "lint scope ≠ PRD violation definition".
• lifecycle milestone↔version mapping (README schema, version-management.md) — milestone must be SemVer (v3.13.0), not a codename (M9-xxx); codename goes to milestone_name. Makes milestone/version/stage machine-resolvable.
• Skeleton-first gate + 02-04 skip hardening (01-prd, csp-full) — forbids writing production skeleton before PRD Approved (PRD is a spec, not a post-hoc record); tightens the lightweight skip to require PRD contains Feature+AC (skip 02) / data model+API (skip 03), else 02-04 must run.

Full Changelog: v0.11.0...v0.11.1