QA run · north-star path published 17.6.0 (11/13) · 617f25f8 · 2026-10-02 · 2 PASS / 8 PARTIAL / 1 FAIL / 0 BLOCKED / 2 NOT-RUN #21318

Environment fingerprint

Scope

Selector: the path in docs/NORTH-STAR.md (「唯一的度量,那条路」), walked end to end as a new developer reading only the published docs (content/docs/**) and CLI output, against the published 17.6.0 train. The items scored are the 「路上的功能点」 checklist items each step exercised, at these revisions:

cli.scaffold-first-run r2 · cli.scaffold-console-first-paint r2 · cli.build-own-contract r3 · cli.dev-boot-contract r3 · platform-core.console-login r4 · cli.lint-severity-exit-contract r1 · cli.verify-verdict-exit-mapping r1 · platform-core.marketplace-install-local-lifecycle r1 · ai.mcp-http-surface r2 · ai.mcp-run-action-exposure-gate r2 · identity-auth.api-key-ui-lifecycle r1 · studio-authoring.first-run-loop r3 · cli.dev-automigrate-policy r1

Planned items: none in this selection.

The app built for the walk (tasks-app, namespace tasks_app): a shared picklist tasks_app_work_status used by two objects; objects tasks_app_project and tasks_app_task (text, lookup → project, picklist select, date, number, boolean, textarea); a list view + a two-section form view; a script action complete_task with an inline body, visible: 'record.done != true', ai.exposed: true; an active record_change flow task_completed_note (task after-update, record.status == 'done' → create_record on the starter note object); a permission set tasks_app_task_user (CRUD + readScope: 'org', no delete on project); an app tasks_app with three nav entries.

The path — per-step verdicts

Per-clause verdicts

Derived item verdicts

Hand-off (not reached this run): studio-authoring.first-run-loop (all clauses), cli.dev-automigrate-policy (all clauses), and the not-run clauses listed above.

Reproduction rule for the fail

ai.mcp-run-action-exposure-gate clause 2, on an installed package (no authentication or authorization element; full recipe published):

1. npm create objectstack@17.6.0 tasks-app; add a script action with an inline body and ai: { exposed: true, description } on an app object (any body that updates the record — the docs' Path A example shape); npx os build.
2. In a second directory boot an empty runtime: OS_CLOUD_URL=off npx os start -p 4340 --home ./home --auth-secret <32+ chars>; POST /api/v1/auth/sign-up/email (header Origin: http://localhost:4340) for the first owner.
3. npx os package install ./dist/objectstack.json --runtime http://localhost:4340 --email … --password … → ✓ Package installed into the running kernel.
4. POST /api/v1/data/tasks_app_task {"name":"probe"} → 201.
5. POST /api/v1/actions/tasks_app_task/complete_task {"recordId":"<id>"} → expected 200 {success:true, data:{ok:true}}; actual 404 {"code":"RESOURCE_NOT_FOUND","message":"Action 'complete_task' on object 'tasks_app_task' not found"}.
6. Mint POST /api/v1/keys; MCP list_actions → lists complete_task; MCP run_action {actionName:'complete_task', recordId} → actual isError: true, No handler registered for action 'complete_task' on 'tasks_app_task'.
7. Restart the runtime: same result (reproduced on :4320 after restart and on :4340 hot, i.e. twice on fresh loads).
8. Control: npx os start -p 4350 --artifact <path>/dist/objectstack.json … → step 5 answers {"success":true,"data":{"ok":true,…}} and the record reads status: done.

Verify pass (RUNNER rule 7): a second, independent agent re-derived this verdict on fresh runtimes (:4461 install-local, :4462 artifact-pinned) from the steps above alone — CONFIRMED: REST 404 RESOURCE_NOT_FOUND and MCP No handler registered … on the installed runtime while list_actions lists the action; REST 200 and MCP {ok:true} on the artifact-pinned one.

Findings outside the scored clauses (each extracted to its own card)

1. Install-local drops the app's script action bodies — the fail above (P0 of the path).
2. Hot install leaves record-change flows unbound and permission sets unprojected until a restart — on :4340 a task updated to done right after install wrote no note (flow did not fire); after a restart (:4320) the same update writes it. sys_permission_set lists tasks_app_task_user only after a restart (/meta/permission already lists it), so an admin cannot grant the installed app's set until then. The CLI says nothing about a restart.
3. objectstack verify passes a stack the authoring gates refuse — with a dangling lookup target, a bare-reference visible predicate and an unknown list column planted (validate/build/lint all exit 1), objectstack verify prints 3 verified … ✓ verify passed — no runtime failures, exit 0. NORTH-STAR defines done as "objectstack verify is green"; the published docs (content/docs/deployment/cli.mdx) do not document verify at all.
4. objectstack verify --json stdout is not a JSON document — ~329 lines of INFO kernel log precede the payload on stdout, so verify --json > report.json (the item's own step 0) yields an unparseable file.
5. os generate scaffolds fail the project's own gates — os g flow task_done writes a start node on tasks_app_task_done (an object that does not exist) and reports ✓ Reaches the stack; validate only warns. os g view task writes a view that os lint refuses (View "tasks_app_task" is missing a label at views[0].list.label, exit 1) and whose name/label validate calls dead properties. os g action complete_task / os g app tasks derive the object from the NAME and refuse; there is no flag to target an existing object.

Observations recorded, not extracted: the Console requests GET /api/v1/usage/storage on every page and gets 404 ENDPOINT_NOT_FOUND on a community runtime; a plain member's Console requests GET /data/sys_activity and gets 403 on home; the create form does not pre-select the picklist's default: true option (the server applies it on insert); your-first-project.mdx says the default template "runs on an in-memory driver" while os dev resolves a persistent SQLite file (the same page says so two sections later); runtime/config reports aiStudio: true on a community os start boot (not followed up).

Fixture gaps: none.

Generated by Claude Code