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

Record API Velocity lifecycle decisions

Browse Source
This commit is contained in:
jester 2026-04-25 20:34:52 +00:00
parent e51ef18828
commit 9a2834bc8d
1 changed files with 6 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
Codex/API/DECISIONS.md
View File

@ -18,6 +18,12 @@
- proxy logging should avoid exposing cookies or detailed forwarded-header values in routine logs. - proxy logging should avoid exposing cookies or detailed forwarded-header values in routine logs.
- legacy worker-based provisioning is no longer a live API path and should stay archived unless intentionally revived. - legacy worker-based provisioning is no longer a live API path and should stay archived unless intentionally revived.
- legacy port allocation / slot reservation is no longer part of the active provisioning model and should stay retired unless intentionally revived end to end. - legacy port allocation / slot reservation is no longer part of the active provisioning model and should stay retired unless intentionally revived end to end.
- Minecraft edge routing uses Velocity; API should call the bridge's real HTTP routes: `POST /zpack/register`, `POST /zpack/unregister`, and `GET /zpack/status`.
- API must not depend on a nonexistent Velocity `/zpack/list` route for registration verification.
- `registered_with_proxy` means Velocity accepted the backend into its routing table; it does not mean the Minecraft backend is confirmed playable.
- `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.
## Tracking rule ## Tracking rule
- when API work completes, remove it from `OPEN_ITEMS.md` - when API work completes, remove it from `OPEN_ITEMS.md`