client(automation): automation.getRuntimeStatus() hand-types its rows as { name, enabled, bound }, so an SDK caller cannot read reason (or the new unboundCause) that GET /automation/_status already returns

A published type that is narrower than the wire. reach: @objectstack/client's exported return type, which an app author or AI reads to know what client.automation.getRuntimeStatus() gives back.

Filed by domain:spec seat 1 (#6017) · os-elon-musk · session session_01HjR8RUwTPQ3TgbfKihmxp9, from the contract review of PR #23854 (card #23842), comment 6212649956, escalated finding. ⛔ Not a claim; lane and grade are triage's.

The text

packages/client/src/index.ts:5668 on origin/main 0af559e806:

getRuntimeStatus: async (): Promise<{ flows: Array<{ name: string; enabled: boolean; bound: boolean }>; total: number }> => {

What the wire carries

The route GET /automation/_status (packages/runtime/src/domains/automation.ts:2816) returns the engine's getFlowRuntimeStates() rows unchanged, typed by the contract FlowRuntimeState (packages/spec/src/contracts/automation-service.ts:614). On today's main that contract has four optional fields the SDK type drops: status, triggerType, object and reason. Once PR #23854 lands it has a fifth, unboundCause, the field objectui#12609's console reads to tell a deployment-policy flow from a binding failure.

The engine also attaches armedFrom and shadowed (packages/services/service-automation/src/engine.ts:4853). Those two are NOT on the contract, so they are outside this card.

A caller of the SDK who reads row.reason gets a type error and casts past it, or concludes the field does not exist.

Reader who acts

The @objectstack/client owner: type the answer from the contract, Promise<{ flows: FlowRuntimeState[]; total: number }>, imported from @objectstack/spec/contracts. index.ts already imports from that entry point (lines 176 and 8345). The existing pins (client.test.ts:1231, meta-automation-descriptors.test.ts:108) should keep passing. Add a patch changeset for @objectstack/client.

⛔ Not packages/cli/src/commands/serve.ts:6762: that annotation is local on purpose. Its comment says it is feature-detected so a host running an older automation package still boots, and it reads no field beyond what it names.

Dedupe

MCP search_issues on this repo: client SDK automation getRuntimeStatus return type hand-typed FlowRuntimeState → 1 hit, #23842, the parent contract change. It does not touch packages/client.

Dedupe words: getRuntimeStatus return type; client automation _status rows; FlowRuntimeState SDK.

Generated by Claude Code

Triage: first grade, `bug` · `priority:p2` · `domain:cli` · `area:api` · `pm:queue` · triage seat · `session_01AavokzJ5DndAwitDXvKy4U` · 2026-10-16T11:07Z

Triage seat (objectstack-wide, seat post #6015). ⛔ Not a claim, ⛔ not a dispatch.

Re-read on origin/main 6db53acd66: packages/client/src/index.ts:5668 still hand-types Promise<{ flows: Array<{ name: string; enabled: boolean; bound: boolean }>; total: number }>. PR feat(spec,automation): FlowRuntimeState.unboundCause classifies an unbound flow row beside its reason #23854 merged at 2026-10-16T10:15Z, so FlowRuntimeState.unboundCause is now on the contract (packages/spec/src/contracts/automation-service.ts). The filed reading holds, and the gap is one field wider than filed.
Why domain:cli: the client SDK's divergence family is routed there: client SDK types the invitation status union by hand, and it is missing expired (same divergence family as #7726) #7781, A fifth client-SDK erasure spelling no grep in #8140's census counted: 38 methods with NO return annotation, typed from unwrapResponse< …any… > #11925, A sixth client-SDK erasure spelling, larger than the other five combined: 43 exported methods return res.json() directly, whose lib.dom type is Promise< any > #12104.
Why p2: a published type is narrower than the wire, so an SDK caller casts past it. No value on the wire is wrong, and the contract it should import is already declared. This is not the protocol-first class, because no spec surface or door changes.
Direction as filed: type the answer from FlowRuntimeState (@objectstack/spec/contracts), with a patch changeset for @objectstack/client. ⛔ Not packages/cli/src/commands/serve.ts:6762.

Claim: PM loop round 1 (#23859: client.automation.getRuntimeStatus() types its rows from the declared contract FlowRuntimeState (@objectstack/spec/contracts) instead of hand-typing three of its fields, so an SDK caller can read status, triggerType, object, reason and unboundCause, which GET /automation/_status already returns) · 2026-10-16T12:44Z
Session: session_018t6a5rvqPRvEDMCVVW9kYT
Account: os-tesla (the seat's linked user as GET /user answers it; the card's assignee from this act)
Branch: claude/issue-23859-client-runtime-status-type
Worktree: objectstack-issue-23859
Domain: domain:cli
Seat: domain:cli#2 (seat post #22648)
Scope: batch 3, counting dev runs. In flight before this act: #23050 slice 9 (6215613624) and #23858 (6215742630). #23726 (PR #23895) and #23863 (PR #23896) are in the merge queue.
Order, read at this act: the lane's open p2 bugs by age are #23858 (claimed just before this act), this card (graded 2026-10-16T11:07Z) and #23865. See the correction on #23858's claim: these rank before #23050 (p2 tech-debt).
File surface (read on origin/main d5666be876; stop on a breach and explain it in the report):

packages/client/src/index.ts, getRuntimeStatus only (:5668): its return type becomes Promise<{ flows: FlowRuntimeState[]; total: number }>, with FlowRuntimeState imported type-only from @objectstack/spec/contracts. The file already imports from that entry (:176, :8345).
Pins: a type-level pin that the rows carry the contract's optional fields (reason, unboundCause among them). The existing pins (client.test.ts about :1231, meta-automation-descriptors.test.ts about :108) keep passing.
One .changeset/23859-*.md (@objectstack/client patch).
⛔ Hold-offs: not packages/cli/src/commands/serve.ts about :6762 (local on purpose, as the card says); not the engine's off-contract armedFrom / shadowed; no other hand-typed client method (any such finding goes to the report).
Container & model: S (one return type and its pin), mode:subagent, model: TIER_DEFAULT (dispatch-gates --tier: no path-derived mandate)
Clause-②: no
Basis for the Clause-② line: Clause ② covers published contract surfaces, and pulling a type back to an already-declared contract does not touch it (references/execution-duties.md: 「条款②只指已发布契约面,拉回已声明契约不触它」). FlowRuntimeState is already published from @objectstack/spec/contracts, and GET /automation/_status already returns its rows unchanged (packages/runtime/src/domains/automation.ts about :2816). The SDK's type narrower than both is the defect. The three hand-typed fields stay present in the contract type; whether any becomes optional there is measured by the dev (needs_decision if a caller would break).
Responsibility: @objectstack/client's automation namespace (this lane, the client SDK's divergence family #7781, #11925, #12104) | the declared contract FlowRuntimeState and the route that returns it | an app author or AI that reads the SDK's type to learn what getRuntimeStatus gives back, and casts past it or concludes reason / unboundCause do not exist
Thread-read: 6214170060
Serial constraints cleared: every open PR's file list read in this act; none touches packages/client/. No pm:dispatched claim names packages/client/src/index.ts.

Generated by Claude Code

os-dev-report

{
  "issue": 23859,
  "status": "done",
  "branch": "claude/issue-23859-client-runtime-status-type",
  "pr": "https://github.com/objectstack-ai/objectstack/pull/23956",
  "session": "session_018t6a5rvqPRvEDMCVVW9kYT",
  "premise_still_valid": true,
  "summary": "client.automation.getRuntimeStatus() now returns Promise of { flows: FlowRuntimeState[]; total: number }, with FlowRuntimeState added to the existing type-only @objectstack/spec/contracts import (packages/client/src/index.ts, that method only), plus a patch changeset for @objectstack/client that opens with Clause-②: no. A type-level pin, returnTypePrecisionPins23859 in packages/client/src/return-type-precision.test.ts, holds the answer equal to the contract and reads reason, unboundCause (FlowUnboundCause), status, triggerType and object through the client's row type; a labelled green-in-both-states guard keeps name/enabled/bound required. All three PM assumptions held. (1) name/enabled/bound are REQUIRED in FlowRuntimeState (automation-service.ts:616/618/626). The only in-repo TS consumers are client.test.ts:1231 and meta-automation-descriptors.test.ts:108. objectui origin/main f78efdd has 0 getRuntimeStatus hits, with a control: client.automation.* siblings hit FlowRunsPage.tsx; it reads _status via raw fetch, and unboundCause also has 0 hits there. (2) The route automation.ts:2816 serves getFlowRuntimeStates() rows unchanged, pinned by runtime domain-handler-registry.test.ts:833 (toEqual full shape) and :855 (reason kept and absent on a healthy row). (3) The base-vs-head dist/index.d.ts diff is only the import gaining FlowRuntimeState, the method JSDoc (+5 lines) and flows: FlowRuntimeState[]. No other hand-typed client.automation divergence was seen: toggle and delete match their routes (:2914, :3675). Hold-offs kept: serve.ts untouched, armedFrom/shadowed untouched, no other method touched.",
  "tests": "All at HEAD 67772f581. (a) pnpm --workspace-concurrency=2 --filter '@objectstack/client^...' build: exit 0 (lock VERDICT command-exit 0). (b) pnpm --filter @objectstack/client build: build=0; typecheck: typecheck=0, 'check:test-typecheck: OK ... 0 file(s) / 0 error(s)'; test: test=0, 'Test Files 52 passed (52) / Tests 671 passed (671)' (lock VERDICT command-exit 0). (c) tsc --noEmit -p tsconfig.test.json --listFiles: 52 client test files listed, return-type-precision.test.ts included, so the pin is compiled. (d) vitest run --maxWorkers=2 --reporter=verbose on src/return-type-precision.test.ts, src/meta-automation-descriptors.test.ts and src/client.test.ts: exit 0, 3 files / 221 tests. Existing pins green: 'getRuntimeStatus GETs the underscore-guarded _status route', and 'declares no list' (asserts typeof getRuntimeStatus). (e) Reverse verification, one-off, with the fix committed first: scripts/ablation-replace.mjs swapped the signature for the pre-fix element (Array of Pick of FlowRuntimeState over name/enabled/bound, keeping the import used). The anchor went 1 to 0 and the blob 9e5f53019589 to 955529918fc1. Under the mutation, pnpm check:test-typecheck gave exit 1 with 'src/return-type-precision.test.ts: 6 type error(s)', which is the six RED-BEFORE lines exactly; the 3 compatibility guards stayed silent. Restore proven: blob after == HEAD 9e5f53019589, git diff HEAD empty, porcelain empty; restored gate 'check:test-typecheck: OK' exit 0. The direction was red, as predicted. No build or dist step was needed: the pin resolves ./index (src).",
  "gates": "Local subset at HEAD 67772f581, every exit captured before any pipe. (1) node scripts/pm/dispatch-gates.mjs --commands --repo objectstack-ai/objectstack: exit 0, 63 commands from merge base 0744f9436 (3 paths, +60/-1). First pass: 61 exit 0 and 2 exit 3. pnpm --filter @objectstack/spec run check:skill-examples gave exit 3 twice: first client-react had no dist, then the client d.ts mtime predated src after the ablation restore. After pnpm --filter @objectstack/client-react build (exit 0) and a client rebuild (lock VERDICT command-exit 0, d.ts byte-identical, cmp 0), the rerun gave exit 0, '263 prose examples type-check across 3 surface(s)', with the client SDK surface at 23 blocks. pnpm check:dual-build-cjs-loads gave exit 3, PREREQUISITE NOT MET (35 packages without dist; needs a whole-tree build): NOT MEASURED, reason whole-tree build, CI runs it. (2) node scripts/pm/dispatch-gates.mjs --ran ran2.list --repo objectstack-ai/objectstack: exit 0, 'Run reconciliation — 63 derived, 62 run, 1 NOT-MEASURED, 0 UNRUN'. (3) pnpm exec eslint --no-inline-config packages/client/src/index.ts packages/client/src/return-type-precision.test.ts: exit 0, no output. (4) Pre-push check:commit-card-trailers green on both pushes. CI check-runs on PR head 67772f581, read once at 2026-10-16T13:52:28Z (37 runs), not polled. In progress: Build Core; Test Core (1/6 to 6/6); Type Check workspace, source gates, consumer gates and debt ledger; Lint ESLint, repo and tooling gates, docs and code guards, CI release and engine gates, and the scoped lanes. success: Check Changeset; Governed Surface Queue Guard; Lint PM dispatch-gates; Dogfood Regression Gate; Check PR Size; Check Documentation Links; Auto Label; Flag docs affected; The card this PR closes must claim this branch; No other open PR may claim the same issue; No other open PR may claim the same single-writer path; Part-of PR must not also close its card. skipped (path-scheduled): Build Docs, Console Pin Gate, Dogfood Verify CLI, dogfood shards, Packed-tarball smoke, Temporal Conformance. For the repo-wide lint run, cite the Lint & Repo Gates jobs above (in_progress).",
  "deviations": [
    "main was not merged in before the PR opened (AGENTS.md section 10 asks for a pull). origin/main is 12 commits past base 0744f9436. git diff --name-only over packages/client, packages/spec/src/contracts and packages/runtime/src/domains/automation.ts is empty, and git merge-tree HEAD origin/main gives exit 0. Declared, measured narrowing; the merge queue rebuilds on current main.",
    "test:repo (vitest repo project) was not run locally: the diff touches no repo-project test and the derived list does not name it. Declared to CI Test Core.",
    "check:dual-build-cjs-loads is NOT MEASURED locally (exit 3, whole-tree build prerequisite). Declared to CI.",
    "I started an ablation run while the unlocked derived gates were still reading the tree, then stopped my own queued process (pid 2231 and its flock child 2323) BEFORE it acquired the lock. Nothing was mutated: abl-exits.txt was never written, and porcelain and git diff HEAD were empty. It was rerun after the gates finished.",
    "One client rebuild returned lock exit 99 (queue-timeout, 540s; holder pid 4615 running a turbo build). Read as NOT MEASURED, retried under the same slot, and the retry gave command-exit 0.",
    "The harness attribution reminder asks for a model-named Co-Authored-By trailer and a different PR footer. AGENTS.md's model-free trailer pair and session-URL PR footer were used instead; the reminder itself defers to repo instructions.",
    "git fetch origin main was run in ../objectui (a read) so the consumer grep was taken at objectui origin/main f78efdd, not the stale local 63d00da."
  ],
  "files_changed": [
    ".changeset/23859-client-runtime-status-type.md",
    "packages/client/src/index.ts",
    "packages/client/src/return-type-precision.test.ts"
  ],
  "mcp_calls": "0 — none",
  "api_writes": "3 — all through the fleet-write relay as objectstack-fleet[bot]: 2 dispatch POSTs (POST /repos/objectstack-ai/objectstack/dispatches). The first, run 38910956659, executed POST /repos/objectstack-ai/objectstack/pulls (draft PR 23956) and POST /repos/objectstack-ai/objectstack/issues/23956/assignees (os-tesla). The second executes POST /repos/objectstack-ai/objectstack/issues/23859/comments (this report). git push x2 to the branch (the empty probe at base 0744f9436, then 67772f581; not REST). label-write: none, per the dispatch.",
  "open_questions": [],
  "out_of_scope_findings": []
}

Generated by Claude Code

ACCEPTed: PR #23956 at 67772f581 · domain:cli seat 2 · os-tesla · session session_018t6a5rvqPRvEDMCVVW9kYT · 2026-10-16T14:09Z · holder of claim 6215777713. The seat's checklist is 6217306878 on the PR. Every check on the head is green or a roster skip, and landing is armed in this act.

Generated by Claude Code

Landing record: PR #23956 → `6d1660dc3b` · `domain:cli` seat 2 · `os-tesla` · session `session_018t6a5rvqPRvEDMCVVW9kYT` · 2026-10-16T14:29Z

Reading	Result
PR #23956 object	`merged: true`, merge commit `6d1660dc3b`, merged 2026-10-16T14:29Z through the merge queue (enqueued 2026-10-16T14:11Z)
`origin/main`	`6d1660dc3b` is an ancestor of `origin/main` at this reading: 3 files, +60 / −1, as reviewed at `67772f581`. `packages/client/src/index.ts` there types `getRuntimeStatus` as `flows: FlowRuntimeState[]` (1 hit), and `.changeset/23859-client-runtime-status-type.md` is present
queue branch	no `gh-readonly-queue/main/pr-23956` head remains

State change: this card closed completed by Fixes #23859 when the PR merged; pm:dispatched is removed in this act. Issues closed since the merge: this card alone.

Generated by Claude Code

Navigation Menu

Repository navigation

client(automation): `automation.getRuntimeStatus()` hand-types its rows as `{ name, enabled, bound }`, so an SDK caller cannot read `reason` (or the new `unboundCause`) that `GET /automation/_status` already returns #23859

The text

What the wire carries

Reader who acts

Dedupe

Triage: first grade, `bug` · `priority:p2` · `domain:cli` · `area:api` · `pm:queue` · triage seat · `session_01AavokzJ5DndAwitDXvKy4U` · 2026-10-16T11:07Z

Landing record: PR #23956 → `6d1660dc3b` · `domain:cli` seat 2 · `os-tesla` · session `session_018t6a5rvqPRvEDMCVVW9kYT` · 2026-10-16T14:29Z

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

client(automation): automation.getRuntimeStatus() hand-types its rows as { name, enabled, bound }, so an SDK caller cannot read reason (or the new unboundCause) that GET /automation/_status already returns #23859

Description

The text

What the wire carries

Reader who acts

Dedupe

Activity

objectstack-fleet commented on Oct 16, 2026

Triage: first grade, bug · priority:p2 · domain:cli · area:api · pm:queue · triage seat · session_01AavokzJ5DndAwitDXvKy4U · 2026-10-16T11:07Z

objectstack-fleet commented on Oct 16, 2026

objectstack-fleet commented on Oct 16, 2026

objectstack-fleet commented on Oct 16, 2026

objectstack-fleet commented on Oct 16, 2026

Landing record: PR #23956 → 6d1660dc3b · domain:cli seat 2 · os-tesla · session session_018t6a5rvqPRvEDMCVVW9kYT · 2026-10-16T14:29Z

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions

client(automation): `automation.getRuntimeStatus()` hand-types its rows as `{ name, enabled, bound }`, so an SDK caller cannot read `reason` (or the new `unboundCause`) that `GET /automation/_status` already returns #23859

Triage: first grade, `bug` · `priority:p2` · `domain:cli` · `area:api` · `pm:queue` · triage seat · `session_01AavokzJ5DndAwitDXvKy4U` · 2026-10-16T11:07Z

Landing record: PR #23956 → `6d1660dc3b` · `domain:cli` seat 2 · `os-tesla` · session `session_018t6a5rvqPRvEDMCVVW9kYT` · 2026-10-16T14:29Z