CMIS layer into an honest CMIS 1.1

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

@@ -2,7 +2,7 @@
 
 Date: 2026-05-06
 
-Status: Browser Binding MVP implemented.
+Status: Browser Binding subset implemented and capability-hardened.
 
 ## Implemented Slice
 
@@ -61,6 +61,11 @@ model.
 - relationship primitives as CMIS relationship objects,
 - profile-derived allowable actions.
 
+Repository info now uses conservative standard CMIS flags: optional services we
+do not implement are advertised as `false` or `none`, while Kontextual-specific
+projection behavior is exposed through repository feature metadata and an
+unsupported-feature catalog.
+
 The mapper returns `None` for assets or relationships that the access-point
 profile must not expose. It does not fetch from repositories directly; callers
 provide the asset, representations, versions, metadata records, and
@@ -105,6 +110,10 @@ These routes delegate to existing engine services:
 Read-only profiles reject the same mutations with CMIS-shaped authorization
 diagnostics before touching engine services.
 
+The authoring slice intentionally supports only `kontextual:metadata:<key>`
+property updates. Attempts to update standard `cmis:*` properties return
+structured validation diagnostics instead of being silently ignored.
+
 ## ACL And Redaction Slice
 
 The Browser Binding adapter now projects profile-derived ACLs through
@@ -122,7 +131,7 @@ asset IDs through relationship targets or audit-backed change entries.
 
 ## Projection-Only Multifiling
 
-CMIS navigation now supports projection-only multifiling. The same asset can be
+CMIS navigation now supports projection-only parent maps. The same asset can be
 listed under several derived folder paths, including source system, topics,
 owner, lifecycle, and asset type. These folders are navigation projections; they
 do not duplicate assets and do not become canonical storage locations.
@@ -131,6 +140,10 @@ do not duplicate assets and do not become canonical storage locations.
 parent folders for one asset. `GET /cmis/{access_point_id}/browser/children`
 supports folder-scoped navigation through those projected paths.
 
+The standard CMIS `capabilityMultifiling` flag remains `false` because the
+engine does not expose mutating filing services such as `addObjectToFolder` or
+`removeObjectFromFolder`.
+
 ## Fixture And Optional TCK Integration
 
 CMIS fixtures now act as active compatibility contracts: