QA wave R0: provision the shared QA tree and take the machine-lane baseline at e4e5c6e3

[os-zhuang]

Part of #9296. Round 0 of the full platform-checklist regression — everything the later rounds stand on. This card produces no PR and no qa-run issue; it produces one comment on itself carrying the readings, and a structured report to the PM.

What this round owns

1. One QA tree for the whole wave. git worktree add ../objectstack-qa-wave <sha> at e4e5c6e3c608b1b807c83a0d5b734f213eb1a1dd, then pnpm install there. Re-fetch first and record the sha you actually get — if main moved, the wave re-pins to yours and you say so.
   • ⛔ Do not create a second worktree or a second pnpm install anywhere. The container has a fixed disk allowance (~30 GB free at dispatch); rounds R1/R2/R3 all reuse this one tree. Isolation between runs is per-item port + file DB, not per-item tree.
2. Console build — start it first, it is the long pole. pnpm objectui:build builds @object-ui/console at the pinned .objectui-sha (665661ab…) into packages/console/dist. Cold monorepo: budget 10–30 min; run it in the background while the gates below run. ⛔ Never pnpm objectui:refresh — that re-bumps the pin to the local ../objectui HEAD (currently 195b9e4a, ≠ the pin) and every later browser verdict would describe a commit this repo does not pin.
   • packages/console/dist does not exist right now, so /_console/ 404s until this finishes. That is a prerequisite, not a defect.
   • Finish with pnpm check:console-sha and report its output.
3. Repo machine gates, with timings (the timings are a deliverable — they budget R1–R3):
   • pnpm check:platform-checklist (expected green: 15 areas / 182 items / 28 kinds mapped / 2 waived)
   • pnpm typecheck
   • pnpm test
   • objectstack verify against the showcase app, and the packages/qa/dogfood golden suite
4. Smoke the boot path the later rounds depend on: pnpm -C examples/app-showcase exec objectstack dev --ui --seed-admin -p <free non-default port> -d file:/tmp/qa-wave/r0.db, poll /api/v1/health → 200, confirm /_console/ serves after the build. Record the port/DB convention the next rounds should follow.

Reporting

Comment on this issue (English) with: the sha actually tested, .objectui-sha, per-gate command → exit status → wall-clock, the console-sha comparison, and the boot smoke result. Then return the PM report JSON.

A red gate on main is a finding, not your task. Do not fix it: reproduce it twice, check whether it also fails on the merge-base, and file it as its own issue with the failing command and output. Say so in the report.

Non-negotiable for this card

• No PR from this card. Nothing you produce lands in the repo tree.
• Report faithfully: a gate you did not get to is "not run", never "passed". If pnpm test cannot finish in a sane budget, report how far it got, which packages are covered, and stop — a partial run reported honestly is a good outcome; an implied full green is not.

[os-zhuang]

Claim: PM loop round 1 (QA wave #9296)
Session: session_01Ai9gUdihXjg7FumzsBNSSs
Branch: none — this card produces no commit and no PR
Worktree: objectstack-qa-wave (the shared QA tree this card provisions; every later round reuses it)
Domain: domain:devx
File surface: none in the repo tree. Writes go to /tmp/qa-wave/**, node_modules/, and packages/console/dist/ (git-ignored build output). Stop on breach and explain in the report.
Container & model: M, mode:subagent, model: opus — install/build failure diagnosis and the "is this red pre-existing on main?" call are judgment, not gate-mechanical.
Serial constraints cleared: no in-flight card touches the repo tree from this wave. Runs concurrently with #9299, which is disjoint by construction — #9299 edits docs/qa/platform-checklist/** in its own worktree and is barred from pnpm install, so the two never contend for the container's disk allowance.

Routing authority: maintainer direct-dispatch channel — 「按照你的建议执行」 (2026-08-17), authorizing the five-round orchestration proposed in-session and recorded on #9296.

---

Generated by Claude Code