Validate schemas without relying on source filenames

docs/formats.md

@@ -421,6 +421,8 @@ Schemas are JSON documents selected by a prompt or request `schema_path`.
 Directory and `fs.FS` schema paths resolve within the configured root. Each
 schema must be self-contained: in-document references, IDs, and anchors are
 supported, but references requiring another file or network resource fail.
+References must also work without the source filename as a base; use fragment
+references or explicit schema IDs rather than relying on that filename.
 `WithSchemaFile` exposes one schema under its base name. An unreadable,
 invalid, or unresolvable schema causes an operational validation error.
 Valid JSON that fails the schema instead yields a failed validation result.

docs/roadmap/remediation.md

@@ -72,7 +72,12 @@ existing cancellation policy.
 
 ### 2. Check Schema Self-Containment Independently Of Its Source Filename [P2]
 
-**Status:** Open. **Stages:** 11–13.
+**Status:** Complete. **Stages:** 11–13.
+
+Completion: shared compilation checks both the source base and an unrelated
+submission base through the same compiler rules, including unused declarations.
+Host and filesystem regressions preserve fragment, explicit-ID, and embedded-ID
+references while rejecting unsent source-name dependencies.
 
 **Locations:** [schema compilation](../../internal/validate/standard_validator.go),
 `compileSchemaDocument`, lines 426–445, and its host/`fs.FS` callers;