feat: idempotency key, the INTERRUPTED phase, and a real-hub skew suite

The hub now takes an idempotency key and reports INTERRUPTED for a run
its process did not survive, so the client exposes both. The real-hub
suite gained the cross-language half of the idempotency guard: a
repeated key has to answer with the first run's outputs, which only a
real hub can prove.

Signed-off-by: flemming-it <sf@flemming.it>
This commit is contained in:
flemming-it 2026-10-27 01:32:58 +01:00
parent b6c6cc8295
commit 0db793494d
4 changed files with 39 additions and 2 deletions

View file

@ -77,7 +77,19 @@ export interface FlowResult {
/** Where a detached run stands. */
export interface InvocationStatus {
phase: 'PENDING' | 'RUNNING' | 'SUCCEEDED' | 'FAILED' | 'CANCELLED' | 'PHASE_UNKNOWN';
/**
* `INTERRUPTED` means the hub went down while this run was
* executing: it neither finished nor failed on its own, and the
* caller that owns the work decides whether to submit it again.
*/
phase:
| 'PENDING'
| 'RUNNING'
| 'SUCCEEDED'
| 'FAILED'
| 'CANCELLED'
| 'INTERRUPTED'
| 'PHASE_UNKNOWN';
/** Step currently executing, empty unless running. */
currentStep: string;
startedAt: string;