atomic-level-checklist-md-confirm-approval-neededlisted

Create a step-by-step atomic-level checklist as a .md file so we can walk through every item and make sure nothing is missed. ## The loop — slower than you want to move, ALWAYS 1. **Smoke-test FIRST (baseline).** Before writing the plan, look at the current state from multiple angles. Run the read-only checks that tell us what's already there, what's broken, what the expected behavior is. Write the baseline into the checklist as "BEFORE" state so we have a diff anchor. 2. **Build the atomic checklist .md** with this structure per item: - **Every atomic step MUST begin with a GitHub-flavored markdown checkbox: `- [ ]`** — so we can visually confirm completion at a glance. Unchecked = not done. `[x]` = done AND verified. Never mark `[x]` until the verification command has passed. - What to do (exact file + line / exact command) - Why (root cause / constraint / contract the item serves) - Verification command (proves it happened — not "ran without error," but "state matches expectation") - Rollback path (how to undo in one step) - Owner (which parallel agent or master) Example row format: ```markdown - [ ] **P1.3 — Cap Redis at 512MB with allkeys-lru** - File: `docker-compose.yml` line 47 (redis service command) - Why: Redis was unbounded → OOM risk under load - Verify: `docker exec redis redis-cli CONFIG GET maxmemory` → returns `536870912` - Rollback: `git revert <commit>` - Owner: worker-A ``` 3. **Break the checklis