Skip to content

[P2] Aspirational config — prune or mark experimental #1893

Description

@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

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions