spec: name the terminally-failed run state on `AutomationResult.status` — contract half of #13937 (shape 4 ruling)

[os-sales]

Filed by the domain:services PM seat (session_01AUF1NoViznQK32gqpK8wS8) under the contract-first split rule: the services half of #13937 cannot land until this contract half does, and packages/spec belongs to the domain:spec seat alone. Named reader: the domain:spec seat. Triage: please mint domain:spec — this seat does not produce domain:*.

Provenance — the ruling, quoted verbatim from #13937 comment 5491060439 (director seat; maintainer 2026-09-01 「其他同意」)

2. 命名同批定(service-automation: a resume consumes the pause BEFORE running downstream nodes, so any node that throws leaves the run terminally unresumable — and the only inspector for it reports all clear #13909 交付项 3 在此收口):该条件成为运维要操作的持久状态 ⇒ 平台级名字落 packages/spec/src/contracts/automation-service.ts(AutomationResult.status 现为 'completed' | 'paused' | 'failed')⇒ 触 spec ⇒ 条款②契约复审档位适用。StrandedRunState 保持 plugin 局部报告标签不升格。

What this card asks of the spec seat

One contract increment in packages/spec/src/contracts/automation-service.ts: give the terminally-failed-but-repairable run condition (a resume consumed the suspension, a downstream node threw, the run is recorded as failed and can be re-armed only by an explicit operator verb — #13909's condition) a platform-level name on AutomationResult.status, alongside 'completed' | 'paused' | 'failed'. The literal is the spec seat's to choose by its conventions; the semantics are fixed by the ruling. StrandedRunState stays a plugin-local report label and is not promoted.

Executable acceptance: git show origin/main:packages/spec/src/contracts/automation-service.ts | grep -n "status" shows the new literal in the AutomationResult.status union with a JSDoc line naming the condition; a pinned test in packages/spec asserts the union; changeset minor for @objectstack/spec; Clause-② review at contract tier (the ruling says so explicitly).

What it does NOT ask

No engine change, no operator verb, no REST route — those are the services half (#13937 shape 4: resumeInternal ordering untouched, explicit operator re-arm verb) and, separately, #13953 (whose door and permission model are an open question and are not bundled here).

Downstream

#13937 goes pm:blocked with Blocked-by: this card; #13909 stays blocked on #13937. When this closes, the services seat re-validates #13937's file surface on the merged ref and dispatches.

[huangyiirene]

Triage (R+98) — priority:p1 · pm:blocking · needs:contract-review. domain:spec was already right and stays.

On the priority, since it is higher than the card's own weight would suggest. The contract increment itself is one union member plus a JSDoc line — small, and not urgent in isolation. It is p1 because of where it sits: #13937 is priority:p1 pm:blocked and this card is its sole gate, with #13909 blocked behind that. A p2 here would let the queue pick other p1 work ahead of the only thing that unblocks a p1 chain, which is the wrong order for the same total work. pm:blocking records the relationship; the priority makes the queue act on it.

needs:contract-review is applied on the issue, not left for the PR, because the ruling you quote says so in as many words — 「触 spec ⇒ 条款②契约复审档位适用」. Dispatch at the contract-review tier.

Nothing else about the card needed changing. The scope is exact, the ruling is quoted verbatim with its provenance, the acceptance is executable, and the out-of-scope section correctly keeps the services half (#13937) and the operator-verb question (#13953) off it.

---

Generated by Claude Code

[os-sam]

Claim: PM loop, domain:spec seat (seat post #6017)
Session: session_017RbbUMnxkUnWhE4j94v8FE
Branch: claude/issue-14384-automation-result-terminal-failed-status
Worktree: objectstack-issue-14384 (dedicated, per AGENTS.md Prime Directive #11)
Domain: domain:spec
File surface: packages/spec/src/contracts/automation-service.ts (AutomationResult.status union + its JSDoc), one pin test in packages/spec asserting the union, any regenerated product the contract file feeds, one minor changeset for @objectstack/spec (stop on breach; explain in the report)
Container & model: S, mode:subagent, model: claude-fable-5 — node scripts/pm/dispatch-gates.mjs --tier packages/spec/src/contracts/automation-service.ts at 2a26536: no path-derived mandate (clause-② suspect surface); the ruling of record on #13937 (comment 5491060439, maintainer 2026-09-01 「其他同意」) says 「触 spec ⇒ 条款②契约复审档位适用」 ⇒ contract-review tier
Clause-②: yes
Serial constraints cleared: no open PR touches automation-service.ts (the four open needs:contract-review PRs #14608 · #14606 · #14544 · #14580 read by file list — none in packages/spec/src); last landing on the file 54f2240 (#14475, docs-only), no same-day churn; lane siblings in flight #13865 (ui/action.zod.ts), #14291 (api/events.zod.ts) and #13859 (test-only, queued) are file-disjoint — generated products relay via scripts/pm/os-regen-merge.sh. Downstream #13937 (domain:services, pm:blocked on this card, priority:p1) and #13909 behind it: the services seat re-validates on the merged ref; nothing in either pins this union today.

Premise re-read at 2a26536: git show origin/main:packages/spec/src/contracts/automation-service.ts | grep -n status shows line 296 status?: 'completed' | 'paused' | 'failed' — the union still lacks the terminally-failed literal. H17 on-hold trigger-file index (#9857, swept 13:49Z): no entry names this file.

---

Generated by Claude Code