| 1 | # Review brief: region HA plan 1a (foundations), round 4 |
| 2 | |
| 3 | Read `CODEX-PLAN-REGION-HA-1A-BRIEF-1.md` first: its "Fixed: do not |
| 4 | re-argue" and "What to check" sections still apply, to the plan at the |
| 5 | commit named in the prompt. |
| 6 | |
| 7 | ## Round 4 |
| 8 | |
| 9 | This revision answers your round 3 (`CODEX-PLAN-REGION-HA-1A-R3.md`); the |
| 10 | plan's last section is its dispositions table. The fixes were dry-run: |
| 11 | the host-files package was written into the tree, built for linux, |
| 12 | darwin and windows and tested with the race detector; Task 5's files |
| 13 | alone, and Tasks 5 and 6's alone, were also built and tested, to check |
| 14 | each task's gate passes in order. Then the code was removed. |
| 15 | |
| 16 | Give a disposition for the remaining R2-3 issue and your four round 3 |
| 17 | findings: resolved, partly resolved (say what is left), or not resolved. |
| 18 | Then report only new findings, including any these fixes introduce: |
| 19 | `Restore`'s `touched` set and its sync loop, the split of the publishOne |
| 20 | tests into Task 7, and the held-open test's second write. |
| 21 | |
| 22 | Check task order once more for every task, not only 6 and 7: does any |
| 23 | task's test or code use an identifier that a later task defines? |
| 24 | |
| 25 | Do not re-raise anything you have marked resolved in any round. |
| 26 | |
| 27 | ## Output |
| 28 | |
| 29 | As round 1. End with a verdict: ready to build, or not ready. |
| 30 | |
amadan