[finding] unregistered dogfood proof tag `admin-platform-admin-standing` — pre-existing check:liveness warning, recurrence of #10773's class

[os-litant]

Origin: pre-existing check:liveness warning observed by the os-dev run for #11457 (PR #12214) at its base commit 22c42c9 — present before that PR's changes, not introduced by them. Filed by the PM on the dev's behalf (recording only — unassigned, awaiting triage).

Symptom: the dogfood proof tag admin-platform-admin-standing is referenced by the dogfood test tree but is not registered in proof-registry.mts, so check:liveness emits a warning for it.

Lineage: this is a recurrence of the class closed as #10773 ("proof-registry.mts lags the dogfood test tree"). That card fixed the then-known instances; this tag either post-dates the fix or was missed. The recurrence suggests the class-level question is still open: a warning that never turns red does not stop new instances — the eventual card should consider whether registration drift ought to fail the check rather than warn.

Dedup (searched 2026-08-25): #10773 is closed; no open card covers this tag or the registration-drift class.

[os-trump]

Triage: pm:queue + domain:spec, Task, S — the proof-tag registry lives at packages/spec/scripts/liveness/proof-registry.mts (verified on origin/main), so an unregistered dogfood proof tag admin-platform-admin-standing is spec-lane ledger hygiene, a stated recurrence of #10773's class. Fix: register the tag (or correct the producer's spelling to a registered one — decide by reading which side drifted), and check whether #10773's repair left the class un-gated; if a cheap gate closes the class, propose it in the PR body rather than widening this card. Pre-existing warning, not red — no queue-jump. Triage seat session session_01TMpU2R7qfDGR8rHKBay9uJ.

---

Generated by Claude Code

[huangyiirene]

