[P2] Enroll `dashboard` / `webhook` / `report` in the spec liveness GOVERNED set

[os-zhuang]

Systemic follow-up from the metadata-liveness audit (umbrella #1878).

Why

The spec liveness gate governs only the types in GOVERNED (packages/spec/scripts/liveness/check-liveness.mts:56):

object, field, flow, action, hook, permission, position, agent, tool, skill, dataset, page, view

dashboard, webhook, and report are authorable/round-trippable but NOT in this set, so they have no liveness/<type>.json ledger and CI never checks them. That gap is the systemic reason several drifts survived undetected until the 2026-06 audit — e.g.:

• dashboard root title vs label (fixed reactively in fix: read spec-canonical keys for dashboard header title and field length rules objectui#2806);
• webhook object/isActive vs runtime object_name/active ([P2] Webhook: the spec WebhookSchema authoring surface is disconnected from the sys_webhook dispatcher #3461);
• report chart/ReportColumn/ReportGrouping staleness (fixed reactively in docs(spec): correct ReportChart xAxis/yAxis semantics; mark dead report surface (#1890) #3441).

Enrolling these three closes the ratchet so the next such drift is a CI failure, not an audit finding years later.

Scope

For each type, following the view precedent (#2998 Track B):

• Author packages/spec/liveness/<type>.json classifying every top-level prop live / experimental / dead with file:line evidence (drill one level via children where sub-props diverge).
• Add the type to GOVERNED in check-liveness.mts (requires it to resolve through the metadata-type registry — report/dashboard are registered; webhook is not yet, so it may need registration first, or a small gate accommodation).
• Confirm pnpm --filter @objectstack/spec check:liveness is green.
• authorWarn the genuinely-misleading dead props (per the ledger README rules).

Suggested order: report first (its chart/column/grouping split is already characterized in #3441), then webhook (do it with the #3461 decision), then dashboard.

Refs #1878, #1891, #3441, #3461, #2998.

[os-zhuang]

report + dashboard enrolled — merged in #3474 (squash a41ba5c).

• packages/spec/liveness/report.json (20 live / 2 dead) and dashboard.json (18 live / 2 dead) authored, each prop classified with an objectui consumer reference.
• Both added to GOVERNED in check-liveness.mts; pnpm --filter @objectstack/spec check:liveness green (report 22 classified (live 20, dead 2); dashboard 20 classified (live 18, dead 2)).
• performance authorWarn'd on each (the genuinely-misleading dead prop); aria dead but not warned.
• Re-verification corrected several stale 2026-06 audit findings against current objectui HEAD: report chart is live (DatasetReportChart via useDatasetRows, [P1] Finish ADR-0021 analytics migration (chart view / dashboard+Studio / report) #1890/docs(spec): correct ReportChart xAxis/yAxis semantics; mark dead report surface (#1890) #3441); dashboard globalFilters/dateRange live (Dashboard-level filters (date / region) driving multiple charts #2501); title↔label fixed (objectui#2806); ADR-0021 widget migration shipped ([P2] Finish the dashboard analytics migration: Studio → dataset shape, then enable DashboardWidgetSchema strict validation #3251).

webhook — still deferred. It isn't a registered metadata type, so it can't enter GOVERNED without registration first, and its schema is disconnected from the runtime sys_webhook dispatcher (spec object/isActive vs runtime object_name/active). Its enrollment is coupled to the disconnect decision in #3461; this issue stays open to track that last third.

---

Generated by Claude Code