test(console,plugin-detail): re-pin the 17.5.0 population and book every new difference to its owner card, capped (objectui#11111 decision 3 = B, record 5902351047; objectui#11073)

The maintainer's ruling on objectui#11111 (record 5902351047, decision 3 = B):
the bump re-pins the guards' population and declares nothing (Clause ② no).
Every difference 17.5.0 newly surfaces is booked as a ledger entry naming its
owner card and an expiry. Each guard's empty ledger or zero cap becomes a
cap equal to the entries listed, never unbounded.

registry-inputs-spec-parity (Q10, was 23 red):
- Population re-pinned: specCarried 45 -> 55, judged 29 -> 35
  (MINOR_17_5_BLOCKS: action:button, action:group, action:icon, action:menu,
  element:definition-list, element:repeater), registeredPropless 7,
  ledgeredUnjudgeable 9 -> 13.
- UNJUDGED_SPEC_BLOCKS: object-gantt, object-map, object-timeline and
  object-tree, booked OWED to objectui#11168. That is a fourth reason class,
  rot-checked as "still registered lazily and unloaded here". The
  registered-but-unloaded mechanism test now expects exactly the booked
  entries, so a fifth is still red.
- Ledger entries, 73 in all:
  - unpublished keys: 57 (objectui#11168: action:button 22, action:icon 20,
    action:group 2, action:menu 2; objectui#8652: navigation on object-kanban
    and object-calendar; objectui#8649: the field-security triple on
    record:details, record:highlights and record:related_list);
  - refused input: 1 (action:group.name);
  - refused arms: 5 (action:group.actions:object, action:group.size:enum,
    action:menu.actions:object, element:definition-list.columns:enum,
    object-form.layout:enum);
  - owed member pins: 6 (action:group.actions, action:menu.actions,
    element:definition-list.items, element:repeater.fields/.filter/.sort).
- Caps: OBJECTUI_11111_LEDGER_CAPS (4 / 1 / 57 / 5 / 6), asserted exact by a
  new test that also routes each entry to its owner card, requires the
  ruling and the expiry in its reason, and pins the per-owner totals
  (objectui#11168: 62, objectui#8652: 2, objectui#8649: 9). The lazy-block
  backlog ceiling goes 0 -> 2 (exactly the navigation pair),
  MEMBER_PIN_EXEMPTION_CEILING goes 1 -> 7, and OFF_SPEC_EXEMPTIONS is pinned
  to exactly ['action:group.name'].

plugin-detail cast guards (Q9, were 2 red):
- 9965: HONEST_CASTS (already the triple) now names objectui#8649, the ruling
  and the expiry. The source-text guard subtracts it, capped at exactly the
  three.
- 9475: LOAD_BEARING_CASTS gains the triple, booked to objectui#8649 with its
  expiry. "The ledger is empty" becomes a pin of exactly those three.

Expiry: none of these ledgers has a date field, and the repo's SUNSET
convention is a condition, not a date. So "Expires 2026-10-30, or when the
owner card lands" is stated in every entry and asserted present, not
clock-enforced. Each guard's prose says why its ledger is non-empty, and
that the last owner card to land restores the empty ledger and cap 0.

Claude-Session: https://claude.ai/code/session_01TdiauJaVCHuj45EzZGUxHh
Co-authored-by: Claude <noreply@anthropic.com>

Author: claude