Add Codex repo-specific tracking structure
This commit is contained in:
parent
1b2c549b78
commit
b4343ae1e9
36
Codex/Portal/CURRENT_STATE.md
Normal file
36
Codex/Portal/CURRENT_STATE.md
Normal file
@ -0,0 +1,36 @@
|
||||
# Portal — Current State
|
||||
|
||||
This file records what is believed to be implemented now.
|
||||
|
||||
## Readiness / operation UI
|
||||
- Portal consumes API-normalized state.
|
||||
- Portal understands:
|
||||
- `ready`
|
||||
- `operationInProgress`
|
||||
- `operationType`
|
||||
- `maintenance`
|
||||
- `operationStartedAt`
|
||||
- `operationMessage`
|
||||
- targeted `409` and `503` UX messaging exists for operation conflicts and not-ready states.
|
||||
|
||||
## Backup UI
|
||||
- game backup UI exists for:
|
||||
- list
|
||||
- create
|
||||
- restore
|
||||
- delete
|
||||
- Portal uses API routes, not direct agent calls.
|
||||
|
||||
## Console / action gating
|
||||
- console command transport uses POST JSON through API.
|
||||
- previous blanket `ready === false` gating bug for game actions was fixed.
|
||||
- Start is not blocked merely because a stopped server is not ready.
|
||||
- backup actions are not blocked purely by `ready === false`; backend validity decides.
|
||||
|
||||
## Billing / auth / onboarding
|
||||
- billing UI alignment exists with the newer billing state model.
|
||||
- forgot/reset password flow exists.
|
||||
- first-login onboarding flow exists.
|
||||
|
||||
## Dashboard / IA
|
||||
- spotlight server card/dashboard refresh landed.
|
||||
Loading…
Reference in New Issue
Block a user