subagent-driven-development

# subagent-driven-development ## Structured-artifact format boundary New full-lane workflows default to HTML through the installed engine. Existing HTML pairs use the same path. Load [includes/artifacts.md](../../includes/artifacts.md) before HTML artifact I/O; its typed identity, binding, receipt, contextual-read, and scope-state rules replace rendered-document parsing and direct status-cell edits. Existing authoritative Markdown pairs stay on their exact legacy path without conversion. A missing, invalid, or unqualified HTML capability must fail closed rather than fall back to new Markdown authority. HTML `--farm` dispatch remains disabled. Keep every other workflow gate, including human checkpoints, unchanged. One task, one fresh subagent, two reviews, proof on a fresh run. Routed to by `/sprint` (full plan, autonomous) and by `executing-plans` (one batch at a time, with human checkpoints between batches). The loop processes tasks in dependency order and never trusts a self-report. ## Pre-flight Read these, or STOP and surface the gap — never guess scope, command, or obligation: - `<project-root>/.codearbiter/CONTEXT.md` — the `stage:` frontmatter (the maturity value) and project context. - The discovered authoritative spec/plan pair. Existing Markdown pairs retain their current ledger. For HTML, load [includes/artifacts.md](../../includes/artifacts.md), retain the exact artifact identities and engine-written receipts, and read the approved spec binding, oblig...