Move ZpackCommands to optional note in Velocity thread

This commit is contained in:
jester 2026-04-10 21:37:30 +00:00
parent 6d6be18a84
commit a0a9261677

View File

@ -147,12 +147,17 @@ Completed:
- stale default `zpack-api.internal.zlh` fallback removed - stale default `zpack-api.internal.zlh` fallback removed
- explicit `ZPACK_REHYDRATE_ENDPOINT` env wiring validated - explicit `ZPACK_REHYDRATE_ENDPOINT` env wiring validated
- happy-path player routing validated live after restart - happy-path player routing validated live after restart
- negative-path startup validation passed: no backend registered when rehydrate returned zero eligible servers
Outstanding: Outstanding:
- ZpackCommands not registered (`/zpack status`, `/zpack list`, `/zpack reload`) - confirm whether any remaining agent-side registration path can surface a backend before readiness probe success
- negative-path readiness validation still pending for a `ready=false` backend
- see `SCRATCH/velocity-plugin.md` - see `SCRATCH/velocity-plugin.md`
Optional / Nonessential:
- `ZpackCommands` exist in code but are not currently needed operationally
- prefer plugin HTTP status endpoint and host metrics over in-proxy admin commands
- if metrics coverage is sufficient, command registration can remain omitted or the command class can be removed later
--- ---
## Pre-Launch Checklist ## Pre-Launch Checklist