qa(checklist): RUNNER.md — 3 stale environment facts from the 18.2.0 release sweep (#25807) #25850

Filing gate: maintainer-directed task. Filed by the 18.2.0 release-assessment thread · session_01G3h9iZTpL8aCiXbfsp8H5u. ⛔ Not a claim, ⛔ not dispatched.

Maintainer's words (project thread, 2026-10-25, verbatim): 22:54Z 「约 300 条清单准确性问题：是不是应该开卡？」, then 22:55Z 「写issue，不派发」.

Parent: wave anchor #25807 (18.2.0 release test sweep). RUNNER's extraction obligation parks checklist-accuracy findings on the anchor; the maintainer asked for them as issues, so the wave's findings are split into one card per ledger file and the anchor links each card. This is not a release blocker, so it carries no target:v18.

Reader who acts: the lane owning docs/qa/platform-checklist/** (domain:devx). Dedupe (open and closed): no card holds these lines; the 18.0 precedent closed its accuracy rows on its anchor #24579.

Wanted

For each line below, edit docs/qa/platform-checklist/RUNNER.md: correct the environment fact, citing the run record the line comes from. Keep pnpm check:platform-checklist green. A line that turns out to describe a product defect rather than stale text gets its own card instead of a ledger edit.

Findings (3)

From #25812 — priority:P0, 23 items, at 6679644a, pin b41ed7f68956

• RUNNER environment facts: (1) the walled-boot entry is stale — examples/app-showcase/package.json now declares @objectstack/organizations, so a walled run boots from the tree with three env vars, no scratch copy; (2) the Playwright entry is stale — /opt/pw-browsers now holds chromium 1243 and the alias resolves there (the alias advice still works).

From #25817 — release-18.2.0-manual-set, 29 items, at 6679644a, pin b41ed7f68956

• RUNNER.md "export OS_PORT" environment fact. At 6679644, os dev boots from the prebuilt dist/objectstack.json. With OS_PORT=41302 exported, GET /api/v1/meta/connector/showcase_status_api still answers baseUrl http://127.0.0.1:3000. Yet live connector_action reached 41302: ping.body uptime matched the boot, and nothing listens on 3000. So the Check that entry prescribes would misreport the fixture.

From #25823 — addendum, identity-auth.admin-lifecycle-operations at 17f8217b, after #25626

• RUNNER.md "Walled personas come from the admin door": stale after feat(plugin-auth): multi-org Create User joins the administrator's current organization #25626 — the operator must create and set-active an organization before Create User.

Acceptance

• Every line above is either applied (item revised, revision bumped, history cites the record) or answered on this card with the reason it was not.
• pnpm check:platform-checklist is green.
• The PR links this card and [sweep] v18.2.0 release test sweep #25807.

Generated by Claude Code