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

Track dev shell boundary and dev backup ownership direction in Agent open items

Browse Source
This commit is contained in:
jester 2026-04-19 22:04:50 +00:00
parent 36eaa8942f
commit 2fd5a57239
1 changed files with 4 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
Codex/Agent/OPEN_ITEMS.md
View File

@ -19,6 +19,7 @@ Only keep unfinished Agent work here.
- game/dev template cleanup: remove `node-exporter`, keep Alloy preinstalled, and keep `/etc/default/alloy` fixed to `/etc/alloy/config.alloy` on port `12345`
- Alloy config label cleanup for game/dev containers: keep the required label contract minimal and consistent with dashboards/discovery (`vmid`, `instance`, `container_type`, optional metadata) and remove redundant labels if they add no value
- verify automatic Alloy config refresh path on metadata changes after initial `POST /config`
- resolve dev interactive shell boundary behavior: current live validation indicates PTY/dev console sessions can traverse upward from `/home/dev/workspace`, so confirm whether shell confinement is intended and, if so, implement it at the correct layer
## Cleanup / consolidation priorities
- fold Forge + NeoForge installer flow into one shared helper without changing external behavior
@ -39,6 +40,7 @@ Only keep unfinished Agent work here.
## Clarified boundary
- do not add agent-side remote/offsite backup sync if PBS/platform layer is the intended durability path
- agent backup scope is local, app-aware rollback
- do not assume dev-container backups are agent-owned; current likely direction is platform/LXC-snapshot ownership for dev backups unless that decision changes
## Verify before re-opening
- readiness-aware start/restart unification
@ -50,8 +52,10 @@ Only keep unfinished Agent work here.
- code-server manual start endpoint uses service start path, not installer path
- live backup/restore validation on real Minecraft servers
- current Minecraft runtime provisioning split (`vanilla` internal profile vs normal `fabric`) and Forge/NeoForge first-start handling
- dev shell / PTY behavior relative to the intended workspace boundary model
## Not Agent-owned
- API response-shape normalization for frontend consumers
- portal UX/polish
- PBS/offsite backup strategy
- dev-container snapshot orchestration / retention policy if that ownership stays outside the agent