docs(qa): wave-2 checklist-accuracy close-out, slice A — seven areas and three RUNNER facts - #26969

Part of #25807 (wave-2 accuracy, slice A)

Clause-②: no
Metadata-protocol: none

维护者速读

• 改了什么：按 18.2.0 第二波五份测试记录，修正 7 个领域共 37 条测试清单条目和 1 个共享配方里的过时描述，并给 RUNNER.md 补 3 条环境事实。只改文档，不动产品代码。
• 为什么改：第二波运行发现这些条目的步骤、字段名、错误码或引用的测试文件已与当前代码不符，下一轮运行会被误导、误判或白跑。
• 风险与回滚：只影响 QA 清单文本，不改任何断言的判定标准（新增的只有 trigger-status-contract 的第五行和 query-contract-matrix 的六个运算符变体）。每条 revision +1、追加一行 history，回滚就是 revert 本 PR。
• 先看：areas/integration-system.json 的 webhook-lifecycle（QA run · surface:mixed (90/90) · 36b2889c · 2026-10-12 · 72 PASS / 10 PARTIAL / 8 FAIL / 0 BLOCKED / 0 NOT-RUN #23166 是已关闭的运行记录，不是阻塞卡）；areas/automation.json 的 trigger-status-contract（新增 422 FLOW_INPUT_SCHEMA_INVALID 行）；RUNNER.md 的三条新事实。
• 两分钟验证：node scripts/check-platform-checklist.mjs，预期打印 check-platform-checklist: OK、退出码 0。
• 需要你做的：无，席位落地。

What changes

The slice-A close-out of the wave-2 checklist-accuracy findings that RUNNER.md routes to the wave anchor ("close out through the wave's anchor card … not extracted"). Sources: anchor comments 6433587719, 6433708086, 6433784748, 6433878766, 6433966437 and the run records #26450, #26456, #26468, #26476, #26481. Every finding was checked against the code at base e4ba846f before its edit; the history row of each item names the file read.

• 37 items in automation, cli, api-backend, identity-auth, integration-system, search and ux-conventions: revision +1 from main's value and one appended history row each, citing the run record that found it. No existing history row is touched.
• 1 shared recipe: search.json qa-contributor-bound-member step 5 asks for a non-churned account (recipes carry no revision; its provenance line records the change).
• RUNNER.md: (1) a per-boot -d DB does not isolate the showcase's upload root or its external datasource file; (2) the process-kill hook refuses one command that runs ps, grep and a kill, so the group stop runs on its own; (3) the OS_PORT-connector entry now says os dev compiles by default since cli/dev: on an os dev boot with OS_PORT set, served connector metadata reads the build-time baseUrl (http://127.0.0.1:3000) while dispatch reaches the live port, so /meta disagrees with what runs #26130.
• automation.packaged-flow-clone-contract changes surface from api to mixed: its acceptance[6] is a Studio browser leg.

No change, and why

