docs(qa): round 11's history rows name their pull request

Claude-Session: https://claude.ai/code/session_01FM29ZqLTrnPNXxijioZwMp
Co-authored-by: Claude <noreply@anthropic.com>

Author: claude

docs/qa/platform-checklist/areas/access-security.json

@@ -931,7 +931,7 @@
           "revision": 4,
           "date": "2026-10-20",
           "change": "automated dropped and fixtures.knownGaps[0] added, under round 6's theme-B rule (drop `automated` where no pin asserts a full clause, with a knownGaps line) — round 11 of wave anchor #24579, whose round-3 summary named this nominally Tier 1 item. Its revision-3 automated.ref already said the three dogfood pins cover no clause. Re-read at 46bb5e3e54: they drive business-unit depth on showcase notes and never the manager / executive / ops personas or showcase_inquiry. The item is now Tier 2, every clause driven by hand as revision 3 already prescribed. No clause changed",
-          "ref": "claude/issue-24579-v18-sweep-round11"
+          "ref": "#24801"
         }
       ]
     },
@@ -2485,7 +2485,7 @@
           "revision": 6,
           "date": "2026-10-20",
           "change": "producers re-measured and acceptance[0] aligned with its governing text — QA run #24783 (finding F3), round 11 of wave anchor #24579. personas[0]–[1], fixtures.requires[1] and knownGaps[0]–[1] now name the two durable producers on a walled boot (a user the operator creates under invite-only, membershipCreated:false; a member that sets its active organization to null). The signup race is closed by ADR-0123 D3's session-seam settle, and the removed-member path revokes or re-points the session (QA run #24783 measured 401). acceptance[0]'s clause and verify scope 'resolve to nothing' to a caller with no organization scope, which ADR-0123 D2 defines under `group` as an empty membership set, ADR-0105 D2 letting a `group` member's reads span its memberships. acceptance[4] is unchanged: ADR-0123 states no answer for a member-less user's NULL-tenanted audit rows, so knownGaps[3] names the question. knownGaps[4] names #24784, the `group` write 500. knownGaps[2]: the prerequisite sentence holds through os dev only (a bare production os serve needs OS_AUTH_SECRET first, RUNNER.md), and the blocked marker's reason is restated (every clause is a walled leg) because a producer is no longer missing; the marker itself is unchanged",
-          "ref": "claude/issue-24579-v18-sweep-round11"
+          "ref": "#24801"
         }
       ]
     },
@@ -2640,7 +2640,7 @@
           "revision": 8,
           "date": "2026-10-20",
           "change": "fixtures.requires[3] names the recipe for the walled legs' org-owner manage_metadata grant, and knownGaps[0]'s prerequisite sentence says os dev — QA run #24783 (findings F7 and F2), round 11 of wave anchor #24579. No HTTP door placed the grant on the walled boot: the operator's insert into an organization it is not a member of is refused by the Layer 0 tenant check, and the owner's own insert by ADR-0090 D12 condition (c), manage_metadata being scope 'platform'. The recipe is the dogfood harness's system-context engine insert (wall-environment-metadata-refusal.dogfood.test.ts, its boot helper). A bare production os serve judges none of the walled prerequisites until OS_AUTH_SECRET is set (RUNNER.md), so the refusal sentence now names os dev. No clause changed",
-          "ref": "claude/issue-24579-v18-sweep-round11"
+          "ref": "#24801"
         }
       ]
     },
@@ -3524,7 +3524,7 @@
           "revision": 5,
           "date": "2026-10-20",
           "change": "fixtures.requires[2] names the recipe for its organization-scoped manage_metadata grant, and knownGaps[0]'s prerequisite sentence says os dev — QA run #24783 (findings F7 and F2), round 11 of wave anchor #24579. No HTTP door placed the grant on the walled boot: the operator's insert into an organization it is not a member of is refused by the Layer 0 tenant check, and the owner's own insert by ADR-0090 D12 condition (c), manage_metadata being scope 'platform'. The recipe is the dogfood harness's system-context engine insert (wall-environment-metadata-refusal.dogfood.test.ts, its boot helper). A bare production os serve judges none of the walled prerequisites until OS_AUTH_SECRET is set (RUNNER.md), so the refusal sentence now names os dev. No clause changed",
