docs(qa): name this PR in round 18's history rows

The 19 history rows were committed with a placeholder ref because the PR
had no number yet. This swaps in #25018 and changes nothing else.

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

@@ -3057,7 +3057,7 @@
           "revision": 7,
           "date": "2026-10-21",
           "change": "Respelled — fixtures.knownGaps[0]: 'its own isolated scratch database' → 'its own scratch database'. PR #25003's out-of-scope finding (round 17 of wave anchor #24579; ACCEPT 6304389370, landing record 6304641541): 22 non-history texts in 17 items named the own-port boot or its DB with 'isolated' in other words, the phrasing round 12 found a runner reading as the `isolated` tenancy posture (OS_TENANCY_POSTURE=isolated). The new spelling names the boot or the DB by what it is, the run's own port and DB (RUNNER.md's trap-table counter: own port/DB, skill §0), and names no posture. Read at base 93e6c1a5f8. steps[0]'s 'a walled posture (group / isolated)' names the posture and is left as written. No clause changed",
-          "ref": "#PENDING-24579R18"
+          "ref": "#25018"
         }
       ]
     },

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

@@ -872,7 +872,7 @@
         { "revision": 1, "date": "2026-08-08", "change": "initial — the record-page approval surface (distinct from the inbox-drawer items): header Approve/Reject, one-dialog Reject (#3126), decision round-trip, and the lockRecord-driven inline-edit hide (#2902)", "ref": "claude/platform-test-checklist-ocwugl" },
         { "revision": 2, "date": "2026-10-17", "change": "the both-sides clause and step 9 named no persona, and the natural choice — the dev admin on a record routed away from them — sees 'Override Approve' / 'Override Reject' (#23878 checklist-accuracy finding), so it can never show the closed side; the step and clause 5 now name a non-override member. The record route in step 3 is the served /_console/apps/showcase_app/showcase_project/record/:id (the shorthand form redirects to it). Re-run on main c91af8ed6 with the console at objectui f8267df93aba: on a project whose budget approval is pending for the admin, the admin's header shows Approve and Reject; a contributor-bound member's header shows neither; with the admin's slot reassigned away the admin's header shows Override Approve and Override Reject", "ref": "#24036" },
         { "revision": 3, "date": "2026-10-20", "change": "source[2] re-pointed, and fixtures.knownGaps[0] added. PR #24982's pin finding: source[2] cited objectui's RecordDetailView.approvalDecisionActions.test.tsx, absent at both console pins. Read in a full objectui clone: objectui 99782f961 (objectui#3055) deleted it, and that commit is an ancestor of 616df6598b42 and of cf153eb2e535 (exit 0 both; control, cf153eb2e535 as an ancestor of 99782f961: exit 1). The same commit retired buildApprovalDecisionActions and moved the record page's decisions onto sys_approval_request's declared actions. At cf153eb2e535, RecordDetailView.approvalDeclaredActions.test.tsx holds the params half (the comment and declared outputs reach the POST to the request), and this repository's sys-approval-request.object.test.ts holds the one-dialog half. The knownGap tells a runner that the rest of the item still describes the retired header buttons. steps[0] respelled: 'boot showcase isolated' → 'boot the showcase on its own port and DB'. Round 12's out-of-scope finding (landing record 6287983829 on wave anchor #24579): the phrase 'showcase isolated' named the dogfood §0 own-port boot, and a runner read it as the `isolated` tenancy posture (OS_TENANCY_POSTURE=isolated). The new spelling names that boot by what it is, in RUNNER.md's own words for it (the trap table's counter: own port/DB, skill §0), and names no posture. Read at base e4d604efd3. No clause changed", "ref": "#25003" },