• cli.migrate-plan-apply-json: already corrected by qa(checklist): cli.migrate-plan-apply-json enumerates 19 os migrate subcommands; audit-key-material (#26772) makes 20, so the item's --json sweep no longer covers the family #26795 (dispatch note).
• The api-backend items re-pinned the same day by qa(checklist): api-backend — pin the Tier 1 clauses the 18.2.0 sweep scored partial at the layer their oracle names (11 items) #26572 (declarative-endpoint-execution, packaged-action-disabled-dispatch, action-activation-door-contract, rest-crud-config-contract, rest-batch-config-contract, rest-metadata-config-contract, rest-route-generation-tombstones, second-object-exposure-and-internal-fields, data-request-shape-and-query-arity, meta-read-doors-v18, error-sentences-and-unique-violation-wire-code): each wave-2 line on them was read against the current text, which already names the pins and the layer each reaches (for example, rest-crud-config-contract says its discovery pin runs at /objects, and rest-route-generation-tombstones says §E's plugin-path case drives batch.defaultAtomic).
• Lines that read "ref accurate" (confirmations, nothing stale): automation.durable-suspend-restart (its ref already calls the fixture the pin's own), paused-run-trigger-record-masked, flow-registration-verdict-on-read, flow-authoring-refusals-v18, flow-run-semantics-v18, inbound-hook-timestamped-signature, scheduled-work-opt-in; cli.organization-ownership-ceremony, meta-package-flags-and-explain, validate-v18-authoring-verdicts, verify-derived-proof-families; cli.migrate-meta-write-stored-and-all (a scoring divergence; its ref claims no command layer).
• automation.packaged-flow-subflow-disable-refusal: the run confirmed knownGaps[0] live, and its N1 fixture gap already has a recipe (qa(checklist): automation — provisioning recipes for a second packaged caller and the 503 STORE_UNAVAILABLE trigger arm #26622).
• integration-system.connector-auth-kind-application: its ref already names both pins the mapping cited.
• identity-auth.two-factor-enrollment-reveal and two-factor-backup-codes: the shared two-factor lines are applied where the items read rows or settings; backup-codes already names the DB-file read.
• The identity-auth (9) and search (3) items of QA run · release-18.2.0-w2-tier1-b (80/80) · 756220c4 · 2026-10-27 · 15 PASS / 64 PARTIAL / 1 FAIL / 0 BLOCKED / 0 NOT-RUN #26450 carry clause verdicts only, no accuracy line.
• cli.scaffold-first-run's revision-6 history row says 'seven clauses' for five: history rows are append-only, so it stays.
• Outside slice A, not touched: the v17 --legacy-peer-deps recipe line lives in platform-core.v18-boot-refusals fixtures, and studio-authoring.draft-publish-lifecycle's METADATA_CONFLICT / NO_DRAFT lines belong to slice B.

Tests

No product code changed. Gates at head 0a7d5b4f (after merging origin/main):

node scripts/check-adr-links.mjs                                exit 0
node scripts/check-adr-links.mjs --self-test                    exit 0
node scripts/check-closing-keyword-parity.mjs                   exit 0
node scripts/check-closing-keyword-parity.mjs --self-test       exit 0
node scripts/check-comment-mask-corpus.mjs                      exit 0
node scripts/ci/plan-test-core-shards.mjs --self-test           exit 0
pnpm --filter @objectstack/lint run check:doc-formula-expressions  exit 0 (exit 3 before building @objectstack/formula and @objectstack/lint)
pnpm check:ci-filter-parity                                     exit 0
pnpm check:cross-package-test-inputs                            exit 0
pnpm check:doc-authoring                                        exit 0
pnpm check:driver-memory-census                                 exit 0
pnpm check:gitlink-declared                                     exit 0
pnpm check:nul-bytes                                            exit 0
pnpm check:platform-checklist                                   exit 0
pnpm check:refd-timer-probe                                     exit 0
pnpm check:watch-hint-literal                                   exit 0
✓ dispatch-gates --ran: 16 derived famil(ies) accounted for — 16 run, 0 NOT-MEASURED (a DERIVED zero — all 16 recorded an exit code and none of them is 3).

check-platform-checklist: OK — 16 areas, 329 items (324 active, 1 planned); coverage: 39 kinds mapped, 4 waived; traps: 19 documented, 19 in use; provisioning: 10 area recipes, 15 item references resolved (2 area-qualified), 10/10 recipes referenced

A script compared every item in the seven files against origin/main: 37 changed, each at main's revision + 1 with exactly one appended history row and the earlier rows byte-equal.

Acceptance notes

Observations from these records that are not ledger edits (reported to the seat, not filed here):

• webhook-lifecycle A2: whether a flow node's predicate multi-write should carry the organization is a maintainer question raised in QA run · surface:mixed (90/90) · 36b2889c · 2026-10-12 · 72 PASS / 10 PARTIAL / 8 FAIL / 0 BLOCKED / 0 NOT-RUN #23166, and no open issue carries it (its successor anchors closed with it noted). The wave-2 run measured the block again.
• A retired-filter-operator refusal is cut at the 500-character client-message bound before the $contains alternative its prescription names (QA run · release-18.2.0-w2-manual-api (29/29) · 756220c4 · 2026-10-27 · 27 PASS / 2 PARTIAL / 0 FAIL / 0 BLOCKED / 0 NOT-RUN #26476; truncateClientMessage).
• The kanban drop gate's dimmed lane carries no reason text (QA run · release-18.2.0-w2-manual-browser (34/34) · 756220c4 · 2026-10-27 · 30 PASS / 3 PARTIAL / 1 FAIL / 0 BLOCKED / 0 NOT-RUN #26456), against the disabled-control convention.
• After a failed datasource connect, POST /api/v1/datasources/NAME/test answers 'no registered driver to introspect', which names no cause (QA run · priority:P0 (23/23) · 756220c4 · 2026-10-27 · 20 PASS / 3 PARTIAL / 0 FAIL / 0 BLOCKED / 0 NOT-RUN #26481).

Verification

node scripts/check-platform-checklist.mjs exits 0 on the head. Run git diff origin/main...HEAD -- docs/qa/platform-checklist/areas to see that each hunk is the item's text plus one new history row.

🤖 Generated with Claude Code

https://claude.ai/code/session_01QSeKYkXktsD6m4eAJ18rUE

Generated by Claude Code