# Review brief: region HA plan 1a (foundations), round 4

Read `CODEX-PLAN-REGION-HA-1A-BRIEF-1.md` first: its "Fixed: do not
re-argue" and "What to check" sections still apply, to the plan at the
commit named in the prompt.

## Round 4

This revision answers your round 3 (`CODEX-PLAN-REGION-HA-1A-R3.md`); the
plan's last section is its dispositions table. The fixes were dry-run:
the host-files package was written into the tree, built for linux,
darwin and windows and tested with the race detector; Task 5's files
alone, and Tasks 5 and 6's alone, were also built and tested, to check
each task's gate passes in order. Then the code was removed.

Give a disposition for the remaining R2-3 issue and your four round 3
findings: resolved, partly resolved (say what is left), or not resolved.
Then report only new findings, including any these fixes introduce:
`Restore`'s `touched` set and its sync loop, the split of the publishOne
tests into Task 7, and the held-open test's second write.

Check task order once more for every task, not only 6 and 7: does any
task's test or code use an identifier that a later task defines?

Do not re-raise anything you have marked resolved in any round.

## Output

As round 1. End with a verdict: ready to build, or not ready.