Reconcile public capability counts with the enforced catalog

[sodejm]

Follow-up to [E01.02] Reconcile advertised and implemented capabilities from the acceptance audit of issues closed September 28–October 5, 2026.

Audited source: d090c6ad51e65ae739b247a55733390c38a5d5bd on main. This issue covers only the unmet criteria below; delivered behavior remains credited.

Unmet original acceptance criteria

Criterion 1: Reconcile the verified baseline of 13 plugins and 18 specialist profiles against catalog and documentation, removing stale package counts.

Stale documentation: Runtime enforcement contains 14 plugins, 18 profiles, and 37 scenarios. Public and contributor documentation still advertises 13 plugins and 32 scenarios.

Source evidence

• cops/capabilities/auditor.py:253-268 — Runtime truth check enforces the current 14 plugins, 18 profiles and 37 scenarios.
• docs/CAPABILITIES.md:44-44 — Still advertises 63 capabilities: 13 plugins, 18 profiles, 32 scenarios.
• docs/contributing.md:99-99 — Still says checks run across all 13 plugins.
• docs/index.md:46-46 — Still says list all 13 plugins.
• docs/getting-started.md:36-36 — Still repeats 13-plugin counts.

Acceptance criteria for this follow-up

• Reconcile affected user/contributor docs with the verified catalog counts (14 plugins, 18 profiles, 37 scenarios at the audited commit).
• Add a focused consistency check or generated count source so future catalog changes cannot leave these public counts stale.
• Run the focused acceptance checks and make check; update affected documentation, or record a concrete rationale if the change is solely acceptance-test coverage.

Validation and duplicate review

The clean audited Git checkout passed make check. That validates the existing suite, not the missing acceptance cases identified here. The audit used source inspection and offline/inert tests; it does not claim live assessment or deployment evidence.

The 66 open issues were reviewed before creation; no existing issue covers this exact remaining scope.