CMIS compliance fixture integration and optional OpenCMIS TCK harness boundary

docs/cmis-profiled-access-points-implementation.md

@@ -120,6 +120,22 @@ Relationship listings and change logs now apply the same asset visibility gates
 as object reads. This prevents indirect leakage of confidential or restricted
 asset IDs through relationship targets or audit-backed change entries.
 
+## Fixture And Optional TCK Integration
+
+CMIS fixtures now act as active compatibility contracts:
+
+- `examples/cmis/capability-fixtures.json` defines profile expectations and
+  capability groups,
+- `tests/cmis/test_cmis_fixture_integration.py` compares those expectations to
+  implemented profiles and access-point shapes,
+- `tests/cmis/opencmis-tck/tck-subset-map.json` maps fixture capability groups
+  to selected OpenCMIS TCK groups,
+- `tests/cmis/opencmis-tck/tck-result-template.json` captures optional TCK
+  result summaries and known capability gaps.
+
+The default Python suite validates the fixture/TCK mapping without requiring
+Java or Maven. Actual OpenCMIS TCK execution remains opt-in.
+
 Route-level tests are present but skip when the optional FastAPI/httpx service
 dependencies are not installed. Runtime-level Browser Binding tests cover the
 same behavior in the default Python test suite.