gsd-orchestrator-runtime

Multi-agent orchestration for Ignition SDK module work coordinates cross-session tasks using a file-based runtime state model. It manages backend, frontend, and packaging work through durable task states stored in `.agents/runtime/` to survive interruptions.

File-based runtime state management persists task lifecycles on disk instead of hidden conversation state. It satisfies bootstrapping, routing, and resume needs by coordinating cross-session collaboration through role-based dispatch into discuss, planner, supervisor, implementer, and reviewer flows.

To bootstrap runtime mode for a large task, initialize a new runtime task with a unique task-id. This enables durable task state on disk, allowing you to manage cross-stack work and re-enter sessions without relying on hidden conversation state.

Use a multi-agent orchestrator when a task is large, cross-stack, long-running, or likely to span multiple sessions. It is necessary for coordinating backend, frontend, and packaging work among multiple roles through repository-local state management.

Yes, role-based routing manages Ignition SDK tasks by dispatching work into discuss, planner, supervisor, implementer, and reviewer flows. This coordinates cross-stack development work spanning backend, frontend, and packaging through file-based task lifecycle management.

Runtime-backed orchestration supports resuming interrupted cross-session work through durable task state on disk. By managing task lifecycles via `.agents/runtime/`, it satisfies bootstrapping and resume needs without relying on hidden conversation state.