[sebastiaoteixeira]

Every grammar key is either enforced in every consumer (dev server, generated FastAPI, DRF and raw ASGI backends, UI generator) or rejected by schema validation.

All versions

• Every spec schema object is closed: unknown or misplaced keys fail validation.
• filter and writeFields no longer exist; role: inside a long-form given: rule is rejected. Per-role writable fields are expressed as separate operations with their own service input:.
• Soft deletion hides removed rows from every generated query in the dev server and every backend.
• Readonly fields are rejected in request bodies and filled by the server; DTOs share one field base, with a partial payload for updates.
• Datetimes are stored as canonical UTC strings; field defaults are stored in the canonical form of their field.
• Nested properties/additionalProperties are validated as nested models with extra keys forbidden.
• Role grants are limited to the caller's held roles; anonymous register/create cannot assign roles.
• Anonymous callers get 401 unless an allow rule can admit them; when over a document acts as a row filter on list routes.
• <collection> by <param> binds the record the route addresses.
• Typed request bindings resolve path parameters through every request part.
• Offset pagination breaks sort ties on the id.
• DRF views run on adrf with the same routing, statuses and access as the other targets; raw ASGI handlers keep per-controller access.

0.1

• options.strict, indexes, security.redaction, ref store: embed/expand and OIDC discovery_url/claim_mapping/auto_provision are removed.
• Collection roles and their hierarchy are kept; a replace without access of its own uses the update access.
• The mongo block is the default datastore; the dev server runs 0.1 specs.
• security.headers.enableStandard sends the standard security headers in every backend.

0.2

• Top-level roles: is removed; role hierarchies live in entities.<e>.roles.hierarchy.
• Repository softDelete: <timestampField> and per-operation includeDeleted: true on custom repository operations.
• Repository ttl: { field, seconds } expires rows on every datastore (MongoDB TTL index; SQL row filter and purge).
• api.operations.defaults accepts only CRUD switches and api.operations.auth only register/login; auth.login: false generates no login route.
• Standard security headers are sent by default; api.securityHeaders: false turns them off.
• api.port is honoured by stackform run, deploy, DRF and the UI.
• deploy.mongo.local is honoured and defaults from datastores.
• Service abstract/extends generate abstract service base classes; custom operations run through service methods.
• SAML: provider keys invalid for type: saml are rejected, relations are applied in the callback, SAML login works in the dev server, and replayed or malformed responses are rejected.

0.3

• Same changes as 0.2, plus: root input: and entities.*.auth.bindings are removed (via: replaces bindings); imports accepts only the object form.

UI

• Requests go through declared routes, pagination, roles and the access matrix; pages and actions are gated on it.
• Forms send typed, writable-only bodies and cleared fields as null; the ui block is validated against the pack manifest.

Docs and examples

• User docs describe the enforced grammar; pages about removed keys are deleted.
• The access-control example binds owners to the caller, restricts user deletion to admins and filters sensitive rows by owner.