Implement Rfc

2) Execute task-by-task

For each checklist item in order:

1. Research enough of the codebase that the change fits existing patterns and interfaces.
2. Implement the smallest coherent slice. Prefer tests first for new behavior: add or extend tests before marking the item complete.
3. Use only make targets for build, test, lint, format, serve, etc. (e.g. make test, make lint), not ad hoc commands, unless the Makefile is missing a needed target and the user approves an exception.
4. Do not advance to the next checklist item until tests pass for the current scope.
5. For client-rendered UI (SPA, React, etc.), verify behavior with the browser MCP available in the environment (e.g. Chrome DevTools MCP: navigate, snapshot, screenshot). Do not rely on curl for HTML that requires JavaScript.
6. For external libraries, rely on the repo’s declared versions, lockfiles, and official project documentation (vendor docs, package READMEs) when API details matter.

3) Update the RFC after each task

After completing a task (or a tight sub-task if the RFC splits that way):

1. Check off the item only when implementation and tests match the stated acceptance.
2. Append or update the Implementation notes section with: what changed, files touched, commands run, links to PRs/issues, and anything the next agent must know.

4) Debugging failing tests

• Run tests with verbose output when useful.
• Add focused logging if it helps; if logs are truncated, redirect full output to a file such as debug.log (overwrite each run) and inspect there.

5) Tracking

• Maintain an internal todo list mirroring RFC tasks and substeps; keep it in sync with the RFC checklist.

Confirmation checkpoints

• Before large or irreversible changes, summarize the plan and align with the RFC scope.
• Before marking an item complete, confirm tests for that item are green.

Error handling

• Tests fail: Fix implementation or tests; do not skip tests to proceed.
• Checklist contradicts code: Prefer truth in code; update RFC to reflect reality or file gaps explicitly.