docs(release): clarify platform line break

CHANGELOG.md

@@ -18,8 +18,9 @@ include migration notes.
   `tools.jackson.databind.ObjectMapper`.
 - Updated integration tests for Spring Boot 4's `spring-boot-resttestclient`
   package and explicit test client auto-configuration.
-- Recommended a new `7.0.0` release for Spring Boot 4.1 consumers. Use
-  `6.0.x` for Spring Boot 3.5 / Java 21 applications.
+- Recommended a new `7.0.0` release for Spring Boot 4.1 consumers. Vigil
+  `6.0.x` was the final Spring Boot 3.5 / Java 21 line, not a
+  backward-compatibility target for `7.0.x`.
 
 ## 6.0.0 - 2026-06-05
 

README.md

@@ -19,9 +19,10 @@ Vigil `7.0.0` is the Spring Boot 4.1.x / Java 25 certification line.
 | Gradle wrapper | 9.1.x |
 | JSON support | Jackson 3 (`tools.jackson`) |
 
-Vigil `6.0.x` remains the Spring Boot 3.5.x / Java 21 line. Spring Boot 4.1
-consumers should use `7.0.0` or newer because Boot 4 moves to Jackson 3 and
-modular test/client support.
+Vigil `7.0.x` is the active supported platform line. Vigil `6.0.x` was the
+final Spring Boot 3.5.x / Java 21 line and is not supported for Spring Boot
+4.1 consumers. Do not add compatibility shims between the two lines; Boot 4
+moves to Jackson 3 and modular test/client support.
 
 The only intentional public API break in `7.0.0` is the JSON mapper type used
 by `VigilAuthenticationEntryPoint`: Spring Boot 4 defaults to Jackson 3, so the

docs/release.md

@@ -44,9 +44,11 @@ Current tested compatibility envelope:
 - HS256 with a configured 256-bit minimum secret;
 - RS256 with configured PEM private/public keys and JWKS publication.
 
-Vigil `6.0.x` is the Spring Boot 3.5.x / Java 21 line. Spring Boot 4.1
-consumers must use a `7.0.x` or newer artifact because Boot 4 changes the
-default JSON stack to Jackson 3 and modularizes several Boot support packages.
+Vigil `7.0.x` is the active supported platform line. Vigil `6.0.x` was the
+final Spring Boot 3.5.x / Java 21 line and is not supported for Spring Boot
+4.1 consumers. Do not add compatibility shims between the two lines; Boot 4
+changes the default JSON stack to Jackson 3 and modularizes several Boot
+support packages.
 
 The `7.0.0` line intentionally changes
 `VigilAuthenticationEntryPoint(String, ObjectMapper)` from Jackson 2

docs/usage-guide.md

@@ -15,9 +15,10 @@ Vigil `7.0.x` supports Spring Boot 4.1.x, Spring Framework 7.x, Spring Security
 7.1.x, Java 25, Gradle 9.1.x, and Jackson 3. Consumers still own their
 `SecurityFilterChain` and product authentication endpoints.
 
-Use Vigil `6.0.x` for Spring Boot 3.5.x / Java 21 applications. Do not mix the
-Boot 3.5 line with Vigil `7.0.x` because Spring Boot 4 moves JSON support to
-Jackson 3 `tools.jackson` packages.
+Vigil `6.0.x` was the final Spring Boot 3.5.x / Java 21 line. Do not mix the
+Boot 3.5 line with Vigil `7.0.x`, and do not add compatibility shims between
+the two platform lines. Spring Boot 4 moves JSON support to Jackson 3
+`tools.jackson` packages.
 
 ## Choosing The Client Path