PendingJoinPlan
The work a join leaves for the caller. The set is transport-less: it names
the I/O the MUSTs require and the caller performs it, then feeds the
answers back through replayAnswered / acked.
Properties
Section titled “Properties”| Property | Type | Stability | Presence | Description |
|---|---|---|---|---|
kept |
readonly string[] |
required | Entries kept as server-confirmed pending, in their new render order. | |
mustReplay |
readonly string[] |
required | Acked entries the caller MUST resolve by replaying the commandId. |
|
mustResubmit |
readonly string[] |
required | Unacked entries the caller MUST resubmit with the SAME commandId before any retire-to-composer — demanded once per plan (the single ordered pass that builds a plan visits each entry once), re-demanded on each new join; idempotency makes the re-demand safe. A fresh-commandId re-send is the double execution this ordering prevents. |
|
retirements |
readonly PendingRetirement<I>[] |
required |
Source
clients/sdk-ts/src/pending/pending-command-set.ts:175
{ "kind": "Interface", "canonicalPath": "PendingJoinPlan"}