# STATUS — phase pvfix (proxy /16 VIP exhaustion fix)

**Updated:** 2026-06-13T05:53Z  
**Phase:** pvfix  
**Builder:** autonomic-bot

---

## DONE

Both gates have fresh Adversary PASSes (dated 2026-06-13, within 24h).

### Evidence

| Check | Result |
|---|---|
| M1 PASS (patch + procedure) | 2026-06-13T05:33Z — see REVIEW-pvfix.md |
| M2 PASS (live fix + health) | 2026-06-13T05:49Z — see REVIEW-pvfix.md |
| `proxy` subnet on host | `10.10.0.0/16` (was `10.0.1.0/24`) |
| All 9 swarm services | 1/1 |
| `ci.commoninternet.net` | HTTP/2 200 |
| `drone.ci.commoninternet.net` | HTTP/2 303 |
| `nix/modules/swarm.nix` commit | `e6349a9` — `--subnet 10.10.0.0/16` |
| nixos-rebuild applied | swarm-init activated 2026-06-13T05:38:17 UTC |

### Adversary finding A1

Filed by Adversary (2026-06-13, pvfix): `deploy-proxy` health gate circular dependency on fresh boot.
Pre-existing issue (not introduced by pvfix), D8 risk. Not a VETO on pvfix DONE.
Deferred to `machine-docs/DEFERRED.md` (entry: `2026-06-13 — deploy-proxy health-gate circular dependency`).

---

## Definition-of-Done checklist (pvfix)

- [x] `proxy` is explicitly configured and live as a `/16`
- [x] The change is committed and pushed to cc-ci (`e6349a9`)
- [x] Core routes are healthy after the maintenance action
- [x] Adversary has signed off on M1 in `machine-docs/REVIEW-pvfix.md`
- [x] Adversary has signed off on M2 in `machine-docs/REVIEW-pvfix.md`

Phase pvfix complete.
