What this documentation covers

• Release notes grouped by version and date.
• Breaking changes and migration steps.
• New features and configuration flags.
• Security updates and operational notices.

Who this is for

• All users who depend on stable behavior across environments.

Operational expectations

• Examples favor deterministic behavior and explicit contracts (schemas, IDs, correlation).
• Security is treated as a default: least privilege, audit logs, and safe fallbacks.
• Changes are versioned; breaking changes should be announced via /docs/changelog.