48 lines
2.5 KiB
Markdown
48 lines
2.5 KiB
Markdown
# Portal — Open Items
|
|
|
|
Only keep unfinished Portal work here.
|
|
|
|
## Active
|
|
- SSH config snippet for power users.
|
|
- Portal-owned email notification preferences/status UX once the API contract exists.
|
|
- 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
|
|
- fold repeated API-client/status-polling patterns and shared state-mapping logic where behavior is already the same
|
|
- fold repeated table/detail/action rendering helpers only where it reduces duplication without hiding page intent
|
|
- 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
|
|
- centralize shared server-management action handling so files/backups/restore/restart flows do not re-implement the same request/toast/poll logic
|
|
- 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
|
|
- prefer behavior-preserving folding over broad refactors
|
|
- merge repeated flows, not concepts
|
|
- keep helpers small and concrete
|
|
- reduce page-local duplication before introducing new abstractions
|
|
- treat runtime/tooling cleanup as contract-sensitive once it touches auth, API integration, or user-visible route behavior
|
|
|
|
## Repo cleanup
|
|
- remove stray root binary `testdameon` from the Portal repo if it still exists after the cleanup pass.
|
|
|
|
## Verify before re-opening
|
|
- restore accepted -> status polling -> completion UX
|
|
- backup metadata rendering, including checkpoint-aware presentation
|
|
- console reconnect/state behavior during restart/restore transitions
|
|
- server management flows that share action/polling/toast logic
|
|
- login/refresh/hosted-IDE flows after API token tightening
|
|
|
|
## Not Portal-owned
|
|
- agent-local backup implementation details.
|
|
- API transport semantics.
|
|
- PBS / infra backup strategy.
|