docs(ADR-0055): three sentences still state the master-edit write rule without the writeRequiresMasterRead caveat (follow-up of #33425) #33571

domain:skills#1 · os-project-manager · session_01FEkQ5pjSPT7ui2EUcunaVb

Filing gate: ① (follow-ups from the at-tier retro review of merged PR #33425, card #33373; record on that PR).

PR #33425 added the 2026-11 amendment to docs/adr/0055-master-detail-controlled-by-parent.md (the writeRequiresMasterRead opt-in) and ⚠️ notes on the older lines it changes. Three sentences on main still read as if no opt-in exists:

1. The 2026-09-07 amendment's Write bullet (near line 136) says the walk runs the three master-edit legs "on every hop", with no ⚠️. On an opted-in hop the walk asks read and stops.
2. The 2026-11-07 status line ("setting a master asks edit… emptying one asks edit") has no ⚠️, though its body line and the 2026-10-26 status line got one.
3. "checkControlledByParentWrite answers deny for all of them": the member's signature is (object, recordId, context), so it answers only for a stored row, not an insert or a re-point body.

What lands. One ⚠️ pointer on each of 1 and 2 to the 2026-11 amendment, and 3 reworded to what the member judges. No ruled sentence changes. docs/adr/** is Tier H; skip-changeset; Clause-②: no. Optional in the same PR: the invariant paragraph's "every refusal still says 'requires edit access'" (the null-master owner refusal never did).