docs: supersede outdated retirement commitments

Author: sidmohan0

README.md

@@ -188,9 +188,10 @@ scan/redact helpers, or guardrail helpers.
     model.
   - A Java runtime is required by PySpark.
 
-OCR and Spark are not deprecated. Their broader API and packaging overhaul is
-deferred; the 4.x goal is to keep them explicit, documented, and isolated from
-the lightweight core path.
+The upcoming 4.9 release deprecates OCR and Spark with visible use-time
+warnings; their APIs and extras will be removed in 5.0. They remain functional
+in 4.9. Users who need these features can stay on the final 4.x release. See
+the [4.9 migration guide](docs/migration-4.9.md) for the transition plan.
 
 ## Backward-Compatible APIs
 

docs/roadmap.rst

@@ -2,6 +2,14 @@
 Release Roadmap
 ================
 
+.. note::
+
+   This earlier planning document is retained for context. The upcoming 4.9
+   bridge revises its compatibility commitments: ``detect``/``process``, OCR,
+   and Spark are deprecated in 4.9 and removed in 5.0. The former promise to
+   retain the shims through 5.x no longer applies. See the
+   :download:`current migration plan <migration-4.9.md>` for the agreed scope.
+
 Where DataFog is today (4.8.x) and where it is going (v5.0.0). The 4.x
 line delivered the lightweight-core architecture and, from 4.6.0 on, an
 offline PII firewall for AI agents and gateways. The v5 cycle turns that

docs/v5-compatibility-matrix.rst

@@ -2,6 +2,14 @@
 v5 Compatibility Matrix
 =======================
 
+.. note::
+
+   This earlier planning document is retained for context. The upcoming 4.9
+   bridge revises its compatibility commitments: ``detect``/``process``, OCR,
+   and Spark are deprecated in 4.9 and removed in 5.0. The former promise to
+   retain the shims through 5.x no longer applies. See the
+   :download:`current migration plan <migration-4.9.md>` for the agreed scope.
+
 Status
 ------