-        { "revision": 4, "date": "2026-10-21", "change": "Re-derived against the shipped record page. PR #25003's carried finding (round 17 of wave anchor #24579; ACCEPT 6304389370, landing record 6304641541): the steps, clauses, fixtures.requires[1] and source[0]–[1] still described the record header's hand-written Approve/Reject — buildApprovalDecisionActions, approve_request / reject_request in record_header, ordered -100 / -99, behind a client-side canDecide — which objectui 99782f961 (objectui#3055) retired before both console pins. Read at objectui cf153eb2e535 (RecordDetailView.tsx, DeclaredActionsBar.tsx, recordApprovalActions.ts, useRecordApprovals.ts, useConsoleActionRuntime.tsx, approvalOverride.ts) and at base 93e6c1a5f8 (sys-approval-request.object.ts; approval-service.ts attachViewers and decide; request-read-gate.ts; approvals-routes.ts; the showcase budget flow and approval seed): the record page runs sys_approval_request's declared record_section actions through DeclaredActionsBar above the page body, each gated by its visible predicate over the server's viewer block. title, fixtures.requires[0]–[1], steps[1]–[8], the verify and evidence of every clause, clauses [0], [1], [2] and [4] (whose oracle moves dom → api: the gate is the server's), negative[2] and source[0]–[1] rewritten; steps[9] (the off-slate admin's override framing) and source[4]–[5] (the server's declarations, viewer block, read gate and refusal) added; fixtures.knownGaps[0] removed, the retired text it warned about being gone. No automated ref is added: neither pin holds a clause whole at its layer (the objectui test mounts the page in jsdom over a fetch double, with a hand-written definition and the param dialog mocked; sys-approval-request.object.test.ts reads the declarations). The live verdicts at the pin are NOT MEASURED: the sources were read, not run", "ref": "#PENDING-24579R18" }
+        { "revision": 4, "date": "2026-10-21", "change": "Re-derived against the shipped record page. PR #25003's carried finding (round 17 of wave anchor #24579; ACCEPT 6304389370, landing record 6304641541): the steps, clauses, fixtures.requires[1] and source[0]–[1] still described the record header's hand-written Approve/Reject — buildApprovalDecisionActions, approve_request / reject_request in record_header, ordered -100 / -99, behind a client-side canDecide — which objectui 99782f961 (objectui#3055) retired before both console pins. Read at objectui cf153eb2e535 (RecordDetailView.tsx, DeclaredActionsBar.tsx, recordApprovalActions.ts, useRecordApprovals.ts, useConsoleActionRuntime.tsx, approvalOverride.ts) and at base 93e6c1a5f8 (sys-approval-request.object.ts; approval-service.ts attachViewers and decide; request-read-gate.ts; approvals-routes.ts; the showcase budget flow and approval seed): the record page runs sys_approval_request's declared record_section actions through DeclaredActionsBar above the page body, each gated by its visible predicate over the server's viewer block. title, fixtures.requires[0]–[1], steps[1]–[8], the verify and evidence of every clause, clauses [0], [1], [2] and [4] (whose oracle moves dom → api: the gate is the server's), negative[2] and source[0]–[1] rewritten; steps[9] (the off-slate admin's override framing) and source[4]–[5] (the server's declarations, viewer block, read gate and refusal) added; fixtures.knownGaps[0] removed, the retired text it warned about being gone. No automated ref is added: neither pin holds a clause whole at its layer (the objectui test mounts the page in jsdom over a fetch double, with a hand-written definition and the param dialog mocked; sys-approval-request.object.test.ts reads the declarations). The live verdicts at the pin are NOT MEASURED: the sources were read, not run", "ref": "#25018" }
       ]
     },
     {

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

@@ -1278,7 +1278,7 @@
           "revision": 5,
           "date": "2026-10-21",
           "change": "Respelled — fixtures.requires[2]: 'so an isolated boot without it dials 3000' → 'so a boot on its own port without it dials 3000'; fixtures.knownGaps[1]: 'so a dogfood-§0 isolated boot on a non-3000 port' → 'so a dogfood-§0 boot on its own non-3000 port'. PR #25003's out-of-scope finding (round 17 of wave anchor #24579; ACCEPT 6304389370, landing record 6304641541): 22 non-history texts in 17 items named the own-port boot or its DB with 'isolated' in other words, the phrasing round 12 found a runner reading as the `isolated` tenancy posture (OS_TENANCY_POSTURE=isolated). The new spelling names the boot or the DB by what it is, the run's own port and DB (RUNNER.md's trap-table counter: own port/DB, skill §0), and names no posture. Read at base 93e6c1a5f8. No clause changed",
-          "ref": "#PENDING-24579R18"
+          "ref": "#25018"
         }
       ]
     },
