Add Platform Evolution tracking to PROGRESS_V1.md

Phase A complete: route declarations, port allocation, $PORT env vars.
Phase B in progress: agent mc-proxy route registration.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

PROGRESS_V1.md

@@ -70,6 +70,25 @@
   blocks podman runtime dir → relaxed to `ProtectSystem=full`, `ProtectHome=false`
 - Agent needs `PATH`, `HOME`, `XDG_RUNTIME_DIR` in systemd environment
 
+## Platform Evolution (see PLATFORM_EVOLUTION.md)
+
+### Phase A — COMPLETE (2026-03-27)
+
+- [x] Route declarations in service definitions (`[[components.routes]]`)
+- [x] Automatic port allocation by agent (10000-60000, mutex-serialized)
+- [x] `$PORT` / `$PORT_<NAME>` env var injection into containers
+- [x] Proto: `RouteSpec` message, `routes` + `env` on `ComponentSpec`
+- [x] Registry: `component_routes` table with `host_port` tracking
+- [x] Backward compatible: old-style `ports` strings still work
+
+### Phase B — IN PROGRESS
+
+- [ ] Agent connects to mc-proxy via Unix socket on deploy
+- [ ] Agent calls `AddRoute` to register routes with mc-proxy
+- [ ] Agent calls `RemoveRoute` on service stop/teardown
+- [ ] Agent config: `[mcproxy] socket` field
+- [ ] TLS certs: pre-provisioned at convention path (Phase C automates)
+
 ## Remaining Work
 
 ### Operational — Next Priority