fix(sp-skill-catalog): correct plan count + soften SP-N header claim in cyclone-spec

.superpowers/skills/cyclone-spec/SKILL.md

@@ -10,7 +10,7 @@ a spec, a plan, an implementation branch, and a single atomic merge commit
 into `main`. This skill encodes the conventions so every increment follows
 the same shape and the commit history stays auditable.
 
-As of this writing: **16 specs** in `docs/superpowers/specs/`, **11 plans**
+As of this writing: **16 specs** in `docs/superpowers/specs/`, **12 plans**
 in `docs/superpowers/plans/`, and SP numbers used through **SP21** (the
 universal-drilldown design in progress). The next increment is **SP22**.
 
@@ -68,13 +68,18 @@ universal-drilldown design in progress). The next increment is **SP22**.
 
 ## Patterns
 
-### Spec header (every SP-N spec starts with this)
+### Spec header (canonical SP-N shape, post-SP9)
+
+This is the canonical header for new specs. Older specs (pre-SP9) deviate
+slightly — different title style, no Branch or Aesthetic direction line —
+and have not been retroactively normalized. **Use this template for any
+new SP-N spec.**
 
 ```markdown
 # Sub-project <N> — <Topic>: Design Spec
 
  **Date:** YYYY-MM-DD
- **Status:** Draft, pending user review
+ **Status:** Draft, awaiting user sign-off
  **Branch:** `sp<N>-<short-kebab-topic>`
  **Aesthetic direction:** <one line — e.g. "No new UI" or "Modern (geometric sans + bold borders + electric blue accent)">
 
@@ -82,8 +87,7 @@ universal-drilldown design in progress). The next increment is **SP22**.
  <2-6 lines: what's in, what's out, with explicit out-of-scope list>
 ```
 
-Real examples: `docs/superpowers/specs/2026-06-19-cyclone-db-reconciliation-design.md`,
-`docs/superpowers/specs/2026-06-20-cyclone-multi-payer-npi-sftp-design.md`.
+Worked example (matches this template): `docs/superpowers/specs/2026-06-20-cyclone-multi-payer-npi-sftp-design.md`.
 
 ### Plan header (every SP-N plan starts with this)