readme: correct the fork boundary

README.md

@@ -86,24 +86,28 @@ If you are used to using generative AI, please ensure you read our [Policy](http
 
 ## Why this fork exists
 
-This is Smithay with five patches on top of upstream
+This fork carries five functional patches on top of upstream
 `812bd33259ff58810dadef6086d8385eeac1ca55` (*renderer: `cgmath` -> `glam`*,
-2026-07-14). 332 insertions across 7 files. Nothing else differs.
+2026-07-14), plus the fork's own explanation, CI contract and toolchain
+compatibility fixes.
 
 - **`wlr-layer-shell`: do not validate a role the client already destroyed.**
   A teardown race: the client destroys the role, the compositor validates it
   anyway, the session dies.
 - **`session-lock`: tolerate a bufferless commit before the first ack.**
-  A lock surface that commits before acking is legal and was rejected.
+  Qt commits once before the first configure ack, which the protocol forbids.
+  This fork tolerates only that bufferless compatibility commit; attaching a
+  buffer before the ack still fails.
 - **`gles`: optional linear-space gamut transform on sampled textures.**
   Opt-in. Needed to map sRGB content into a panel's own primaries.
 - **`drm/compositor`: wait when there is no native fence.**
   Without it a device with no native fence tears.
 - **`gles`: optional chromatic split on sampled textures.** Opt-in.
 
-The first two are plain upstream bugs. The fence wait is a correctness fix.
-The two `gles` changes are feature-gated and off by default. All five look
-upstreamable; none has been submitted yet.
+The layer-shell teardown and fence wait are upstream candidates. The
+session-lock change is an explicit Qt compatibility exception. The two `gles`
+changes are ViewTop-facing features, gated and off by default. None has been
+submitted upstream yet.
 
 Consumed by [souveraine-viewtop](https://forge.caseytunturi.com/Fimeg/souveraine-viewtop),
 which pins this fork by revision.