RunStatus

One of 9 shapes:

1. state: "created"

   The Run document exists; nothing has been asked to start.

   Field	Type	Description
   staterequired	"created"

2. state: "starting"

   Admission, materialization and session creation are under way.

   Field	Type	Description
   staterequired	"starting"

3. state: "running"

   The provider is up. attention and control are the markers §7.5 and §7.4 put on a running run instead of more states; both default so a header written before either existed still reads.

   Field	Type	Description
   attention	AttentionSet	Default []
   control	ControlState	Default {"holder":"orchestrator"}
   staterequired	"running"

4. state: "interrupted"

   A restart ended the attempt (D10). Never Failed; offers Resume.

   Field	Type	Description
   prior_attemptrequired	PriorAttempt	What recovery could prove about the attempt a restart interrupted (§7.6).
   staterequired	"interrupted"

5. state: "completed"

   An orchestrator turn completed the objective with nothing pending.

   Field	Type	Description
   staterequired	"completed"

6. state: "failed"

   Field	Type	Description
   stagerequired	FailureStage	Why a start or a turn failed. A closed vocabulary - a stage, never a message - so a failure can be reported anywhere without carrying text.
   staterequired	"failed"

7. state: "cancelled"

   Field	Type	Description
   staterequired	"cancelled"

8. state: "awaiting_review"

   Minted for M5 (UC14); no transition reaches it in M1.

   Field	Type	Description
   staterequired	"awaiting_review"

9. state: "waiting_for_participant"

   Minted for M5 (UC13); no transition reaches it in M1.

   Field	Type	Description
   staterequired	"waiting_for_participant"