Expand description
Job state machine and dispatch (RFC §10).
Phase 3 implements the core lifecycle: a tool.invoke envelope is
turned into a Job that runs in its own tokio task with a
CancellationToken. The runtime emits job.accepted,
job.started, then a terminal job.completed / job.failed /
job.cancelled.
The heartbeat watchdog and hard-kill escalation that the RFC describes
in §10.3 / §10.4 land in a follow-up phase; the cooperative cancel
path is in place via CancellationToken.
Structs§
- JobEntry
- Per-job runtime bookkeeping.
- JobRegistry
- Map of in-flight jobs, keyed by
JobId. - JobSnapshot
- Public projection of
JobEntryreturned byJobRegistry::snapshot.
Enums§
- JobState
- Job state (RFC §10.2).