docs(adr): name the obstacle to folding that survived ADR-0132's merge

The hand-merge note said the only thing blocking a single combined record was
ADR-0132 being unmerged, and that with it landed the choice "stands on its
merits alone". True, but it leaves the reader to rediscover the merit that
matters: that record carries its own D1 through D6, which are different
decisions from cloud ADR-0081's D1/D3/D4, so folding this mirror into it puts
two unrelated D1s in one document — exactly the property the deliberately
unrenumbered mirror exists to keep checkable.

Stated, not decided: the disposition is still the maintainer's merge-time call,
and this change takes the option neither way.

Gates re-run on this tree: check-adr-anchors exit 0, check-adr-symbol-anchors
exit 0 with "0 line anchors survive", check-adr-links exit 0, check-nul-bytes
exit 0, check-doc-authoring exit 0, check-governed-merges --test exit 3 GOVERNED.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01XpTx2tbq3pZRYAdoGt6E6Y

Author: claude

docs/adr/0133-org-management-open-basics.md

@@ -91,9 +91,13 @@ D1/D3/D4 into that file instead of writing a second one. When this file was
 drafted that option was not available: ADR-0132 did not exist on `main`, so
 "extending" it would have meant building on an unmerged governed PR and coupling
 two hand-merges into one. That obstacle is gone — the record has landed — so the
-choice now stands on its merits alone. This change does not take it. **If the
-maintainer prefers one combined record, that is still a merge-time call** — the
-two files are disjoint, so folding them is a move, not a rewrite.
+choice now stands on its merits alone. ⚠️ One of those merits is structural and
+survived the merge: that record carries **its own D1 through D6**, which are
+different decisions from cloud ADR-0081's D1/D3/D4, so folding this file into it
+would put two unrelated `D1`s in one document — the property the unrenumbered
+mirror above exists to keep checkable. This change takes the option neither way.
+**If the maintainer prefers one combined record, that is still a merge-time
+call** — the two files are disjoint, so folding them is a move, not a rewrite.
 
 ---