docs(llm-security): v8 Phase 2 — B10 docs consistency, counts pinned by test

Extends tests/lib/doc-consistency.test.mjs with 15 cases that derive every
inventory count from source instead of trusting prose. Each count has one
stated derivation; a doc surface that disagrees now fails the suite.

Counts corrected (all were wrong before the test existed):
- orchestrated scanners: docs said 10 (README, ci-cd-guide), CLAUDE.md said 12,
  the synthesizer agent said 9 — scan-orchestrator registers 14
- total scanners: README badge + 3 prose sites said 23; the counting rule in
  docs/scanner-reference.md (14 orchestrated + 8 standalone) yields 22
- knowledge files: README badge + prose said 22; knowledge/ holds 23
- output.mjs finding() prefix JSDoc listed 10 of the 17 prefixes actually
  passed to it (missing IDE, MCI, MEM, PST, SCR, TFA, WFL)
- norwegian-context.md said "8 hooks, 10 scanners" -> 9 and 14
- ci-cd-guide "what gets scanned" table listed 10 of 14 rows; adds workflow,
  trigger abuse, signature, AST taint

Two plan items changed after verifying against ground truth:
- CLAUDE.md's synthesizer "(12 scanners)" was not a deliberate subset; the
  agent file itself claimed 9. Both bumped to 14.
- compliance-mapping.md's "13 posture categories" is substantively correct —
  its matrix has exactly 13 data rows, and categories 14-16 are governance
  consumers of the file, not rows in it. The planned 13->16 bump would have
  made the document false. Wording clarified to "code-level" instead, and the
  test now pins row count against the stated claim.

Framework currency (both verified against primary reporting):
- EU AI Act: Digital Omnibus (EP 2026-06-16, Council 2026-06-29) deferred the
  high-risk obligations behind Art. 9/15 to 2027-12-02 (Annex III) and
  2028-08-02 (Annex I); transparency still applies from 2026-08-02
- OWASP Agentic AI Top 10 labelled as the 2026 edition

Also: CLAUDE.md Distribution section rewritten monorepo -> polyrepo (each
plugin is its own repo; the catalog pins url + ref per plugin), and
current-state test counts synced 2013 -> 2034. Release-note paragraphs keep
their historical numbers.

No scanner, hook, or command behaviour changes. Suite 2034/2034.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Wt4YQGoXwRja5K2Zmv8RZE

CLAUDE.md

@@ -1,6 +1,6 @@
 # LLM Security Plugin (v7.8.3)
 
-Security scanning, auditing, and threat modeling for Claude Code projects. 5 frameworks: OWASP LLM Top 10, Agentic AI Top 10 (ASI), Skills Top 10 (AST), MCP Top 10, AI Agent Traps (DeepMind). 2013+ unit, integration, and end-to-end tests (`tests/e2e/` covers the multi-hook attack chain, multi-session state simulation, and the full scan-orchestrator pipeline); mutation-testing coverage not published.
+Security scanning, auditing, and threat modeling for Claude Code projects. 5 frameworks: OWASP LLM Top 10, Agentic AI Top 10 (ASI, 2026 edition), Skills Top 10 (AST), MCP Top 10, AI Agent Traps (DeepMind). 2034+ unit, integration, and end-to-end tests (`tests/e2e/` covers the multi-hook attack chain, multi-session state simulation, and the full scan-orchestrator pipeline); mutation-testing coverage not published.
 
 Release notes for v7.0.0 → v7.8.2: see `docs/version-history.md` — read on demand.
 
@@ -51,7 +51,7 @@ Release notes for v7.0.0 → v7.8.2: see `docs/version-history.md` — read on d
 | `mcp-scanner-agent` | 5-phase MCP server analysis | opus |
 | `posture-assessor-agent` | Full audit narrative (posture-scanner.mjs handles quick mode) | opus |
 | `threat-modeler-agent` | STRIDE x MAESTRO interview | opus |
-| `deep-scan-synthesizer-agent` | Scanner JSON → human-readable report (12 scanners) | opus |
+| `deep-scan-synthesizer-agent` | Scanner JSON → human-readable report (14 scanners) | opus |
 | `cleaner-agent` | Semi-auto remediation proposals | opus |
 
 ## Hooks (9)
@@ -90,12 +90,14 @@ Post-clone: size check (100MB max), cleanup guarantee (temp dir + evidence file
 
 ## Distribution
 
-This plugin lives in the `ktg-plugin-marketplace` monorepo at `https://git.fromaitochitta.com/open/ktg-plugin-marketplace` under `plugins/llm-security/`. It is not published as a standalone repo — users install it via the Claude Code marketplace mechanism:
+This plugin is its own repository at `https://git.fromaitochitta.com/open/llm-security`. It is distributed through the `ktg-plugin-marketplace` catalog, which is a **polyrepo**: the catalog (`catalog/.claude-plugin/marketplace.json`) holds no plugin source, only a `url` + `ref` pin per plugin, and each plugin repo is released independently by tag. Users install via the Claude Code marketplace mechanism:
 
 ```bash
 claude plugin marketplace add https://git.fromaitochitta.com/open/ktg-plugin-marketplace.git
 ```
 
+A version bump is therefore two-sided: tag `vX.Y.Z` in this repo, then bump the catalog's `ref` to the same tag.
+
 Issues, bug reports, and security disclosures all route to the marketplace repo.
 
 ## State