Claim: session_01E5LFCYBJ3q2s6yW6oMLxwy (domain:spec PM seat R7, seat post #6017) — branch claude/issue-12216-proof-tag-registry.

• File surface: packages/spec/scripts/liveness/proof-registry.mts (+ proof-registry.test.ts as needed). No overlap with the other in-flight card (docs content: the 38 generated reference pages still render two <h1> — the heading comes from a spec JSDoc header via build-docs.ts #12249: build-docs.ts / check-docs-single-h1.mjs / content/docs/references).
• Container & model: node scripts/pm/dispatch-gates.mjs --tier packages/spec/scripts/liveness/proof-registry.mts derived at origin/main 5d4d93a: no path-derived mandate (surface hits none of the declared globs). Content judgment: registering an existing dogfood proof tag changes no contract accept/reject behaviour and widens no public surface → opus (default tier).
• Clause-②: no (path limb: not packages/spec/src/**; content limb: no).
• Serial constraints: none. H17 holds not touched.

---

Generated by Claude Code

[huangyiirene]

os-dev-report

{
 "issue": 12216,
 "verdict": "implemented",
 "status": "done",
 "branch": "claude/issue-12216-proof-tag-registry",
 "pr_number": 12549,
 "pr_url": "https://github.com/objectstack-ai/objectstack/pull/12549",
 "premise_still_valid": true,
 "diff_summary": "2 files, +87/-3. (1) packages/spec/scripts/liveness/proof-registry.mts — registers HIGH_RISK_CLASSES entry `admin-platform-admin-standing`, bound:false with a blockedReason (commit 846750d). (2) packages/spec/scripts/liveness/check-liveness.mts — closes the #10773 CLASS: adds report.orphanProofs.length to the `failed` condition, upgrades the warning glyph to a failure glyph with remediation guidance, names the new invariant in the success line (commit b884d56, deliberately separate so it can be dropped independently). No producer edit. No changeset (packages/spec `files` excludes scripts/); `skip-changeset` label applied and read back.",
 "drift_side": "registry",
 "gate_finding": "#10773's repair registered instances but left the class un-gated. scanOrphanProofs() populated report.orphanProofs and printed it, but orphanProofs was ABSENT from the `failed` condition — so registration drift could never red the gate. That is the recurrence mechanism: the warning reported 13 tags, PR #10934 registered the 11 then present, a 12th arrived with the next dogfood proof, and this card was written off the same warning line as #10773. The gate is included rather than only proposed: one line of condition plus guidance text, same directory and same gate family as the card's own fix, no new validation surface, and the orphan list is at ZERO after the registration so it starts green — the same 'a check that starts at zero can be red' reasoning the keyMention* half was switched on under, three lines above it in the same condition.",
 "summary": "The tag `admin-platform-admin-standing` is produced at packages/qa/dogfood/test/admin-platform-admin-standing.dogfood.test.ts:113 and was absent from the registry, so the REGISTRY drifted, not the producer: the file names itself, its tag and its sibling consistently and cites admin-route-nonadmin-refusal.dogfood.test.ts as a different, already-registered file; no registered id is within a typo of it. Registered UNBOUND with an honest blockedReason — platform-admin standing is the ADR-0068 D2 identity resolution inside the auth plugin's route gate (runtime principal resolution, no authorable metadata key whose `live` status it gates), and it is a breadth guard over a derived route population besides, so binding any single ledger entry would misrepresent both what it covers and what that entry is proven by. proof-registry.test.ts needed no change: its 'unbound classes record an honest blockedReason' invariant covers the new entry and BOUND_PROOF_PATHS is unchanged because nothing bound.",
 "checks_run": [
 "pnpm --filter @objectstack/spec check:liveness — verdict line: 'every dogfood @proof: tag on disk is registered in proof-registry.mts', orphan list empty (at head b884d56)",
 "vitest run scripts/liveness/proof-registry.test.ts scripts/liveness/check-liveness.test.ts — 'Test Files 2 passed (2)' / 'Tests 62 passed (62)' (at head b884d56)",
 "pnpm --filter @objectstack/spec typecheck — 'check:test-typecheck: OK'; tsc -p tsconfig.scripts.json --listFiles confirms BOTH edited .mts files are in the program (2 hits), so this is measured, not a green over unread source",
 "pnpm lint (full repo, eslint . --no-inline-config) — exit 0, no narrowing and no narrowing-declaration owed",
 "pnpm check:nul-bytes — OK, 6921 text files, no raw ASCII control bytes",
 "node scripts/pm/bare-root-worklist.mjs --self-test — exit 0 (convention-triggered by the gate-script edit)",
 "pnpm check:pm-dispatch-gates — exit 0 (the second convention-triggered obligation of a gate-script edit)",
 "check:empty-state, check:strictness-ledger, check:variant-docs, check:merge-driver, check:page-declaration-shape, check:pm-governed-merges, check:published-files, check:slot-lookup, check:test-source-alias, check:type-source-resolution, check-comment-mask-adoption, check-plugin-teardown-shape, docs-audit/check-affected-docs — all exit 0",
 "REVERSE VERIFICATION: registry entry ablated; mutation proved on disk BEFORE the reading (git hash-object 51066bf -> 11f6368, marker grep -c 1 -> 0); check:liveness then exited 1 printing '1 unregistered dogfood proof tag(s)'. The same tree at BASE (same orphan tag, gate flip absent) exited 0 with the warning glyph — so the direction is a genuine warn-to-red flip, not an artifact of registering. Restore proved by observation not exit code: blob back to 51066bf, marker back to 1, `git diff HEAD` empty and `git status --porcelain` empty (index clean, no MM). Script carried a trap with absolute paths. No build/dist involved — check:liveness runs tsx over .mts sources.",
 "Gate family derived with `node scripts/pm/dispatch-gates.mjs --repo objectstack-ai/objectstack` against the real changeset (2 paths vs merge-base), not from the dispatch brief's list."
 ],
 "premise_notes": "Premise CONFIRMED on fresh origin/main (worktree base 1c0b9a5). check:liveness at base printed exactly one orphan: '@proof: admin-platform-admin-standing (in packages/qa/dogfood/test/admin-platform-admin-standing.dogfood.test.ts) — not registered in proof-registry.mts', and the gate exited 0 — warning-only, as the card said. Neither side had already been fixed.",
 "new_findings_filed": [],
 "instrument_disclosures": [
 "node scripts/check-dev-prereqs.mjs exits 1 in this worktree reporting 'The workspace is not built' — 67 of 67 workspace packages missing a dist/ entry point. PREREQUISITE NOT MET in a fresh never-built worktree (AGENTS.md multi-agent discipline section 9, first row), not a measurement of this diff: the verdict is about whether dist/ exists at all and cannot be moved by a two-file scripts-only change. Recorded as NOT MEASURED, not as a red gate. CI builds before it runs.",
 "Labelling took the declared fallback. The additive labels REST endpoint answered 403 'GitHub access is not enabled for this session' from this dev seat, so skip-changeset went through read -> union -> whole-set write via MCP issue_write: read ['size/s'], written back ['size/s','skip-changeset'], confirmed by read-back.",
 "GitHub body sanitizer mutation caught on read-back: the first PR body revision contained an angle-bracketed placeholder in the ablation command and the sanitizer removed it after storage, leaving 'git checkout --'. Respelled as BASE-COMMIT. A stale sentence in the second revision (written between the 403 and the successful label fallback) claimed the label could not be applied; corrected in the third revision rather than left standing.",
 "pnpm --filter '@objectstack/spec^...' build printed 'No projects matched the filters'. That is the zero-match pnpm trap by shape, but here it is genuine: @objectstack/spec has no workspace dependencies (it is the root of the graph), so there was no dependency closure to build. Typecheck and tests were run afterwards and passed."
 ]
}

---

Generated by Claude Code