Inert UI elements from unsubscribed store slice + unthreaded optional callback (React/[REDACTED])

Three clickable-looking UI elements in a React/[REDACTED] + R3F splash app ("[REDACTED]") appeared inert. Investigation classified each: (1) a record-row click meant to hijack the anchor role, (2) a root-cause "chip" meant to filter a WebGL lattice, (3) post-lock "attestation" (locked-record) items that look clickable. Symptom: clicking the chip and the locked items produced no perceptible effect even though a click handler existed. Traced handlers to source and drove the live build with [REDACTED] real trusted wheel/click (synthetic WheelEvents do not advance the wheel-driven beat machine). Findings: (1) Record click WORKS — wired twice (RecordRow.onClick -> onRecordClick -> bloomRecord AND a delegated useClickBloom listener on the scene root). Live: clicking a flood-beat row set that exact record as the anchor hero. Not inert. (2) Chip: onClick calls store.filterChip(slug) which sets [REDACTED]. A grep for every consumer of [REDACTED] showed the ONLY subscriber is the DOM wall's getRowState (adds an is-dim class to non-matching pour rows). The [REDACTED] receives only beat/beatProgress/anchoredRecordId/latticeEnabled — it never reads filters, so the spec'd "lattice filters to that root cause" is unimplemented. Worse, at every beat where the chip is actually interactive the pour rows are already dimmed, so the class churn is imperceptible. aria-pressed did flip true live, proving the handler fires. (3) Locked "attestation" items have onClick -> onFocus?.(record), but onFocus comes from an optional onRecordFocus prop that the host ([REDACTED]) never passes to OracleWall, so it is always undefined and the click is a guaranteed no-op. CSS still sets cursor:pointer + tabIndex=0, so they LOOK clickable. Spec only ever calls these "focus/inspect, no navigation" — no click behavior was specified.