Changelog — 2026-05-27

Breaking

• Attribute model consolidation around capabilities. @stndrds/schema now derives behavior from a single AttributeCapabilities matrix instead of scattered per-type flags. Several legacy public APIs were removed without aliases — migrate as follows:

  • textarea() → text({ ... }).multiline()
  • rating() → number({ ... }).renderAs("rating").max(5)
  • user.allowedRoles(...) → user({ ... }).types(["user", "agent"]) (default is both user and agent)
  • relation.minItems(n) removed (keep .maxItems(n))
  • document.maxDocuments(n), .autoProcess(), and the legacy .attribute(...) child API removed — use .slots([...]) and .qualifyWith(...)
  • location.enableAutocomplete(), .enableMap(), .displayFormat(...) removed — autocomplete/map are UI/view concerns now
  • .disabled() removed from the schema attribute model — express read-only at the view/form level
  • .featureGate(...) removed from all builders, parsers, and UI
  • Option.id and Option.icon removed — option objects are now { value, label, color?, description?, group?, inverse? } and identified by value

  See the updated Attributes page for the current modifier surface.

Other

• Runtime filterable/searchable/sortable/groupable behavior, Meilisearch processed-value projection, agent schema-tool exposure, default columns, popover editors, and form placeholder rules are all now derived from the capability matrix rather than duplicated per consumer. No editorial guide changes are required, but downstream forks that read attribute.filterable or similar duck-typed flags should switch to the capability helpers exported from @stndrds/schema.