chore(spec): regenerate api-surface and export-origins; changesets for unboundCause

Co-Authored-By: Claude <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01PU9ijL7gdKme3dFxWKcBE6

Author: claude

.changeset/23842-automation-stamps-unbound-cause.md

@@ -0,0 +1,9 @@
+---
+'@objectstack/service-automation': minor
+---
+
+feat(automation): `getFlowRuntimeStates()` stamps `unboundCause` beside `reason`
+
+Clause-②: yes (widening)
+
+Each branch that decides why an enabled, triggered flow is not armed now answers its closed `FlowUnboundCause` together with its sentence: `deployment_policy`, `disabled_subflow`, `missing_trigger` or `binding_failure`. `GET /automation/_status` passes the rows through unchanged, so the field reaches the console with no route change. Bound, disabled and trigger-less rows carry neither `reason` nor `unboundCause`. The sentences and `getTriggerBindingAudit()` are unchanged.

.changeset/23842-flow-runtime-state-unbound-cause.md

@@ -0,0 +1,18 @@
+---
+'@objectstack/spec': minor
+---
+
+feat(spec): `FlowRuntimeState` gains `unboundCause`, a closed classifier beside `reason`
+
+Clause-②: yes (widening)
+
+`FlowRuntimeState.reason` is a sentence a consumer renders and must not parse, so until now a console could not tell a flow left unarmed by deployment policy from one whose binding is broken: both arrive as `enabled: true, bound: false` with a `reason`. The row now also carries an optional `unboundCause`, present on exactly the rows that carry `reason` and absent on every other row.
+
+Its values are published as `FLOW_UNBOUND_CAUSES` (`@objectstack/spec/contracts`), with the derived type `FlowUnboundCause`:
+
+- `deployment_policy`: package-authored scheduled work is switched off on this deployment. An operator remedy, not a defect.
+- `disabled_subflow`: the flow calls a packaged subflow that is disabled (ADR-0126 §7.3). Enable the subflow and the caller arms.
+- `missing_trigger`: no trigger of the declared type is registered. Depend on the trigger package (`requires: ['triggers']`).
+- `binding_failure`: the trigger is registered but binding the flow to it failed. The earlier boot warnings name the error.
+
+Additive: existing producers and consumers keep working unchanged, and `reason` keeps its text.

packages/spec/api-surface/contracts.json

@@ -100,8 +100,10 @@
     "ExecuteUpgradeInput (interface)",
     "ExplainAccessRequest (interface)",
     "FILE_ATTACHMENT_SERVICE (const)",
+    "FLOW_UNBOUND_CAUSES (const)",
     "FinishReason (type)",
     "FlowRuntimeState (interface)",
+    "FlowUnboundCause (type)",
     "GenerateDraftOpts (interface)",
     "GenerateObjectOptions (interface)",
     "GrantShareInput (interface)",

packages/spec/export-origins/contracts.json

@@ -100,8 +100,10 @@
     "ExecuteUpgradeInput": "src/contracts/package-service.ts#ExecuteUpgradeInput (interface)",
     "ExplainAccessRequest": "src/contracts/security-service.ts#ExplainAccessRequest (interface)",
     "FILE_ATTACHMENT_SERVICE": "src/contracts/storage-service.ts#FILE_ATTACHMENT_SERVICE (const)",
+    "FLOW_UNBOUND_CAUSES": "src/contracts/automation-service.ts#FLOW_UNBOUND_CAUSES (const)",
     "FinishReason": "node_modules/ai/dist/index.d.ts#FinishReason (type)",
     "FlowRuntimeState": "src/contracts/automation-service.ts#FlowRuntimeState (interface)",
+    "FlowUnboundCause": "src/contracts/automation-service.ts#FlowUnboundCause (type)",
     "GenerateDraftOpts": "src/contracts/external-datasource-service.ts#GenerateDraftOpts (interface)",
     "GenerateObjectOptions": "src/contracts/ai-service.ts#GenerateObjectOptions (interface)",
     "GrantShareInput": "src/contracts/sharing-service.ts#GrantShareInput (interface)",