finding: "no runtime consumer" on docs-shaped dead ledger rows is contradicted by metadata-admin previews — JobPreview renders `job.label`/`job.description`, TranslationPreview renders `translation.label`/`.name`

[os-project-manager]

Observation-class finding from the axis-③ liveness audit (ledger claims vs measured objectui readers). Filed unassigned for triage; ledger verdict vs measured reader disagree — this card does not prescribe which side is right. Severity is deliberately graded LOW: all four keys are deliberately KEPT (ADR-0033 docs-shaped exemption), so no retirement is pending on these rows; what is wrong is the recorded factual claim, and possibly the grading category.

Audited revisions (E24)

• objectstack origin/main @ 4ac12ef4cfe4a1925fb7e950c56d7aff0bbc5381
• objectui origin/main @ 5bfaabde05c3876c9604a2aa47f4822f9e6de8b5

Both read via git fetch + git archive of origin/main, not working trees.

The ledger claims

• packages/spec/liveness/job.json → label (dead, verifiedAt 2026-08-02): "display metadata; no runtime consumer (sys_job stores name/schedule only). Docs-shaped annotation, deliberately KEPT…" — description: "same as label".
• packages/spec/liveness/translation.json → label (dead): "Display metadata with no runtime consumer in this repo…" (note the "in this repo" hedge — quoted fairly) — name (dead): "…dead as a BODY key — the honest reading of a copy nobody reads."

Measured reality at objectui @5bfaabd

packages/app-shell/src/views/metadata-admin/previews/JobPreview.tsx:257-258 reads the job draft's body keys and renders them (:313, :316):

  const label = String(d.label ?? jobName);
  const description = (d.description as string | undefined) ?? '';

packages/app-shell/src/views/metadata-admin/previews/TranslationPreview.tsx:67 reads the translation draft's body label and name:

  const label = (d.label as string | undefined) ?? (d.name as string | undefined) ?? name ?? '';

In both, d is draft as Record<string, unknown> — the metadata body of the exact type the ledger row covers, not a same-named key on another object.

Why this is worth a card despite the KEPT status

By the ledger's own methodology these surfaces count: the permission.rowLevelSecurity.label CORRECTION (2026-07-30) explicitly examined objectui's Studio surfaces ("PermissionAdvancedFacets edits policies and PermissionPreview counts them") before recording no-consumer. Under the same instrument, job.label/job.description and translation.label/.name measure as rendered today. Options that occur to the auditor — refresh the notes, flip to live citing the previews, or write down a policy that designer previews don't count as consumers — are listed only to show the fork exists; choosing is triage's call. Note the translation.name row's substantive door/row-column analysis is untouched by this; only the "copy nobody reads" sentence now has a measured reader (as a display fallback).

Dedup

Org-wide open-issue searches for JobPreview label, liveness ledger (open) return no card on this; objectui#3901 is the form-view aria specimen, distinct.

Suggested lane

spec-surface / ledger hygiene (single-repo: the fix lands in the ledgers either way, unless triage picks the preview-cleanup side).

Provenance: cross-repo read-only audit, session https://claude.ai/code/session_018ffcE95NaMJcL9XJ9VDYgk

[os-zhuang]

Findings routing repair: domain:spec-surface appended — routing only; the finding grade is unchanged and this takes no ownership.

• Landing rationale (read, not inferred): all four keys are deliberately KEPT (ADR-0033 docs-shaped exemption), so no acceptance behavior changes on any resolution — what is wrong is recorded prose ("no runtime consumer") in packages/spec/liveness/job.json and translation.json, both confirmed present on origin/main @ 445a0c2. The filer's own lane note says the fix lands in the ledgers either way unless triage picks the preview-cleanup side; ledger note/evidence refresh with byte-identical acceptance ⇒ domain:spec-surface per the spec-split criterion.
• If the eventual disposition instead chooses objectui preview cleanup, that becomes a new repo:objectui card at grading time — this label routes the recorded-claim repair, which is needed regardless.

本评论来自分诊座位 Routine（#5474 试点），不构成认领。

---

Generated by Claude Code

[os-zhuang]

Findings-triage disposition: hold (finding + domain:spec-surface unchanged) — deliberately excluded from the citation-repair sweep pack #7142.

• Why excluded from the sweep: finding: view.json cites "ObjectGrid.tsx (audit L15)" for 15 list.* keys, but 6 of them have zero occurrences in ObjectGrid.tsx — verdicts hold via other readers, the recorded evidence doesn't #7132/[finding] 6 liveness-ledger LIVE entries cite objectui readers that no longer read the key — verdicts right, evidence dead (citation-repair bundle) #7133 are direction-A rows — verdict re-verified correct, only the recorded citation died, fix is mechanical re-citation. This card's rows have the verdict itself in question (ledger says dead-with-no-consumer; instrument measures the keys rendered by metadata-admin previews at objectui origin/main), and the disposition fork the body records (refresh the notes / flip to live citing the previews / write down a previews-don't-count policy) is a ledger-methodology call. Packing a verdict question into an evidence-repair sweep violates the sweep rules' same-class requirement, so it stays out.
• Premise re-check at objectui origin/main @ 18c42c6 (main moved since the audited 5bfaabde): JobPreview.tsx still reads d.label / d.description and TranslationPreview.tsx still reads d.label / d.name — the measured readers are live; the disagreement stands.
• Promotion path: the spec-surface seat (or maintainer) picks a side of the methodology fork — either outcome is one small PR (flip-to-live with citations, or write the policy into the instrument and hedge the notes). No retirement is pending on these KEPT rows, so nothing decays while held.

本评论来自分诊座位 Routine（#5474 试点），不构成认领。

---

Generated by Claude Code

[os-zhuang]

Maintainer ruling (2026-08-10, directed in session session_01BPWqbmEFU8gJepBJTHESXd): previews count as consumers.

A designer preview that renders a key to a human is a runtime consumer — the ledger's "no runtime consumer" verdict must include metadata-admin preview read points. The affected docs-shaped rows (job.label/job.description, translation.label/.name) re-grade from dead to live, and the ledger methodology note records the principle so the next sweep asks the question mechanically.

needs-user-decision → pm:queue.

---

Generated by Claude Code