@@ -1836,7 +1836,7 @@
         { "revision": 5, "date": "2026-10-20", "change": "line citations re-pointed — the comma-range spelling that round 7 of wave anchor #24579 named (18.0 sweep; round 7's report 6281433885, out_of_scope_findings[1]). source[4] cited lines 707, 795, 816, 1322 and 1339 of the showcase flows index.ts in the comma-range spelling (authored in e0abc386a4 as the list 678 to 1339). At that commit those lines were the names and child flowName values of the three stock caller flows; at this base all of them have moved. source[4] now anchors the three callers, index.ts#TaskDoneNotifyOwnerFlow, #ProjectClosureFlow and #ReleaseSignoffFlow, and names each child in prose. The spelling is what #13786's strip left when it removed only the first range of a ':A,B' list, and the line-citation limb reads only the colon spellings, so no gate caught it. Where the surrounding words still describe the range the strip removed, the new citation names that code too. No clause's assertion changed", "ref": "#24752" },
         { "revision": 6, "date": "2026-10-20", "change": "fixtures.knownGaps[0] and negative[1] no longer score door arms from the engine pin, and negative[2] moved to steps[7]. PR #24891's carried finding (round 15's acceptance notes: the 'score from the pin' spelling, engine-pinned arms of api clauses) and QA run #24841's procedural-negative finding (18.0 sweep round 4 at 307ce4c4). Under RUNNER rule 6 the engine pin flow-activation-ledger.test.ts (over a fake store, read at base feb09db14a) is evidence of its own layer only: the non-packaged-caller and self-call arms, and negative[1]'s several-callers arm, are door answers, recorded blocked(fixture) without a scratch caller, with the pin beside them. negative[2] (the UI half belongs to another item) stated a scope rule with no product expectation, so it could only score not-run; its text moved, unchanged in substance, to steps[7]. No acceptance clause changed", "ref": "#24963" },
         { "revision": 7, "date": "2026-10-20", "change": "steps[0] respelled: 'boot showcase isolated' → 'boot the showcase on its own port and DB'. Round 12's out-of-scope finding (landing record 6287983829 on wave anchor #24579): the phrase 'showcase isolated' named the dogfood §0 own-port boot, and a runner read it as the `isolated` tenancy posture (OS_TENANCY_POSTURE=isolated). The new spelling names that boot by what it is, in RUNNER.md's own words for it (the trap table's counter: own port/DB, skill §0), and names no posture. Read at base e4d604efd3. No clause changed", "ref": "#25003" },
