[P2] Aspirational config — prune or mark experimental

[os-zhuang]

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

Problem

Aspirational config — rich spec, zero runtime. These properties parse but have no consumer. Each should be either pruned from the spec or explicitly marked experimental so authors know it does nothing yet.

Checklist

• field: enhanced-type configs (barcode / qr / slider / rating / color / location) + governance (encryption / masking / audit / dataQuality)
• object: enable / versioning / partitioning / cdc / softDelete / search
• agent: autonomy (memory / guardrails / structuredOutput / lifecycle) — except planning.maxIterations (live)
• tool: outputSchema
• job: retryPolicy / timeout
• theme: spacing / breakpoints / logo / rtl / density (and touchTarget)
• translation: messageFormat: 'icu' (no ICU engine), supportedLocales, cache
• webhook: non-HMAC auth
• PortalSchema (entire) — not registered, no route, no renderer (100% dead)

Evidence

• docs/audits/README.md cluster Add Changesets and GitHub Actions automation #4, plus per-type reports.

[os-zhuang]

Checklist pruning note — the object line is now fully resolved (via #2377's three-wave enforce-or-remove: #2402, #3176, #3414):

• versioning / partitioning / softDelete / search — removed from the spec, tombstoned in UNKNOWN_KEY_GUIDANCE
• enable.* — every flag is now either live with an enforcement contract ([spec/cli] 对象 enable.files/trackHistory/activities/feeds 为 dead property:schema 接受、liveness 仅告警不拦 #2707/[objectui/framework] enable.files: generic Attachments related-list (Salesforce Notes & Attachments parity) #2727: trackHistory/searchable/apiEnabled/files/feeds/activities/clone) or removed (trash/mru, feat(spec)!: remove dead enable.trash/mru capability flags (#2377 close-out, ADR-0049) #3414 — ObjectCapabilities is now .strict(), so future aspirational flags can't silently accumulate there)
• cdc — no longer present in the object schema

So the - [ ] object: enable / versioning / partitioning / cdc / softDelete / search item can be checked off. The trash/mru "prune or build" question this issue was holding landed on prune (#3414): a default-true flag promising a recycle bin that doesn't exist was a data-safety false affordance; if a recycle bin or MRU tracking is built, they return as live enforced flags.

Remaining scope here = the other types (field enhanced-type configs + governance, agent autonomy, tool.outputSchema, job retry/timeout, theme, translation, webhook auth, PortalSchema).

---

Generated with Claude Code

---

Generated by Claude Code