ultra-tddlisted

# Write one failing test on a seam, then just enough code to pass it Without feedback from code that actually ran, the work is blind flying. This is the loop that supplies it, and it serves Goal 3, Production-Ready. ## Before you start 1. When called from a planned Change, read `../ultra-change/references/change-contract.md` and apply its **Active Change authority resolution** before reading any active `intent.md`, resolving the current `change_id` or task, reading its context, running the baseline, or executing red-green product edits. A stable zero result stops with no current task; any typed diagnostic, including non-unique authority, stops with its repair before the baseline, red-green, or any product write. After one valid authority, read its intent, `.ultra/tasks.json`, and the matching current task context for the seams confirmed during planning. For a micro edit outside the Ultra lifecycle, no active task context is required; use the accepted request, maintained specification, and an existing repository seam, and create no Ultra task or delivery claim. 2. Run the repository's existing test command once, unchanged, to see what passing currently looks like. Read `references/test-execution.md` before recording that run or any red/green evidence. 3. Read `CONTEXT.md` for vocabulary — test names carry the domain words. ## Definition of done - One slice is complete: one seam, one test, one minimal implementation. - The test was obser