-        { "revision": 8, "date": "2026-10-21", "change": "Respelled — steps[6]: '(or discard the isolated DB)' → '(or discard the run's own DB)'. PR #25003's out-of-scope finding (round 17 of wave anchor #24579; ACCEPT 6304389370, landing record 6304641541): 22 non-history texts in 17 items named the own-port boot or its DB with 'isolated' in other words, the phrasing round 12 found a runner reading as the `isolated` tenancy posture (OS_TENANCY_POSTURE=isolated). The new spelling names the boot or the DB by what it is, the run's own port and DB (RUNNER.md's trap-table counter: own port/DB, skill §0), and names no posture. Read at base 93e6c1a5f8. No clause changed", "ref": "#PENDING-24579R18" }
+        { "revision": 8, "date": "2026-10-21", "change": "Respelled — steps[6]: '(or discard the isolated DB)' → '(or discard the run's own DB)'. PR #25003's out-of-scope finding (round 17 of wave anchor #24579; ACCEPT 6304389370, landing record 6304641541): 22 non-history texts in 17 items named the own-port boot or its DB with 'isolated' in other words, the phrasing round 12 found a runner reading as the `isolated` tenancy posture (OS_TENANCY_POSTURE=isolated). The new spelling names the boot or the DB by what it is, the run's own port and DB (RUNNER.md's trap-table counter: own port/DB, skill §0), and names no posture. Read at base 93e6c1a5f8. No clause changed", "ref": "#25018" }
       ]
     },
     {
@@ -1945,7 +1945,7 @@
         { "revision": 4, "date": "2026-10-19", "change": "acceptance[1] (clause, verify) counts the dropped keys the clone really drops — checklist-accuracy finding of the 18.0 QA sweep (QA run #24545, automation.packaged-flow-clone-contract acceptance[1]; wave anchor #24579 §3): FLOW_CLONE_DROPPED_KEYS is 10, not 9, since packages/runtime/src/flow-clone.ts appends 'protection' (#23120, ADR-0010 §3.5) to the 2 read decorations and 7 protection fields. Re-derived at base 9a7838edf5", "ref": "#24649" },
         { "revision": 5, "date": "2026-10-20", "change": "line citations re-pointed — the comma-range spelling that round 7 of wave anchor #24579 named (18.0 sweep; round 7's report 6281433885, out_of_scope_findings[1]). acceptance[3].verify cited line 439 of automation-flow-clone.test.ts in the comma-range spelling (authored in e0abc386a4 as the list 368-401 and 439). Those lines are unchanged at this base: the same-name 409 cases and the unknown-source 404 assertion. The verify now anchors the two codes those cases assert, automation-flow-clone.test.ts#RESOURCE_CONFLICT and #RESOURCE_NOT_FOUND. The spelling is what #13786's strip left when it removed only the first range of a ':A,B' list, and the line-citation limb reads only the colon spellings, so no gate caught it. Where the surrounding words still describe the range the strip removed, the new citation names that code too. No clause's assertion changed", "ref": "#24752" },
         { "revision": 6, "date": "2026-10-20", "change": "steps[0] respelled: 'boot showcase isolated against a file DB' → 'boot the showcase on its own port against its own file DB'. Round 12's out-of-scope finding (landing record 6287983829 on wave anchor #24579): the phrase 'showcase isolated' named the dogfood §0 own-port boot, and a runner read it as the `isolated` tenancy posture (OS_TENANCY_POSTURE=isolated). The new spelling names that boot by what it is, in RUNNER.md's own words for it (the trap table's counter: own port/DB, skill §0), and names no posture. Read at base e4d604efd3. No clause changed", "ref": "#25003" },
-        { "revision": 7, "date": "2026-10-21", "change": "Respelled — steps[8]: '(or discard the isolated DB)' → '(or discard the run's own DB)'. PR #25003's out-of-scope finding (round 17 of wave anchor #24579; ACCEPT 6304389370, landing record 6304641541): 22 non-history texts in 17 items named the own-port boot or its DB with 'isolated' in other words, the phrasing round 12 found a runner reading as the `isolated` tenancy posture (OS_TENANCY_POSTURE=isolated). The new spelling names the boot or the DB by what it is, the run's own port and DB (RUNNER.md's trap-table counter: own port/DB, skill §0), and names no posture. Read at base 93e6c1a5f8. No clause changed", "ref": "#PENDING-24579R18" }
+        { "revision": 7, "date": "2026-10-21", "change": "Respelled — steps[8]: '(or discard the isolated DB)' → '(or discard the run's own DB)'. PR #25003's out-of-scope finding (round 17 of wave anchor #24579; ACCEPT 6304389370, landing record 6304641541): 22 non-history texts in 17 items named the own-port boot or its DB with 'isolated' in other words, the phrasing round 12 found a runner reading as the `isolated` tenancy posture (OS_TENANCY_POSTURE=isolated). The new spelling names the boot or the DB by what it is, the run's own port and DB (RUNNER.md's trap-table counter: own port/DB, skill §0), and names no posture. Read at base 93e6c1a5f8. No clause changed", "ref": "#25018" }
       ]
     },
     {
@@ -2102,7 +2102,7 @@
           "revision": 7,
           "date": "2026-10-21",
           "change": "steps[3] rewritten to the Activation cell's real states. PR #25003's out-of-scope finding (round 17 of wave anchor #24579; ACCEPT 6304389370, landing record 6304641541): the step read \"confirm every switch reads On … 31 On / 1 Off\", and at the console pin cf153eb2e535 the cell carries a badge beside the switch that reads 'Not running here', switch still checked, for an enabled flow whose _status row carries an unboundCause (objectui#13159; packagedFlows.ts activationReading, PackagedAutomationPage.tsx, blobs a85c96d28e5a and f4aa90e11d32). On a default boot showcase_scheduled_digest and showcase_task_due_reminder carry unboundCause 'deployment_policy' (RUNNER.md, the scheduled-work entry; describeUnboundReason in service-automation engine.ts), so a count of 'On' badges is not 31. The step now names the three readings, and states the count with its derivation from the 32 flows allFlows declares at base 93e6c1a5f8: 29 On / 2 Not running here / 1 Off on a default boot, 31 On / 1 Off with the switch exported, and it tells the run to reconcile against _status. No clause changed; the live reading at the pin is NOT MEASURED",
-          "ref": "#PENDING-24579R18"
+          "ref": "#25018"
         }
       ]
     },