What problem does it solve? Long-running autonomous coding sessions tend to drift out of scope, touch protected hot paths, or silently widen into adjacent domains. This Skill keeps an agent executing a pre-defined cleanup or build lane overnight while enforcing lane boundaries, stop conditions, and a truthful control trail after every tranche. ## Core Features & Use Cases - Bounded autonomous execution: Keeps iterating on an already-decomposed lane without reopening scope each cycle, stopping on ambiguity instead of widening. - Hot-path protection: Explicitly forbids widening from non-TUI cleanup into TUI or dashboard hot paths and treats untracked files as not merge-safe. - Structured control trail: Requires a six-part report after each tranche covering current lane, tranche completed, files changed, validation performed, residual risks, and the next bounded seam. - Use Case: An operator defines a cleanup lane in a control document before leaving for the night; the agent works through tranches, updates the control docs and frontmatter as it goes, and stops with a recorded note when it hits unresolved ownership or path-coupling ambiguity. ## Quick Start Activate the dharma-autonomous-build mode and execute the next bounded tranche of the cleanup lane defined in the overnight control document, then report files changed and residual risks.
