Compatibility and version policy

The unversioned documentation describes the current development line. Versioned documentation is a release snapshot and may not contain components introduced later.

Reading version-sensitive pages

When a component, configuration key, API endpoint, or delivery guarantee is version-sensitive, use the version dropdown and confirm the release note for that version. A feature documented only in the current tree must not be assumed to exist in an older snapshot.

Maintaining compatibility notes

Add a compatibility notice when behavior changes, a configuration key is renamed, or an endpoint is deprecated. Keep the old route or a migration stub until the route migration is announced; record path changes in the route migration map.