Pin the documents collaboration-storage plan merge (PR #59)
Why: the approved plan r1 landed on documents main via PR #59; the Dev parent must pin it for the combined build. Evidence: documents origin/main=95e5c9d307626727db2d1df3b42d74873bc8bbe4 containing proposal r1, index entry, review record, audit receipt. Impact: gitlink only; no code or runtime change. Refs: documents PR #59.
This commit is contained in:
+1
-1
Submodule modules/documents updated: b3ca409cfc...95e5c9d307
Reference in New Issue
Block a user