trio:subsprint-runner

To execute a subsprint plan, you invoke the runner with a prepared plan file to validate front-matter and apply code-path and doc-path edits directly to your code and docs directories for deterministic changes.

To track progress, the runner flips plan checklist entries like Execute Coding and Update Docs as tasks complete, then hands off remaining test case work to a subsprint-sync process for continuous updates.

You validate subsprint plan inputs by passing the plan file to the runner, which resolves and validates the plan front-matter and supports absolute paths, folder names, or bare numeric identifiers.

No, the subsprint runner does not write changes itself; it dispatches execution to apply edits and returns an execution log with per-task results, touched files, side-edits, and verification outcomes.

You get an auditable execution log by running the subsprint plan, which returns per-task results, touched files, side-edits, and verification outcomes to ensure deterministic and auditable changes.

Yes, the subsprint runner supports plan inputs from a planner including absolute paths, folder names, or bare numeric identifiers to resolve and validate the plan front-matter.