QA P0 release sweep 2026-10-01 — checklist re-point for query-contract-matrix clause 6 + the run's checklist-accuracy findings and fixture gaps (anchor for #21056)

[objectstack-fleet]

Filing gate: ③ a maintainer-directed task — the maintainer, after the P0 run, chose to file every extraction including this anchor (Claude Code session session_01MRdbfpy4sQT8bUjmMhxsN7, 2026-10-01, selected option verbatim: 「全部立卡（推荐）」). Reader: the lane owning docs/qa/platform-checklist/** (checklist edits: revise the item, bump revision, append history, keep pnpm check:platform-checklist green). Dedupe: no open sweep anchor for this run (searched "QA run platform checklist sweep wave anchor tracking release", open + closed; #9296 is the August regression epic).

QA-source: #21056 · api-backend.query-contract-matrix · acceptance[5]

This card is the wave anchor for run #21056 (RUNNER "Extraction obligation": checklist-accuracy findings and fixture gaps close out here, not as separate cards). Product defects from the run are extracted separately: #21052, #21057, #21058, objectstack-ai/objectui#11326, objectstack-ai/objectui#11327.

1. Re-point (owns a red row) — api-backend.query-contract-matrix acceptance[5]

Disposition stale spec, independently verified. The clause (rev 2, 2026-08-18) expects 400 INVALID_FILTER for a scalar $nin comparand on the POST /query door in both spellings. Since #20116 the refusal happens in the request schema (FilterConditionSchema.superRefine(checkFilterConditionComparands); the AST arm via lowerFoldedTransportValues), and the POST door answers schema failures 400 VALIDATION_FAILED with a fields[] entry at query.where… naming operator, field and expected array — a posture pinned by rest-server-repeated-filter-param.test.ts and analytics-filter-refusal-envelope.test.ts. GET $filter still answers INVALID_FILTER. Revise: POST both spellings → 400 VALIDATION_FAILED + fields[]; GET → 400 INVALID_FILTER; both never 500, never widen. Also: step 5 / acceptance[2] — dotted fields: ['account.name'] is refused 400 INVALID_FIELD by design (prescribes expand); negative[0] — {"filter": …} is now a declared transport alias, so use an undeclared key (400 INVALID_FIELD). Residual for the maintainer, not a defect: GET and POST answer different codes for the same condition (#8001 family).

2. Checklist-accuracy findings

• Personas, all member-persona items + recipe search:qa-contributor-bound-member step 1: stock audience posture is invite_only; POST /api/v1/auth/sign-up/email answers 403 SELF_REGISTRATION_CLOSED. Every "fresh sign-up" needs admin invite-member first (or admin create-user + change-password, which returns mustChangePassword:true).
• access-security.crud-permission-matrix: automated.ref still says "25 showcase_* rows / 100 cells", clause/fixture say "31 rows"; actual access-matrix.json 47 rows, the pin judges 41 showcase_* rows = 164 cells (87 allow / 77 deny). acceptance[1] should list 405 OBJECT_API_METHOD_NOT_ALLOWED for sys_user create/delete (every caller). acceptance[5] (guest create-without-read) is unobservable on stock — add to knownGaps or re-point to the public-form lane. automated.ref's "pinned on both sides" for delegate sys_user_position writes does not hold on the dev boot (the pin runs with no organization — see [finding] The delegated-admin gate resolves an EMPTY subtree on a stock objectstack dev boot — seeded business units are organization-less while every session carries an active organization, so every in-scope delegated write is refused #21057). Probe delegate edit/delete on a row the delegate created (others' rows hit the ownership floor).
• access-security.write-path-guards acceptance[5]: "drops the field for the batch" → per row: only the locked row's field is dropped, reported in results[i].droppedFields.
• access-security.owd-sharing-matrix step 1 / crud-permission-matrix persona recipe: grant the position, not the set directly (reason with the maintainer; see [showcase][security] An owner-isolation policy in the showcase's contributor permission set does not hold for every way a member can hold the set — detail withheld pending maintainer #21052).
• access-security.rls-both-sides: the private "D11" handle collides with a public "D11" row in FOLLOW-UPS.md §7c; history/cross-references say "clause 5" (0-based) where runs say clause 6 (1-based).
• access-security.anonymous-deny-surfaces: the pin does not cover /batch or /security/explain (both 401 rest-flat live) — extend it.
• ai.mcp-stdio-fail-closed: no single showcase persona carries both RLS-hidden rows and an FLS-masked field on one object (use contributor for RLS, client_liaison for FLS); details.forbiddenFields is not on either wire; step 1 names no host command (os dev prints banner lines to stdout — use os start).
• api-backend.packaged-action-disabled-dispatch knownGaps: the MCP door IS drivable live over HTTP (POST /api/v1/mcp, tools/call run_action).
• platform-core.seed-integrity step 5 / platform-core.boot-health step 4: no SeedLoader lines at the default log level — name the banner Seeds: row or --log-level info [Seeder] Seed loading complete {…errored}. boot-health acceptance[2] "no ⚠" collides with the two stock unbound — disabled by deployment policy lines; name the misauthored classes instead.
• cli.dev-boot-contract: steps 5/7/8 (touch sources, nothing-chosen DB, legacy dev.db) are unsafe in a shared tree — prescribe a scratch copy of the app; name the expected exit code (SIGINT → 0 under pnpm exec, --fresh SIGINT → 130); the "Dev admin … seeded" banner reprints on later boots and is not seeding evidence.
• integration-system.datasource-credential-refusal-matrix: knownGaps "the wizard can plant a legacy alias row" is false (400) — planting needs a stopped-server sys_metadata write; acceptance[6] "PUT the response back" — the admin door is PATCH-only; acceptance[3] should name the admin door (the console reads hasSecret / redactedConfigKeys there); step 5 path GET /api/v1/meta/datasource/{name}; source omits the composed twin 18.datasource-credentialsref-mongo-composed-no-username-refused.ts, and the url-branch entry still says the composed branch is "Deliberately NOT refused" (stale since Composed-branch twin of #9041: external.credentialsRef bound + discrete mongo fields naming no username is the same silent no-op, unrefused #9147).
• platform-core.console-login: acceptance[2].verify still says "after clearing cookies" (rev 3 step 5 expires with POST /auth/sign-out); acceptance[0] "nav + header" — /_console/home has a launcher, not a sidebar.
• platform-core.nav-surfaces-render: the pin's playwright.config.ts hardcodes PORT = 3000 (no baseURL / executablePath override); its non-chart check can pass on the boot splash (22/49 first <main> texts were "Initializing application…"); SURFACES covers 31 of 49 served destinations — add the 18 hand-walked ones.
• platform-core.builtin-apps-nav-render: counts moved (Setup 45, Account 8; acceptance[4] "7 vs 7" → 8 vs 8); member fixture cannot be a fresh sign-up — record the seeded plain persona (demo-personas.ts); Browse Marketplace needs egress to cloud.objectos.ai (knownGap).
• records-forms.crud-roundtrip: acceptance[6]'s readonly-column half is unobservable on the stock seed (no approval_status; lead_score null everywhere); the own-row invoice must not point at the run's account (later delete → 409 DELETE_RESTRICTED); list quick-search text persists across reloads.
• approvals.account-app-entry: acceptance[6] should say 中文（中国） (zh-CN) — no zh option exists; acceptance[1] tab labels listed only in zh; acceptance[5] fixture → use a persona-owned invoice set to sent (unreadable rows render no link); the seeded sign-off request was routed before the persona held finance — launch a new one.
• studio-authoring.first-run-loop: object name is repairs_repair_ticket (package namespace), not repair_ticket; knownGaps "a new app scaffolds ZERO nav items" is stale (checkbox default on); step 9 — the UI hides New object / Add field on read-only packages, so the server probe is a forged request; the New object dialog now requires an OWD choice; acceptance[0]'s cited objectui pin targets testids that do not exist at the pin.
• RUNNER "Environment facts": CRUD tail is now 15 verified … 1 needs-fixture, 8 skipped; verify --rls probes 10 of 10 positions (digits only).

3. Fixture gaps and environment (record, no edit needed unless chosen)

No Postgres/MySQL/Mongo runnable in the sandbox (a wire-level fake PG served the connect legs); sandbox egress denies cloud.objectos.ai and map tiles; the container's Node v22.22.0 is below the pinned objectui's jsdom engine floor; runner port ranges must avoid the egress proxy's 127.0.0.1:41333.

---

Generated by Claude Code

[objectstack-fleet]

Triage: first grade — documentation · priority:p1 · domain:devx · area:devpath · pm:queue. The P0 release sweep's anchor: re-point the stale red row first

Triage seat (objectstack-wide, seat post #6015) · session_01AavokzJ5DndAwitDXvKy4U · 2026-10-01T04:56Z. ⛔ Not a claim, ⛔ not a dispatch.

Why p1. It is the release-priority rule: this anchor owns a red row in the P0 release sweep that is a stale spec, not a product defect. A false red in the P0 sweep stands in the way of release sign-off.

Routing. docs/qa/platform-checklist/** is domain:devx.

Direction. It is the card's own scope, confirmed:

1. The re-point: api-backend.query-contract-matrix acceptance[5] expects what the doors answer since spec: FilterConditionSchema (the save-time door) admits a non-boolean $null / $exists flag, so a stored dataset or widget filter carrying one saves clean and is refused 400 on every query face #20116. The POST door gives 400 VALIDATION_FAILED with fields[], and GET $filter gives INVALID_FILTER. Revise the item, bump revision, append history, and keep pnpm check:platform-checklist green.
2. Then the run's checklist-accuracy findings and fixture gaps close out here, per RUNNER's extraction obligation.

• The product defects stay on their own cards: [showcase][security] An owner-isolation policy in the showcase's contributor permission set does not hold for every way a member can hold the set — detail withheld pending maintainer #21052, [finding] The delegated-admin gate resolves an EMPTY subtree on a stock objectstack dev boot — seeded business units are organization-less while every session carries an active organization, so every in-scope delegated write is refused #21057, [finding] POST /api/v1/datasources (and the PATCH door) never run DatasourceSchema's cross-field refinements — a mongo credentialsRef pairing that os build and PUT /meta refuse is accepted 201, and the bound secret is silently unused #21058, [finding] @object-ui/i18n never loads the built-in Chinese catalogue for a stored zh-CN locale — the lazy loaders are keyed by base code zh with no region fallback, so after a reload all Console chrome reverts to English objectui#11326 and [finding] The vendored Console bundles TWO zod instances (4.4.3 + the spec's 4.6.1), so spec-derived Studio schemas crash — the New Package dialog cannot create a package; dashboard/report inspectors show "Spec schema unavailable" objectui#11327.

---

Generated by Claude Code

[objectstack-fleet]

Claim: PM loop round 2 (maintainer queue jump)
Session: session_01JAhu8u8QfBvRjVZDox7CP9
Account: os-bill (the seat's linked user as GET /user answers it; the card's assignee from this act)
Branch: claude/issue-21060-p0-sweep-checklist
Worktree: objectstack-issue-21060
Domain: domain:devx
Seat: domain:devx#2 (seat post #20163)
Provenance:

• Who: the maintainer.
• Verbatim: 「21060 插队」.
• Where: this seat's session chat, 2026-10-01T05:25Z.
• This is a maintainer-directed queue jump, which heads the take order.
  File surface:
• docs/qa/platform-checklist/areas/*.json: only the items the card names. Each edit is a real revision: bump revision and append history.
  • §1 is first: api-backend.query-contract-matrix acceptance[5], plus its step 5 / acceptance[2] and negative[0].
• docs/qa/platform-checklist/RUNNER.md: the "Environment facts" lines the card names.
• docs/qa/platform-checklist/FOLLOW-UPS.md: only the §7c "D11" handle collision.
• packages/qa/dogfood/test/showcase-anonymous-deny-surfaces.dogfood.test.ts: only to cover /batch and /security/explain.
• examples/app-showcase/e2e/showcase-smoke.spec.ts and examples/app-showcase/playwright.config.ts: only the three platform-core.nav-surfaces-render findings (the hard-coded port, the boot-splash false pass, the 18 hand-walked surfaces).
• ⛔ No product code. The run's product defects stay on [showcase][security] An owner-isolation policy in the showcase's contributor permission set does not hold for every way a member can hold the set — detail withheld pending maintainer #21052, [finding] The delegated-admin gate resolves an EMPTY subtree on a stock objectstack dev boot — seeded business units are organization-less while every session carries an active organization, so every in-scope delegated write is refused #21057, [finding] POST /api/v1/datasources (and the PATCH door) never run DatasourceSchema's cross-field refinements — a mongo credentialsRef pairing that os build and PUT /meta refuse is accepted 201, and the bound secret is silently unused #21058, [finding] @object-ui/i18n never loads the built-in Chinese catalogue for a stored zh-CN locale — the lazy loaders are keyed by base code zh with no region fallback, so after a reload all Console chrome reverts to English objectui#11326 and [finding] The vendored Console bundles TWO zod instances (4.4.3 + the spec's 4.6.1), so spec-derived Studio schemas crash — the New Package dialog cannot create a package; dashboard/report inspectors show "Spec schema unavailable" objectui#11327.
• Stop on breach and explain in the report.
  Container & model: M, mode:subagent, default tier (dispatch-gates --tier at dff98c1f51: no path-derived mandate)
  Clause-②: no
  Thread-read: 5925034641
  Serial constraints cleared:
• At origin/main dff98c1f51, open PR docs(qa): re-point the two-factor-disable mfa_required anchor at a declaration the resolver reads #21027 touches docs/qa/platform-checklist/areas/identity-auth.json. That is ordinary concurrency outside SINGLE_CLAIM_PATHS, and this card names no identity-auth.* item.
• No open PR touches the two pin files or the showcase e2e config.

---

Generated by Claude Code

[objectstack-fleet]

Additional checklist-accuracy finding, surfaced by the #21052 fix (PR #21104, Acceptance notes):

• docs/qa/platform-checklist/areas/search.json describes invoice_own_rows as carrying positions: ['contributor'] in two places: in the prose of an expect step and in a source line. Once fix(showcase): the contributor set's row-level policies apply to every holder of the set #21104 lands, the showcase contributor set's row-level policies carry no positions list, so that parenthetical becomes stale and should be revised with the rest of this anchor's edits.

---

Generated by Claude Code

[objectstack-fleet]

os-dev-report
{
"issue": 21060,
"status": "done",
"branch": "claude/issue-21060-p0-sweep-checklist",
"pr": "#21111",
"session": "session_01JAhu8u8QfBvRjVZDox7CP9 (mode:subagent, the PM's session id)",
"premise_still_valid": true,
"summary": "Section 1: api-backend.query-contract-matrix re-pointed (rev 3): POST /query answers 400 VALIDATION_FAILED with a located fields[] entry in both spellings, GET $filter answers 400 INVALID_FILTER, dotted fields refused INVALID_FIELD by design, and the widening negative moved off the declared filter alias; each claim was grounded in source plus a local schema parse. Section 2: 17 checklist items, the search recipe, RUNNER Environment facts and FOLLOW-UPS 7c were revised, each with a bumped revision and a history entry naming #21060/#21056, and every clause was grounded in source, a live probe on a stock dev boot, or objectui at the pin. Two pins extended: the dogfood anonymous-deny pin now covers POST /batch and GET /security/explain (48 tests, ablation-proven), and the showcase smoke reaches all 49 nav destinations, waits past the boot splash and takes SMOKE_API_URL / OS_TEST_CHROMIUM_EXECUTABLE_PATH (49 passed against a console built at the pin). Findings not acted on are listed in the PR body with reasons.",
"tests": "On de73aa8 (after merging origin/main 9b81314): check:platform-checklist exit 0. Before, on base 6f57888, it was exit 1 with the single pre-existing identity-auth #twoFactor problem, which upstream fixed. --self-test exit 0 (221 assertions). Dogfood pin 48/48 on a rebuilt closure. Ablations, each through scripts/ablation-replace.mjs: the mutation was proven on disk (anchor 1 -> 0, blob changed), and the restore was proven (blob == HEAD 35985879ce93, git diff HEAD empty). Unrouting the explain probe turned exactly 3 cases red (expected 404 to be 401; expected 404 not to be 404); the batch probe likewise. Showcase smoke 49 passed (2.6m) on port 43871 with /opt/pw-browsers/chromium against packages/console/dist stamped e420df310f5b; an instrumented one-off run, restored afterwards, saw 29 of 49 surfaces on the boot splash first. Both typechecks exit 0, with the edited files in each program. Live probes on stock dev boots, all servers killed by recorded PID: verify --rls (15 verified/1 needs-fixture/8 skipped; 10 of 10 positions; all-personas 38 PROVEN); os dev vs os start stdout (15 vs 0 lines); datasource wizard alias 400, admin PUT 405, meta GET 200; Setup 45 / Account 8 leaves for admin, Account 8 for the seeded member. dispatch-gates: 55 derived, 55 run, 54 exit 0, check:dual-build-cjs-loads NOT MEASURED (prerequisite).",
"mcp_calls": "0",
"api_writes": "4 REST writes through 3 relay dispatches. The dispatches are POST /repos/objectstack-ai/objectstack/dispatches x3 (fleet-write relay; runs 36829737405, 36829786721, plus the report-comment run). The writes are POST /repos/objectstack-ai/objectstack/pulls (draft #21111); POST /repos//issues/21111/labels (skip-changeset); POST /repos//issues/21111/assignees (os-bill); POST /repos//issues/21060/comments (this report). git push is not counted. No PATCH of the PR body.",
"open_questions": [
{
"question": "The Personas finding covers 'all member-persona items'. I updated the shared recipe and the P0 items this run drove (crud-permission-matrix, write-path-guards, rls-both-sides, builtin-apps-nav-render, approvals). About 28 other active items still describe a 'fresh sign-up', which the invite_only default refuses 403 SELF_REGISTRATION_CLOSED, and several sit in identity-auth.json. How should the rest be closed?",
"options": [
"A: one RUNNER 'Environment facts' bullet (stock posture invite_only; mint members invite-first or via admin create-user). This covers every item at once. It is outside this claim's RUNNER surface, so it needs a patch round or follow-up.",
"B: a per-item sweep of the ~28 items, each revised with revision+history.",
"C: leave as is; each item gets corrected when a run next trips on it."
],
"recommendation": "A. Real business need: the posture is measured, so every member-persona run hits the 403 today. Long-term soundness: one standing fact, not 28 drifting copies; the area-recipe discipline already prefers one home. Preventing AI-authoring errors: a runner reads Environment facts first, so it cannot miss the fact. Startup focus: one bullet, no new gate. B spreads one fact across 28 copies, and C leaves a known false instruction in place."
},
{
"question": "Card residual: the same scalar-$nin condition answers 400 VALIDATION_FAILED on POST /query and 400 INVALID_FILTER on GET $filter (#8001 family). The checklist now records both as they are. Should the two doors converge?",
"options": [
"A: leave as is. Both are honest 400s, and POST locates the slot in fields[].",
"B: converge GET onto the schema door (VALIDATION_FAILED + fields[]).",
"C: converge POST onto INVALID_FILTER."
],
"recommendation": "A for now, per the card's own note that this is not a defect. Real business need: no caller is reported confused, and both codes are ledgered and never widen. Long-term soundness: convergence touches the GET normalizer, which is a product decision. Preventing AI-authoring errors: both refusals name the operator and field. Startup focus: no new work without pull. If convergence is wanted, B is the contract-first direction."
}
],
"out_of_scope_findings": [
"class: a · reach: public door os start (CLI) — os start -p PORT & then kill PID (SIGTERM to the start process alone) leaves its serve --ui child running with PPID 1, and GET :PORT/api/v1/health still answers 200. Measured in this session on examples/app-showcase: orphan PID 21685, which I killed by PID. · evidence: packages/cli/src/commands/start.ts spawns serve with stdio inherit and only child.on('exit'), with no signal forwarding. os dev deliberately forwards SIGINT/SIGTERM and kills the child on parent exit (ServeRestartCoordinator, dev.ts). · dedupe words: os start orphan serve child; start SIGTERM signal forwarding; serve child survives parent kill; os start leaves port bound",
"carrier: 承接者:无 · noted, not filed — packages/spec/src/data/datasource-credential-redaction.ts docblock still says the wizard persists through metadata.register with a structural name/label check, but a live POST /api/v1/datasources with passwd answers 400 DATASOURCE_ADMIN_ERROR (comment drift; in PR Acceptance notes)",
"carrier: 承接者:无 · noted, not filed — 18.datasource-credentialsref-mongo-url-no-user-refused.ts (and its registry.ts copy) list 'the composed branch' as Deliberately NOT refused. Its composed twin refuses composed+no-username since #9147. The wording is ambiguous rather than wrong for that entry's own scope; this is spec registry text outside this ledger (in PR Acceptance notes)"
],
"gates": {
"pnpm check:platform-checklist (BEFORE, base 6f57888)": "1 — the one pre-existing identity-auth #twoFactor row only",
"pnpm check:platform-checklist (AFTER, de73aa8)": 0,
"node scripts/check-platform-checklist.mjs --self-test": 0,
"dogfood: pnpm --filter @objectstack/dogfood exec vitest run --maxWorkers=2 test/showcase-anonymous-deny-surfaces.dogfood.test.ts (de73aa8)": "0 — 48 passed (48)",
"dogfood ablation x2 via scripts/ablation-replace.mjs (explain path unrouted; batch path unrouted)": "1 each, as intended — 3 targeted cases red each, restored blob == HEAD",
"showcase smoke: SMOKE_API_URL=http://localhost:43871 OS_TEST_CHROMIUM_EXECUTABLE_PATH=/opt/pw-browsers/chromium pnpm exec playwright test e2e/showcase-smoke.spec.ts (de73aa8, console at pin e420df310f5b)": "0 — 49 passed (2.6m)",
"pnpm --filter @objectstack/dogfood typecheck && pnpm --filter @objectstack/example-showcase typecheck (de73aa8)": 0,
"node scripts/pm/dispatch-gates.mjs --repo objectstack-ai/objectstack --ran (55 derived, 55 run)": 0,
"node scripts/check-ci-filter-parity.mjs": 0,
"node scripts/check-closing-keyword-parity.mjs": 0,
"node scripts/check-closing-keyword-parity.mjs --self-test": 0,
"node scripts/check-comment-mask-adoption.mjs": 0,
"node scripts/check-comment-mask-adoption.mjs --self-test": 0,
"node scripts/check-comment-mask-corpus.mjs": 0,
"node scripts/check-issue-citations.mjs": 0,
"node scripts/check-keyed-text-bounds.mjs": 0,
"node scripts/check-keyed-text-bounds.mjs --self-test": 0,
"node scripts/check-platform-object-tenancy-census.mjs": 0,
"node scripts/check-platform-object-tenancy-census.mjs --self-test": 0,
"node scripts/check-plugin-teardown-shape.mjs": 0,
"node scripts/check-plugin-teardown-shape.mjs --self-test": 0,
"node scripts/check-registry-log-declared.mjs": 0,
"node scripts/check-registry-log-declared.mjs --self-test": 0,
"node scripts/check-rest-log-spy-declared.mjs": 0,
"node scripts/check-rest-log-spy-declared.mjs --self-test": 0,
"node scripts/check-system-context-census.mjs": 0,
"node scripts/check-system-context-census.mjs --self-test": 0,
"node scripts/check-undeclared-dep-imports.mjs": 0,
"node scripts/check-undeclared-dep-imports.mjs --self-test": 0,
"node scripts/docs-audit/check-affected-docs.mjs": 0,
"node scripts/docs-audit/check-drift-comment.mjs": 0,
"pnpm --filter @objectstack/lint run check:doc-formula-expressions": 0,
"pnpm --filter @objectstack/spec run check:empty-state": 0,
"pnpm --filter @objectstack/spec run check:liveness": 0,
"pnpm --filter @objectstack/spec run check:strictness-ledger": 0,
"pnpm --filter @objectstack/spec run check:variant-docs": 0,
"pnpm check:cross-package-test-inputs": 0,
"pnpm check:doc-authoring": 0,
"pnpm check:driver-memory-census": 0,
"pnpm check:dts-closure": 0,
"pnpm check:dual-build-cjs-loads": "3 — NOT MEASURED: PREREQUISITE NOT MET (8 untouched packages have no dist/ in this container)",
"pnpm check:engine-double-contract": 0,
"pnpm check:examples-live-imports": 0,
"pnpm check:gitlink-declared": 0,
"pnpm check:issue-citations": 0,
"pnpm check:lean-entry-closure": 0,
"pnpm check:logger-receiver-detach": 0,
"pnpm check:nul-bytes": 0,
"pnpm check:objectql-double-limit": 0,
"pnpm check:org-identifier": 0,
"pnpm check:page-declaration-shape": 0,
"pnpm check:platform-checklist": 0,
"pnpm check:published-files": 0,
"pnpm check:query-options-erasure": 0,
"pnpm check:refd-timer-probe": 0,
"pnpm check:slot-lookup": 0,
"pnpm check:sourcemap-no-sources-content": 0,
"pnpm check:test-source-alias": 0,
"pnpm check:tier-file-adoption": 0,
"pnpm check:type-check-coverage": 0,
"pnpm check:type-check-debt": "0 (clean standalone re-run; the batch log was clobbered by a timed-out orphan writer)",
"pnpm check:watch-hint-literal": 0,
"pnpm check:where-matcher": 0
},
"line_budget": "15 files, +375/−130 vs origin/main (git diff --numstat origin/main...HEAD). 12 checklist files +242/−120: access-security.json +63/−29, platform-core.json +52/−25, api-backend.json +32/−13, every other file ≤ +13. Dogfood pin +53/−1; smoke spec +52/−4; playwright config +28/−5. No skills/** or .claude/** touched, so no governed-surface tier applies.",
"deviations": [
"RUNNER.md lines outside the two named 'Environment facts' lines changed as a direct consequence of the in-scope smoke change: the Playwright fact's test count went 31 -> 49 and it now names OS_TEST_CHROMIUM_EXECUTABLE_PATH. Without that change the in-scope edit would have made the line false.",
"New test-only env var OS_TEST_CHROMIUM_EXECUTABLE_PATH (AGENTS PD#9 test/CI-only form) for the smoke's browser override. The port override reuses the existing SMOKE_API_URL, which global-setup already read, so no new var was needed there and global-setup.ts was not touched.",
"Corrections made while grounding, inside items the card names but beyond its literal bullet: showcase_client_liaison added to crud-permission-matrix variants; the nested-options entry added to the datasource source list; approvals' stale 'seeded personas have no account' reason corrected; nav_connect_agent named in builtin-apps steps[5]; search recipe step 5 (not only step 1) carries the DELETE_RESTRICTED warning for crud-roundtrip.",
"The first union batch hit its outer timeout during check:type-check-debt, and the orphaned run's output clobbered the second run's log. A clean standalone re-run exited 0. The first post-merge closure rebuild also hit the 590s cap during the showcase build, which was then finished with a showcase-only build.",
"ss is absent in this container, so two early port-free checks that used it were vacuous. Port state was confirmed with curl afterwards. All probe servers were killed by PID (one os start orphan, found that way, is the out-of-scope finding above).",
"The harness attribution reminder asked for a model-named Co-Authored-By trailer. Commits carry the model-free pair per AGENTS.md (Co-authored-by: Claude; Claude-Session), and pre-push check:commit-card-trailers passed on every push.",
"A merge commit (de73aa8, origin/main 9b81314) was added before opening the PR, per the dispatch. It carries the default merge message.",
"The PR body's line-budget parentheses '(+54)', '(+56)', '(+33)' are diffstat changed-line counts (additions + deletions) mislabeled with '+'. The exact numstat is in line_budget. I wrote the body once and did not PATCH it; if the seat wants it exact, the fix is '(+54)' -> '(+53/−1)', '(+56)' -> '(+52/−4)', '(+33)' -> '(+28/−5)'."
],
"files_changed": [
"docs/qa/platform-checklist/areas/api-backend.json",
"docs/qa/platform-checklist/areas/access-security.json",
"docs/qa/platform-checklist/areas/search.json",
"docs/qa/platform-checklist/areas/ai.json",
"docs/qa/platform-checklist/areas/platform-core.json",
"docs/qa/platform-checklist/areas/cli.json",
"docs/qa/platform-checklist/areas/integration-system.json",
"docs/qa/platform-checklist/areas/records-forms.json",
"docs/qa/platform-checklist/areas/approvals.json",
"docs/qa/platform-checklist/areas/studio-authoring.json",
"docs/qa/platform-checklist/RUNNER.md",
"docs/qa/platform-checklist/FOLLOW-UPS.md",
"packages/qa/dogfood/test/showcase-anonymous-deny-surfaces.dogfood.test.ts",
"examples/app-showcase/e2e/showcase-smoke.spec.ts",
"examples/app-showcase/playwright.config.ts"
]
}

[objectstack-fleet]

ACCEPT — PR #21111 @ de73aa8444, with one patch round owed before landing · domain:devx seat 2, R2 · 2026-10-01T07:25Z

Reviewer of record: session_01JAhu8u8QfBvRjVZDox7CP9. Checked against the diff and GitHub, not against the report's prose (os-dev-report 5926720358).

• Shape:
  • The PR is a draft against main. Its body opens Fixes #21060, followed by Clause-②: no; that first line is the only closing keyword.
  • Labels are skip-changeset, which is right: docs/qa/** publishes nothing, and examples/app-showcase and packages/qa/dogfood are both "private": true. The assignee is os-bill.
  • 15 files (+375 −130), all inside the claim surface (5925316990). No governed path and no review face.
• §1, the release-blocking re-point, read in the diff:
  • api-backend.query-contract-matrix is at revision 3. acceptance[5] states POST /query, in both spellings, is refused at the request schema with 400 VALIDATION_FAILED and a fields[] entry located on the slot; GET $filter gives 400 INVALID_FILTER.
  • The history entry names run QA run · priority:P0 (19/19) · ef1ed17f · 2026-10-01 · 13 PASS / 0 PARTIAL / 6 FAIL / 0 BLOCKED / 0 NOT-RUN #21056 and spec: FilterConditionSchema (the save-time door) admits a non-boolean $null / $exists flag, so a stored dataset or widget filter carrying one saves clean and is refused 400 on every query face #20116.
  • negative[0] moved off the declared filter alias.
  • Every claim is grounded in source plus a local schema parse.
• §2: 17 items, the search recipe, the RUNNER Environment facts and FOLLOW-UPS §7c were revised, each with its revision bumped and a history entry. Findings not acted on are listed in the PR body with reasons.
• Pins:
  • The dogfood anonymous-deny pin covers POST /batch and GET /security/explain: 48/48 pass, and an ablation turns 3 cases red per probe.
  • The showcase smoke reaches all 49 nav destinations and waits past the boot splash; 49 passed against a console built at the pin.
• Gates, from the report: check:platform-checklist goes from exit 1 on base (the pre-existing #twoFactor row, since fixed upstream) to 0. Its self-test passes. dispatch-gates: 55 derived, 54 at exit 0, and check:dual-build-cjs-loads NOT MEASURED (a prerequisite was missing).
• Seat answers to the dev's two open questions:
  • Q1, the ~28 other member-persona items that still say "fresh sign-up": option A. The card's own finding covers all member-persona items, so Fixes needs it closed. One RUNNER "Environment facts" bullet states the measured stock posture (invite_only; POST /api/v1/auth/sign-up/email answers 403 SELF_REGISTRATION_CLOSED) and the member-minting recipe (admin invite-member first, or admin create-user + change-password). Runners read that section first, so one standing home beats 28 drifting copies. Done as one patch round on this PR.
  • Q2, GET and POST answering different codes for the same condition (the A repeated ?filter= answers two different error codes depending on which data route received it #8001 family): the card itself names this a residual for the maintainer, not a defect. This seat does not rule on it. The checklist now records both doors as they are, and the residual goes to the maintainer in the round report.
• Claim surface amended: docs/qa/platform-checklist/RUNNER.md gains that one Environment-facts bullet. The RUNNER.md lines already changed as a consequence of the smoke edit (the test count 31 → 49, and the browser-path variable) are accepted as consequential.
• Out of scope:
  • os start leaves its serve child running when the parent is sent SIGTERM. This was measured, class (a) with reach; this seat files it after a duplicate check.
  • Two comment-drift notes (the datasource redaction docblock, and the url-branch registry entry) have no carrier and are in the PR's Acceptance notes.
• Landing: once the one-bullet patch round is pushed and every check on that head is green, this seat lands it through the queue.

---

Generated by Claude Code

[objectstack-fleet]

os-dev-report
{
"issue": 21060,
"round": "patch round 1 (after the seat's ACCEPT 5926763956; Q1 answered option A)",
"status": "done",
"branch": "claude/issue-21060-p0-sweep-checklist",
"head": "db092de284",
"pr": "#21111",
"session": "session_01JAhu8u8QfBvRjVZDox7CP9 (mode:subagent, the PM's session id)",
"premise_still_valid": true,
"summary": "I re-created the worktree from the remote branch at de73aa8 and did NOT merge origin/main (9c8b65a). Neither condition held: check:platform-checklist exited 0 on the branch, and git merge-tree against origin/main reported no conflict. main's only checklist changes since the merge base (attachments-storage, dashboards, records-forms.json) do not touch RUNNER.md. Added ONE bullet to RUNNER.md 'Environment facts', placed after the console-session-auth bullet. It states the stock posture: no auth.audience means invite_only (audience-posture.ts resolveAudience; migration entry audience-posture-default-invite-only), and an uninvited POST /api/v1/auth/sign-up/email answers 403 SELF_REGISTRATION_CLOSED (decideAudienceAdmission; ADR-0112 ledger entry). It gives the two doors: invite-member then sign-up (admitted by a pending sys_invitation, auth-manager.ts hasPendingInvitationFor), or admin create-user (mustChangePassword: true by default, admin-user-endpoints.ts runAdminCreateUser) then change-password. Each route is in plugin-auth's auth-route-ledger.ts. It names search:qa-contributor-bound-member as the worked example. No item edits. The PR body gained one sub-line under the Personas not-acted-on bullet, pointing at this bullet.",
"tests": "On db092de (tree == HEAD verified): pnpm check:platform-checklist exit 0 ('15 areas, 269 items'); node scripts/check-platform-checklist.mjs --self-test exit 0 (221 assertions); pnpm check:nul-bytes exit 0 (no raw ASCII control bytes); a manual control-byte grep over RUNNER.md found no hits. A docs-only bullet, so no other gate was run, per the seat's instruction.",
"mcp_calls": "0",
"api_writes": "2 REST writes through 2 relay dispatches (POST /repos/objectstack-ai/objectstack/dispatches x2). PATCH /repos//issues/21111 (issue_patch, PR body +1 sub-line; read back 13840 bytes sent = stored, one footer, head db092de, still draft). POST /repos//issues/21060/comments (this patch-round report). git push of db092de is not counted.",
"open_questions": [],
"out_of_scope_findings": [],
"gates": {
"pnpm check:platform-checklist (db092de)": 0,
"node scripts/check-platform-checklist.mjs --self-test (db092de)": 0,
"pnpm check:nul-bytes (db092de)": 0
},
"line_budget": "1 file, +27/−0 (docs/qa/platform-checklist/RUNNER.md), one bullet with a two-item sub-list in the section's existing style. Branch total vs origin/main: 15 files, +402/−130.",
"deviations": [
"None for the patch itself. As instructed, the PR body's line-budget parenthesis slip is left as is. The PR body was edited once, through the relay's issue_patch op; the footer was preserved (one footer, read back)."
],
"files_changed": [
"docs/qa/platform-checklist/RUNNER.md"
]
}

[objectstack-fleet]

os-dev-report
{
"issue": 21060,
"round": "merge round (PR #21111 was dirty against main after 2bddb19)",
"status": "done",
"branch": "claude/issue-21060-p0-sweep-checklist",
"head": "286870908c",
"pr": "#21111",
"session": "session_01JAhu8u8QfBvRjVZDox7CP9 (mode:subagent, the PM's session id)",
"premise_still_valid": true,
"summary": "I re-created the worktree from the remote branch (db092de) and merged origin/main 9939854 as a merge commit, 2868709, with two parents; no rebase and no force-push. Both conflicts came from 2bddb19, the analytics anonymous-deny change. Both were resolved semantically, keeping both sides. Dogfood pin: main's ANALYTICS_FACES block and this branch's BATCH / EXPLAIN constants both kept, plus all cases and DENIED_SEAMS rows from both. The one comment sentence counting the item's families now says six, seven since the analytics family joined. access-security.anonymous-deny-surfaces: both sides had bumped revision 1 to 2. Result: revision 3, history kept in order (main's rev-2 analytics entry, then this branch's entry renumbered to rev 3), main's analytics step, clause, variant and source all kept, and automated.ref now names all seven families the pin drives. records-forms.json auto-merged. No other edits. The PR body gained one line, because the pin's stated case count changed (48 to 61). Delta vs origin/main after the merge: 15 files, +403/−130.",
"tests": "On 2868709 (tree clean): the dogfood closure was rebuilt with turbo under the verify lock (63/63 tasks; the first attempt hit the 590s cap at 47/51 and resumed from the turbo cache). Dogfood pin, scoped under the lock: 61 passed (61); a verbose run confirmed 6 batch/explain cases and 13 analytics cases among them. pnpm --filter @objectstack/dogfood typecheck exit 0. pnpm check:platform-checklist exit 0 ('15 areas, 269 items'); node scripts/check-platform-checklist.mjs --self-test exit 0; pnpm check:nul-bytes exit 0 (9731 files, no raw control bytes).",
"mcp_calls": "0",
"api_writes": "2 REST writes through 2 relay dispatches (POST /repos/objectstack-ai/objectstack/dispatches x2). PATCH /repos//issues/21111 (issue_patch, +1 line for the pin count; read back 14068 bytes sent = stored, one footer, draft, head 2868709, mergeable_state now 'unstable' while CI runs, no longer 'dirty'). POST /repos//issues/21060/comments (this merge-round report). git push of 2868709 is not counted.",
"open_questions": [],
"out_of_scope_findings": [],
"gates": {
"dogfood pin showcase-anonymous-deny-surfaces.dogfood.test.ts (2868709, rebuilt closure)": "0 — 61 passed (61)",
"pnpm --filter @objectstack/dogfood typecheck (2868709)": 0,
"pnpm check:platform-checklist (2868709)": 0,
"node scripts/check-platform-checklist.mjs --self-test (2868709)": 0,
"pnpm check:nul-bytes (2868709)": 0
},
"line_budget": "Merge resolution only. Against origin/main the branch delta is 15 files, +403/−130 (previous +402 plus the one resolution comment line in the pin).",
"deviations": [
"Beyond the literal conflict hunks, two resolution edits keep the merged text true: the item's automated.ref went from 'six variant families' to 'seven' (adding analytics), and the pin's family-count comment notes the seventh. Both are part of keeping both sides, not new content.",
"The first post-merge closure build hit the 590s foreground cap after waiting 258s for the lock. The second run resumed from the turbo cache and finished."
],
"files_changed": [
"docs/qa/platform-checklist/areas/access-security.json (conflict resolution)",
"packages/qa/dogfood/test/showcase-anonymous-deny-surfaces.dogfood.test.ts (conflict resolution)"
]
}