From 76d5ead0d3b4a9b8c3b67f9d30274fd55f9a6cca Mon Sep 17 00:00:00 2001 From: jester Date: Fri, 24 Apr 2026 18:20:01 +0000 Subject: [PATCH] Refresh API open items after live route and legacy flow review --- Codex/API/OPEN_ITEMS.md | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/Codex/API/OPEN_ITEMS.md b/Codex/API/OPEN_ITEMS.md index 604b012..d519f8a 100644 --- a/Codex/API/OPEN_ITEMS.md +++ b/Codex/API/OPEN_ITEMS.md @@ -8,12 +8,16 @@ Only keep unfinished API work here. - 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 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 - 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 - 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 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 - 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 - Prisma config migration 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 - prefer behavior-preserving folding over broad refactors @@ -37,6 +42,7 @@ Only keep unfinished API work here. - restore async-start contract + status polling semantics - streamed file edit/revert forwarding through both canonical and compatibility routes - 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 - agent-local backup implementation details