docs(lexicon): split the alias evidence, correct a false absence claim

Advisor review found six gaps the session's own checks did not cover. The one
that mattered was outward-facing: the divergence report told the guard repo
that two sub-agent bounds were undocumented. That was wrong. lexicon.py's
module docstring documents them explicitly under "Bounded token gaps", and
git log -S dates {0,12} to the original port commit f397cd9 and [^><] to the
ReDoS fix cff0437. Every divergence on the guard's side is documented and
traceable. The claim rested on two sed slices of one file; an absence claim
needs a search over the whole repository. Corrected here and by coord.

lexicon/injection-lexicon.json 0.2.0 -> 0.3.0:

- pattern_id_space.alias_evidence records the two aliases separately instead
  of averaging them. llm_ingestion_guard is verified — coverage.py asserts on
  that exact string, so it is demonstrably what a guard finding carries.
  llm_security is not: it is the pattern table's name, the finding producer
  was never supplied, and the known Node finding shape uses title, not label.
- normalisations[].affects now keys on id, with the prose names kept beside it
  as affects_labels. An internal cross-reference on label was a second
  identity space inside the file the id exists to unify.

Detection data unmoved again: labels, patterns, flags and the ids and aliases
added in 7b70f5b are all byte-identical in sequence; 166/166 Node compiles.

Also: the README lexicon row described thematic families the file does not
have (they are severity families; the theme is the id prefix), and the
conformance convertibility table gained its missing second condition — a case
is buildable only if the label it asserts maps to data this repository
publishes. Eleven cases fail that test (entropy, decoded, the sanitize rows,
the OKF scans), so the buildable set is ~94, not 105.

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

CHANGELOG.md

@@ -53,6 +53,19 @@ checks that were not run instead of attaching a caveat to a pass.
 
 ### Changed
 
+- `lexicon/injection-lexicon.json` **0.2.0 → 0.3.0** — the two aliases are no longer presented
+  as equally backed. `pattern_id_space.alias_evidence` now records each one separately:
+  `llm_ingestion_guard` is **verified** (the guard's coverage matrix asserts on that exact
+  string, so it is demonstrably what a guard finding carries), while `llm_security` is
+  **not** — it is the pattern table's own name, and the finding producer was never supplied,
+  with the known Node finding shape using `title` rather than `label`. Averaging the two into
+  one file-level claim would have repeated the defect this repository corrects per-table
+  elsewhere.
+
+  Also: `normalisations[].affects` now keys on `id` with the prose names kept beside it as
+  `affects_labels`. An internal cross-reference on label was a second identity space inside
+  the file the id was added to unify.
+
 - `lexicon/injection-lexicon.json` **0.1.0 → 0.2.0** — every pattern gains a commons-owned
   `id` and an `aliases` object naming what each seeding runtime calls it, plus a top-level
   `pattern_id_space` block explaining the field. This exists because a `conformance/`