CLAUDE.md: ladder rendering + closed-tickets sweep

Three small fixes flagged by the whitepaper rewrite sweep:

1. Note the four-rung ladder render in the providence-cache layer
   description (audit_mode is schema-level; lattice modes display
   POINTER-LINKED → ANCHOR-WARRANTED → EVIDENCE-WARRANTED, with
   ENTAILMENT-VERIFIED reserved).

2. Add a Conventions entry for the ladder right after the three
   answer modes — names the rung discrimination rules, what each
   violation demotes to, and that quote/span/entity/paraphrase
   modes keep their original tokens.

3. Replace the 'Open tickets' section with a one-liner pointing to
   docs/TICKETS.md as authoritative; all five shipped tickets are
   closed as of 2026-05-02. The previous listing claimed #000001-3
   were open, which has been false since the prior session.

CLAUDE.md

@@ -20,6 +20,12 @@ Three layers stacked on one SQLite file:
 3. **Providence cache** — Q&A records keyed on the v9.8 8-dim
    invariant. Each record carries `audit_mode` (STRICT / HYBRID /
    UNGROUNDED) decided by the verifier in `aborist/qa/verify.py`.
+   For claim-lattice modes the renderer maps that token to a four-
+   rung ladder (POINTER-LINKED → ANCHOR-WARRANTED → EVIDENCE-WARRANTED;
+   ENTAILMENT-VERIFIED reserved); UNGROUNDED below all rungs. The
+   schema column stays unchanged — programmatic callers see the
+   trichotomy, human-facing surfaces see the ladder. See
+   `aborist/cli.py:_render_audit_label`.
 
 ## Source papers
 
@@ -143,6 +149,18 @@ revert without reading why. When in doubt, walk the
   + `json_fixups` disambiguate. Each mode folds into
   `governance_policy_hash`. See `aborist/qa/verify.py`,
   `docs/qa-modes-bench-2026-04-30.md`.
+- **Four-rung ladder (lattice-mode display layer)**: POINTER-LINKED
+  → ANCHOR-WARRANTED → EVIDENCE-WARRANTED → (ENTAILMENT-VERIFIED
+  reserved); UNGROUNDED below. Each rung names a strictly stronger
+  property the lexical verifier could confirm. WARRANT_MISSING drops
+  to POINTER-LINKED; soft-demote violations (LAZY_ANCHOR_DEMOTED,
+  POINTER_OVERFLOW_TRIMMED, TOO_MANY_CLAIMS, BARE_NAME_CLAIM,
+  TITLE_MISMATCH) cap at ANCHOR-WARRANTED. Quote / span / entity /
+  paraphrase modes keep their original audit_mode tokens (those
+  verify against pinned spans, not synthesis). Pure render-layer —
+  cache_key, governance_policy_hash, & all programmatic callers see
+  the underlying audit_mode unchanged. See
+  `aborist/cli.py:_render_audit_label`.
 - **Claim-lattice-pointer mode (G0 / CTI)**: runtime mints
   `pointer_id` (E1, E2, … — what the model sees) and content-addressed
   `evidence_id` (what the cache & run-DAG store). Renderer interpolates
@@ -311,15 +329,10 @@ Architecture / ongoing work:
   `docs/self-reference-distillation-design.md` — recursive distillation.
 - `docs/naming-deferral.md` — naming convention notes.
 
-Tickets: `docs/TICKETS.md` (index + Next ID). Open tickets:
-
-- `docs/ticket-000001-retrieval-keywords-audit-gap.md` — provenance
-  binding for `--retrieval-keywords`. Directive D4.
-- `docs/ticket-000002-reference-frame-polarity-contract.md` —
-  Module L: multi-frame answer compilation. Directive D3.
-- `docs/ticket-000003-anchor-class-warrant.md` — anchor-class
-  warrant generalization (entity-list / count / why-cause shapes).
-  Directive D6.
+Tickets: `docs/TICKETS.md` is the authoritative index with `Next
+ID`. As of 2026-05-02 all five shipped tickets (#000001–#000005)
+are closed; closed tickets stay in place as the design log. New
+tickets bump `Next ID` atomically.
 
 ## Orientation protocol