Merge remote-tracking branch 'upstream/main' into leseb/remove-safety-api

Signed-off-by: Sébastien Han <seb@redhat.com>

Author: leseb

AGENTS.md

@@ -142,6 +142,14 @@ When modifying or extending APIs:
    enforces backward compatibility.
 4. Include a test plan with a testing script and execution output in your PR description.
 
+The full stability contract — HTTP API levels (`/v1alpha`, `/v1beta`, `/v1`),
+the two `ogx-api` package surfaces (`ogx_api.types`, `ogx_api.provider`),
+config schema rules, and the data storage compatibility guarantees across
+Z/Y/X-stream upgrades — is documented in
+[`docs/docs/concepts/apis/api_leveling.mdx`](docs/docs/concepts/apis/api_leveling.mdx).
+Read it before adding a new API, graduating an API between levels, removing
+or renaming a field on a `v1` datatype, or changing on-disk storage schemas.
+
 ## Common Patterns
 
 ### Adding a new parameter to an existing API