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

Trim Portal Codex open items after Node 24 and cleanup pass

Browse Source
This commit is contained in:
jester 2026-04-19 21:25:32 +00:00
parent 29f7710173
commit e2beb04d21
1 changed files with 13 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

16
Codex/Portal/OPEN_ITEMS.md
View File

@ -6,6 +6,7 @@ Only keep unfinished Portal work here.
- SSH config snippet for power users. - SSH config snippet for power users.
- Portal-owned email notification preferences/status UX once the API contract exists. - Portal-owned email notification preferences/status UX once the API contract exists.
- checkpoint-specific backup metadata presentation once the API sends the final fields. - checkpoint-specific backup metadata presentation once the API sends the final fields.
- verify Portal compatibility against API-side JWT/auth hardening, especially login refresh and hosted IDE entry flow after token tightening.
## Cleanup / consolidation priorities ## Cleanup / consolidation priorities
- fold repeated API-client/status-polling patterns and shared state-mapping logic where behavior is already the same - fold repeated API-client/status-polling patterns and shared state-mapping logic where behavior is already the same
@ -13,23 +14,32 @@ Only keep unfinished Portal work here.
- split oversized page/component/state files by responsibility without changing user-visible behavior - split oversized page/component/state files by responsibility without changing user-visible behavior
- keep restore/status wording explicit, but remove duplicate operation-label and status-reason mapping where possible - keep restore/status wording explicit, but remove duplicate operation-label and status-reason mapping where possible
- centralize shared server-management action handling so files/backups/restore/restart flows do not re-implement the same request/toast/poll logic - centralize shared server-management action handling so files/backups/restore/restart flows do not re-implement the same request/toast/poll logic
- standardize repo-local Node version declaration with the current pinned platform version - continue API client surface cleanup where overlapping wrappers or legacy paths still exist
## Completed and moved out of active cleanup
- Node/runtime pin alignment is no longer an open cleanup-only item; Portal is now treated as being on the Node 24 baseline
- Next 16 lint-script migration is no longer an open item
- initial dead HUD wrapper cleanup is no longer an open item
- stale legacy CSS cleanup is no longer an open item
- baseline dependency pruning and audit cleanup are no longer open items
- current TypeScript / build breakage reported during the cleanup pass is no longer an open item
## Cleanup rule ## Cleanup rule
- prefer behavior-preserving folding over broad refactors - prefer behavior-preserving folding over broad refactors
- merge repeated flows, not concepts - merge repeated flows, not concepts
- keep helpers small and concrete - keep helpers small and concrete
- reduce page-local duplication before introducing new abstractions - reduce page-local duplication before introducing new abstractions
- treat Node/runtime/dependency upgrades as separate validation work, not part of cleanup-only changes - treat runtime/tooling cleanup as contract-sensitive once it touches auth, API integration, or user-visible route behavior
## Repo cleanup ## Repo cleanup
- remove stray root binary `testdameon` from the Portal repo. - remove stray root binary `testdameon` from the Portal repo if it still exists after the cleanup pass.
## Verify before re-opening ## Verify before re-opening
- restore accepted -> status polling -> completion UX - restore accepted -> status polling -> completion UX
- backup metadata rendering, including checkpoint-aware presentation - backup metadata rendering, including checkpoint-aware presentation
- console reconnect/state behavior during restart/restore transitions - console reconnect/state behavior during restart/restore transitions
- server management flows that share action/polling/toast logic - server management flows that share action/polling/toast logic
- login/refresh/hosted-IDE flows after API token tightening
## Not Portal-owned ## Not Portal-owned
- agent-local backup implementation details. - agent-local backup implementation details.