-          "ref": "claude/issue-24579-v18-sweep-round11"
+          "ref": "#24801"
         }
       ]
     },

docs/qa/platform-checklist/areas/api-backend.json

@@ -1795,7 +1795,7 @@
           "revision": 4,
           "date": "2026-10-20",
           "change": "fixtures.knownGaps[2] re-pointed — QA run #24783 (finding F5), round 11 of wave anchor #24579. 'Needs an enterprise tenancy runtime no example app composes' is stale since 18.x step 4 (#24580): a scratch app declaring the open @objectstack/organizations composes the walled posture (RUNNER.md 'A walled boot is a fixture of its own'), and QA run #24783 measured the authority-first order on both walled postures. The line now points at that entry and names the handler whose order it asserts. No clause changed",
-          "ref": "claude/issue-24579-v18-sweep-round11"
+          "ref": "#24801"
         }
       ]
     },

docs/qa/platform-checklist/areas/identity-auth.json

@@ -2093,7 +2093,7 @@
           "revision": 5,
           "date": "2026-10-20",
           "change": "fixtures.requires[0]–[1] and personas[2] re-pointed — QA run #24783 (finding F8), round 11 of wave anchor #24579. requires[0]'s 'REFUSES TO BOOT … measured by QA run #23166' predates 18.x step 4 (#24580); the provisioning now points at RUNNER.md's walled-boot entry, keeping only the seeded-admin owner-email hint. requires[1] and personas[2]: the user gets its second membership by creating a second organization itself (QA run #24783, both postures), so the platform-admin add-member is not needed and the admin only mints the member. No clause changed",
-          "ref": "claude/issue-24579-v18-sweep-round11"
+          "ref": "#24801"
         }
       ]
     },

docs/qa/platform-checklist/areas/integration-system.json

@@ -688,7 +688,7 @@
           "revision": 9,
           "date": "2026-10-20",
           "change": "fixtures.requires[0]'s walled sentence and scratch-webhook recipe corrected — QA run #24783 (finding F4), round 11 of wave anchor #24579. 'Under a walled posture it would be refused as belonging to no organization' predates ADR-0131 ruling A: a declared webhook is deployment-wide under every posture (auto-enqueuer.ts admitsOrganization answers true for CachedSubscription.deploymentWide), delivers one row per event stamped with that event's organization, and is switched on by the operator under a wall, as wall-declared-webhook-deployment-wide.dogfood.test.ts pins and QA run #24783 measured on both postures. The scratch sys_webhook recipe now names its required definition_json and the lower-case method values sys-webhook.object.ts declares. No clause changed",
-          "ref": "claude/issue-24579-v18-sweep-round11"
+          "ref": "#24801"
         }
       ],
       "enumSource": {

docs/qa/platform-checklist/areas/platform-core.json

@@ -3311,7 +3311,7 @@
           "revision": 5,
           "date": "2026-10-20",
           "change": "steps[2]'s tenant lock made a named fixture prerequisite (fixtures.requires[2], new knownGaps[1]), and knownGaps[0]'s prerequisite sentence says os dev — QA run #24783 (findings F6 and F2), round 11 of wave anchor #24579. No HTTP door sets a tenant-row lock: sys_setting answers update 405 (apiMethods get/list) and the settings PUT writes values only, so the run stamped the lock with a system write on its scratch DB. A bare production os serve judges none of the walled prerequisites until OS_AUTH_SECRET is set (RUNNER.md), so the refusal sentence now names os dev. No clause changed",
-          "ref": "claude/issue-24579-v18-sweep-round11"
+          "ref": "#24801"
         }
       ]
     },