[objectstack-fleet]

Closes #24900

Clause-②: no

What this does

Re-grades a declared webhook's label and description from dead to live in packages/spec/liveness/webhook.json. It records the reader and producer the card asked for, and carries the re-grade to the one test and the two prose sites that restated the old verdict.

The 2026-10-19 dead verdict measured only the Setup sys_webhook list, which lost the declared webhook when the boot seeder retired (ADR-0131 D2). A second surface reads the declared registry item itself and was never cut.

• Reader (objectui, at the .objectui-sha pin 616df6598b42): ResourceListPage.tsx#defaultColumns (webhook registers no listColumns and no ListPage, so DefaultMetadataList draws label and description through row.item[c.key]), and QuickFind.tsx#MetadataQuickFind. webhook has no registered preview and no Setup catalog.
• Producer (measured by booting): pnpm dev -- --fresh on examples/app-showcase at 223ae939bb, with a probe label and description authored on its declared webhook (reverted, hash-verified), signed in as the dev admin. GET /api/v1/meta/webhook answered 200, and its one item carried both probe values with _packageId: com.example.showcase. GET /api/v1/meta/types lists webhook, and that package has scope: project.
• Not readers, checked: in plugin-webhooks, auto-enqueuer.ts#projectDeclared (delivery props only), redeliver-guard.ts#judgeDeclared and bindDeclaredWebhookNameGuard (name and switch only). In the runtime, catalog-activation.ts DECLARATION_LOOKUPS.webhook (name, packageId). In the CLI, the ownership port declaredWebhooks.list (name, packageId). organization-ownership-apply.ts#isSwitchOnlyEdit compares a seeded row with that row's own stored definition_json: a migration read of 18.0 data, not of the authored key.

This follows the hook.label and email_template.label rows, under the designer-previews ruling (liveness README, "Designer previews count as consumers"). For a display key, being shown to a human is the whole of its claimed effect. No enforce-or-retire decision is owed.

Files

• packages/spec/liveness/webhook.json: both rows are now live, with evidenceScope: cross-repo, evidence, producer and verifiedAt: 2026-10-20. The authorHint is removed, the old note is kept as HISTORY, and the file _note is corrected.
• packages/spec/liveness/state-counts/webhook.md: regenerated with gen:liveness-counts; live/dead moves from 17/2 to 19/0.
• packages/lint/src/lint-liveness-properties.test.ts: the webhook case reads the real ledger and now pins silence on a declared webhook that authors every prop.
• examples/app-showcase/src/automation/webhooks/index.ts (comment only) and docs/qa/platform-checklist/areas/integration-system.json (source line): both now state the live grading and the Studio reader.
• .changeset/24900-webhook-label-description-live.md: @objectstack/spec patch. The spec package ships liveness/ in files[], and the advisory os lint reads it from there, so this change publishes: the liveness-dead-property warning on these two keys stops. That is why there is no skip-changeset.

Verification (head 5848b7dd99)

• pnpm --filter @objectstack/spec check:liveness: exit 0, all-clear line printed.
• pnpm check:platform-checklist: exit 0.
• Lint test src/lint-liveness-properties.test.ts: against the re-graded ledger before the test edit, 1 failed / 102 passed (warns on a declared webhook's label and description only, expected an empty list to equal two findings). After the edit, 103 passed.
• node scripts/pm/dispatch-gates.mjs --commands: 78 families derived. 76 exited 0 and --ran reconciles 78 of 78. The two non-zero results, check:dts-closure and check:dual-build-cjs-loads, are NOT MEASURED. Reason: the local dists were built with OS_SKIP_DTS=1, so they hold no .d.ts (@objectstack/types, triggers, verify), and this diff touches no package source. CI builds with declarations.
• Families 1 to 70 ran at bf94c93377. The 8 changeset families the changeset commit added ran at 5848b7dd99. Between those heads only .changeset/ changed.

Acceptance notes

• The security issue measured on the same boot is filed separately as meta: the webhook metadata type has no redactor, so its secret-bearing fields are not masked on the meta read doors (detail withheld under the disclosure ruling) #24966: GET /api/v1/meta/webhook serves a declared webhook's authored secret verbatim, because webhook has no metadata-type redactor. Nothing in this PR touches it.
• origin/main was merged once (no rebase). Nothing it brought adds a reader of these keys.

---

Generated by Claude Code

[github-actions]

📓 Docs Drift Check

⚠️ 2 changed file(s) yielded no anchor (packages/spec/liveness/state-counts/webhook.md, packages/spec/liveness/webhook.json), so the pages documenting them are NOT COVERED by this run — this is not a clean bill of health for those files. Nothing else in this diff resolved to a documentable surface (no symbol, route or SDK anchor derived from 1 changed package(s)).

What this run could not see

• 2 changed file(s) yielded no anchor (packages/spec/liveness/state-counts/webhook.md, packages/spec/liveness/webhook.json) — pages documenting those are invisible to this run
• a page that states a rule by its inputs shares no identifier with the emitter that implements the rule, so an emitter-only diff cannot list it — not on this run and not on any run. Measured on fix(driver-sql): emit varchar(maxLength) for a text field a declared index keys on #11430: content/docs/protocol/objectql/types.mdx documents the text-family column mapping by the ObjectQL type names it maps FROM (text / textarea / html) while the diff changed createColumn; it went unlisted, and it was the page that diff falsified, in four places. No shared token exists to detect this on, so a rule your change carries has to be re-read by hand in the pages that restate it.
• a key NAME is not a key, so the hand re-read the line above prescribes can land on the wrong schema. The same spelling is authorable on one governed type and a [REMOVED] tombstone on another for each of active, aria, joins, objects, template, tools and version (censused on [finding] tools is a key on BOTH AgentSchema (tombstoned, dead) and SkillSchema (live, cloud-attested), so a name-based search attributes skill examples to the agent key — it produced a false stop-the-line alarm on PR #19059 #19093 over the liveness ledger's governed types, top-level keys); nothing in a search result distinguishes the two, so a grep hit on a LIVE example reads as evidence about the DEAD key. Measured on fix(spec): the agent.tools liveness row says dead — it claimed live on a key the schema tombstoned #19059: content/docs/ai/agents.mdx was reported as contradicting the agent.tools tombstone over its tools: example at :161, which is inside the defineSkill({ block opened at :155 — the page was already correct. Settle ownership by PARSING the value against both schemas, never by the name: that literal PASSES SkillSchema, and as an AgentSchema it FAILS at tools with the tombstone prescription. ⛔ These names are not the whole class — a key retired through a .strict() guidance map leaves no tombstone in the walked shape and none of them here (tool.category, live as AIToolDefinition.category).

Coarse fallback — 144 page(s) merely mention a changed package (the pre-#9192 predicate, kept for the deliberately-wide backstop): node scripts/docs-audit/affected-docs.mjs --json 693352e4c2b56f15bfda068e69c5d82ed6765687 → packageMentionDocs.