[P2] Naming drift → silent no-ops (spec key ≠ consumed key)

[os-zhuang]

Part of the metadata liveness audit umbrella #1878 (P2 — spec hygiene, cluster #3).

Problem

Naming drift: the spec key ≠ the key actually consumed, so the authored property is a silent no-op. Each pair below needs the spec and consumer reconciled to a single name (and an alias/migration where authors already use the wrong one).

Checklist

• field: maxLength / minLength / referenceFilters / maxRating
• page: type → pageType; label → title; visibility
• dashboard: title vs label
• app: renderer reads accentColor / badgeVariant / separator — not declared in spec (see also the inverse-drift issue)
• action: disabled → enabled (see also the P0 action issue for the CEL form)
• flow: http vs deprecated http_request (Studio authors the alias)
• skill: requiredPermissions vs permissions
• agent: knowledge.topics → knowledge.sources
• webhook: object → object_name; isActive → active

Evidence

• docs/audits/README.md cluster Implement ObjectStack protocol specification with Zod schemas and TypeScript interfaces #3, plus the per-type reports for each item above.

[os-zhuang]

Progress from a current-state re-audit + fixes (umbrella #1878). Verified each row against main; several were already reconciled since the 2026-06 audit.

Status by row

• field maxLength/minLength/referenceFilters/maxRating — ✅ done. Server already honored camelCase; the objectui client form now reads spec-canonical minLength/maxLength too (snake_case kept as fallback) — fix: read spec-canonical keys for dashboard header title and field length rules objectui#2806 (merged). referenceFilters was removed in 16.x (→ lookupFilters); maxRating is a non-issue (rating.max is consumed).
• page type→pageType, label→title, visibility — ✅ already reconciled (spec-bridge renames type→pageType, label consumed as-is, visibility normalized to visibleWhen at parse).
• dashboard title vs label — ✅ done. DashboardRenderer header now falls back to spec-canonical label — objectui#2806 (merged).
• action disabled→enabled — ✅ already reconciled (renderer consumes spec disabled; enabled deprecated fallback, [P0][security] Action disabled (CEL form) silently ignored #1885).
• flow http vs http_request — ✅ already reconciled (engine registers http_request as an alias of http + canonicalizes on rehydration).
• skill requiredPermissions vs permissions — ✅ already reconciled (spec settled on permissions).
• agent knowledge.topics→sources — ✅ done. AIKnowledgeSchema now folds the deprecated topics alias into sources at parse time (canonical wins) — fix(spec): fold agent knowledge.topics into sources; mark unenforced AI config experimental (#1891, #1893) #3439 (merged). Authoring topics is no longer a silent no-op.
• webhook object→object_name, isActive→active — ⏳ still open — needs a maintainer decision. Spec WebhookSchema declares object/isActive while the runtime object + auto-enqueuer read object_name/active, with no bridge. Reconciling can go two ways (rename the spec to match the runtime, or add a parse-time alias/transform) — flagging for a call before I implement, since it touches persisted webhook rows.

Leaving this issue open for the webhook row. Everything else is reconciled. Note: dashboard and webhook are the two types with no liveness ledger — enrolling them in the GOVERNED set would have caught these drifts automatically (systemic follow-up).

---

Generated by Claude Code

[os-zhuang]

Closing. Of the 8 naming-drift rows, 7 are reconciled (field length keys, page, dashboard title/label, action, flow, skill, agent — see the previous comment for the per-row status + merged PRs #2806 / #3439).

The webhook row turned out not to be a live-consumer naming drift. On implementation I verified there is no consumer of the spec WebhookSchema's object/isActive — the dispatcher runs entirely off admin-authored sys_webhook rows (object_name/active); nothing ingests the spec Webhook into a row. So the "quick alias" would have been an inert no-op. It's a disconnected/write-only case needing a decision, split out to #3461 (with full evidence) rather than fake-fixed here.

Systemic root cause (dashboard + webhook have no liveness ledger → drift undetected) tracked in #3462.

---

Generated by Claude Code