tdd

# tdd ## Authoritative format boundary For an HTML spec/plan pair, load [includes/artifacts.md](../../includes/artifacts.md) and use the installed structured-artifact engine for artifact I/O. Verify the plan's binding to the approved spec, use typed `index`, `outline`, and symbol-scoped `read`, and follow contextual pages for the selected task. The workflow must not parse rendered HTML for criteria, status, evidence, or authority. Missing or invalid HTML capability is a STOP, not a fallback to Markdown. Existing authoritative Markdown pairs continue through the legacy path. HTML `--farm` dispatch remains blocked. Test-first, or it does not ship. Routed to by `/feature` (after spec approval), `/fix`, and `/refactor`. ## Pre-flight Read these, or STOP and surface the gap — never guess a command or a threshold: - `<project-root>/.codearbiter/CONTEXT.md` — the `stage:` frontmatter (the maturity value) and project context. - `<project-root>/.codearbiter/tech-stack.md` — test, coverage, and lint invocations; file layout; mock patterns. - [includes/verification-boundary.md](../../includes/verification-boundary.md) — the required split between focused local proof and exhaustive exact-head hosted CI. - `<project-root>/.codearbiter/coding-standards.md` — style, structure, naming. Required for Phase 3. - The authoritative approved spec selected by `/feature`. For HTML, read its typed criterion records through the installed engine and confirm the paired plan's exact binding; f...