From b581ab248056cb3cc1c41f31755ca6995ba1cb17 Mon Sep 17 00:00:00 2001 From: jester Date: Wed, 29 Apr 2026 18:22:23 +0000 Subject: [PATCH] Update API Codex decisions --- Codex/API/DECISIONS.md | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/Codex/API/DECISIONS.md b/Codex/API/DECISIONS.md index 1b11b72..9a57abe 100644 --- a/Codex/API/DECISIONS.md +++ b/Codex/API/DECISIONS.md @@ -24,6 +24,13 @@ - `proxy_ping_ok` / `proxy_ping_failed` are the stronger proxy-side readiness signals because they come from Velocity pinging the registered backend. - Proxy lifecycle state belongs under `ContainerInstance.payload.proxy`, separate from agent readiness and `agentState`. - The Velocity bridge should report proxy lifecycle events to `POST /internal/velocity/proxy-status` using the same hashed `X-Zpack-Secret` auth style. +- Edge publish state and Velocity proxy callback state should be merged into `ContainerInstance.payload` atomically rather than read/modify/write replacing the full JSON payload. +- Underlying Proxmox/LXC lifecycle state is a separate API contract from game runtime readiness and agent readiness. +- Shared host lifecycle routes under `/api/servers/:id/host/*` should serve both game and dev containers. +- Host lifecycle actions should return `202 Accepted` plus an operation/status URL instead of holding the request open until Proxmox completes. +- API must check ownership before any host/LXC lifecycle action. +- API should resolve the actual Proxmox node for a VMID when possible instead of assuming the configured default node is always correct. +- Listener-limit fixes should target the socket creation/attachment point. For outbound Axios/follow-redirects traffic, use configured HTTP/HTTPS agents rather than relying on inbound HTTP socket handling. ## Tracking rule - when API work completes, remove it from `OPEN_ITEMS.md`