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

Refresh API open items after live route and legacy flow review

Browse Source
This commit is contained in:
jester 2026-04-24 18:20:01 +00:00
parent 13f0560b47
commit 76d5ead0d3
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/OPEN_ITEMS.md
View File

@ -8,12 +8,16 @@ Only keep unfinished API work here.
- provisioning validation follow-up where API behavior is involved - provisioning validation follow-up where API behavior is involved
- verify Portal compatibility after API JWT issuer/audience tightening, especially refresh flow and hosted IDE token flow - verify Portal compatibility after API JWT issuer/audience tightening, especially refresh flow and hosted IDE token flow
- verify canonical and compatibility file routes still behave identically across list/stat/read/download/delete/put/revert/upload paths after helper extraction - verify canonical and compatibility file routes still behave identically across list/stat/read/download/delete/put/revert/upload paths after helper extraction
- align merged live-status readiness fields so Portal-facing `agentReady` semantics fully match semantic `/ready`
- verify orphan/manual delete behavior after retirement of legacy PortPool release logic
- decide whether the remaining Portal-side `/api/agent/:serverId/:action` bridge should be deleted outright or formally kept as compatibility-only Portal-owned behavior
## Cleanup / consolidation priorities ## Cleanup / consolidation priorities
- fold repeated ownership/auth/IP-guard patterns into small concrete helpers without hiding route intent - fold repeated ownership/auth/IP-guard patterns into small concrete helpers without hiding route intent
- split oversized route/service files by responsibility without changing route contracts - split oversized route/service files by responsibility without changing route contracts
- keep backup/restore status shaping and async-dispatch logic explicit, but remove duplicated mapping/normalization paths where possible - keep backup/restore status shaping and async-dispatch logic explicit, but remove duplicated mapping/normalization paths where possible
- keep stream-vs-JSON forwarding rules centralized in one place and avoid route-local reimplementation - keep stream-vs-JSON forwarding rules centralized in one place and avoid route-local reimplementation
- keep archived legacy flows out of the live tree unless they are intentionally revived and revalidated against the current schema/contracts
## Completed and moved out of active cleanup ## Completed and moved out of active cleanup
- Node/runtime pinning is no longer an open cleanup-only item; Node 24 pinning is now treated as current repo state - Node/runtime pinning is no longer an open cleanup-only item; Node 24 pinning is now treated as current repo state
@ -21,6 +25,7 @@ Only keep unfinished API work here.
- initial file-proxy route deduplication has been completed; only compatibility verification and follow-on cleanup remain open - initial file-proxy route deduplication has been completed; only compatibility verification and follow-on cleanup remain open
- Prisma config migration is no longer an open item - Prisma config migration is no longer an open item
- baseline proxy cookie/log hardening is no longer an open item - baseline proxy cookie/log hardening is no longer an open item
- worker-era provisioning and detached legacy port reservation have been archived rather than treated as active API surfaces
## Cleanup rule ## Cleanup rule
- prefer behavior-preserving folding over broad refactors - prefer behavior-preserving folding over broad refactors
@ -37,6 +42,7 @@ Only keep unfinished API work here.
- restore async-start contract + status polling semantics - restore async-start contract + status polling semantics
- streamed file edit/revert forwarding through both canonical and compatibility routes - streamed file edit/revert forwarding through both canonical and compatibility routes
- older-session re-login behavior after JWT tightening - older-session re-login behavior after JWT tightening
- Portal-side `/api/agent` bridge usage before deleting any remaining compatibility code around instance lookup assumptions
## Not API-owned ## Not API-owned
- agent-local backup implementation details - agent-local backup implementation details