Why: the library now makes precedence, memory tiers, and lesson
mechanization explicit; the composition must pin the revision and register
how its layers map onto the new rules.
Evidence: guidelines PR#3 (ed2af3e) and documents PR#4 (2205138) merged;
make test on this branch per the gitlink rule.
Impact: gitlink advances; adoption registers the hierarchy/memory rows as
manual-with-existing-artifacts. No code change.
Refs: policy/adoption.md; docs/records/2026-09-30-history-migration-sha-map.md
Why: the two 2026-09-30 lesson entries merged into documents main; the
composition should consume them for future retrieval.
Evidence: documents PR#3 merged (2ec3e50); make test on this branch before
merge per the gitlink rule.
Impact: gitlink-only advance; no product code change.
Refs: docs/records/2026-09-30-lesson-*.md
Why: the backend store List* functions encoded empty results as JSON null,
which crashed the frontend nav (.map on null) on any newly created project.
Evidence: backend go test all packages pass; store regression
TestEmptyListsSerializeAsEmptyArrays asserts [] for empty lists.
Impact: parent pins backend at the serialization fix plus the core-pin
build-blocker advance.
Refs: .task/fix-empty-list-json.md
Why: the nine submodule entry docs and the documents migration record merged
via their own PRs; the parent must pin the new combination and register the
adoption with honest enforcement levels.
Evidence: per-repo PR merges (9x entry-docs PR#1, documents PR#2) verified
via API; make test on this branch follows before merge.
Impact: gitlinks advance to post-migration, gate-adopted mains; policy/
adoption.md registers enforced (local hooks) vs advisory vs manual honestly.
Refs: ef89fc8; Development-Guidelines 0.1.0-draft.7
Details (original message):
Advance backend gitlink (intentgate integration a671d60) with its new deps pins; example plugin intent asset uses the overlay matcher format.
weichen