jester/zlh-grind
1
0
Fork 0
Code Issues 14 Pull Requests Actions Packages Projects Releases Wiki Activity

Update API Codex decisions

Browse Source
This commit is contained in:
jester 2026-04-29 18:22:23 +00:00
parent 390c1655fd
commit b581ab2480
1 changed files with 7 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
Codex/API/DECISIONS.md
View File

@ -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_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`. - 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. - 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 ## Tracking rule
- when API work completes, remove it from `OPEN_ITEMS.md` - when API work completes, remove it from `OPEN_ITEMS.md`