Record Portal Codex decisions from Node 24 and cleanup pass
This commit is contained in:
parent
e2beb04d21
commit
aecc641a0f
@ -5,6 +5,11 @@
|
|||||||
- `agentStatus === online` is not enough by itself for game action eligibility.
|
- `agentStatus === online` is not enough by itself for game action eligibility.
|
||||||
- `ready === false` does not automatically mean a stopped server is unstartable.
|
- `ready === false` does not automatically mean a stopped server is unstartable.
|
||||||
- backup actions should not be blocked purely by frontend readiness assumptions when backend can decide validity.
|
- backup actions should not be blocked purely by frontend readiness assumptions when backend can decide validity.
|
||||||
|
- Portal is now tracked on a Node 24 baseline aligned with the API runtime line.
|
||||||
|
- Portal linting should use the current ESLint / Next 16-compatible path rather than removed `next lint` behavior.
|
||||||
|
- confirmed-unused HUD wrapper components and stale legacy CSS should stay removed rather than being reintroduced as dead scaffolding.
|
||||||
|
- runtime/tooling cleanup is allowed when it preserves user-visible behavior and keeps lint/build green.
|
||||||
|
- Portal should preserve compatibility with API auth and hosted IDE flows even when API token verification is tightened.
|
||||||
|
|
||||||
## Tracking rule
|
## Tracking rule
|
||||||
- when Portal work completes, remove it from `OPEN_ITEMS.md`
|
- when Portal work completes, remove it from `OPEN_ITEMS.md`
|
||||||
|
|||||||
Loading…
Reference in New Issue
Block a user