Track dev backup direction in root open threads
This commit is contained in:
parent
b9f2a35ff3
commit
36eaa8942f
@ -26,6 +26,12 @@ Keep this file short.
|
|||||||
- resolve the dev console / shell workspace-boundary mismatch: current live validation shows hosted IDE and dev console work, but interactive shell traversal can still `cd ..` upward from `/home/dev/workspace`
|
- resolve the dev console / shell workspace-boundary mismatch: current live validation shows hosted IDE and dev console work, but interactive shell traversal can still `cd ..` upward from `/home/dev/workspace`
|
||||||
- make docs and implementation agree on whether workspace scoping is file-API-only or true interactive-shell confinement
|
- make docs and implementation agree on whether workspace scoping is file-API-only or true interactive-shell confinement
|
||||||
|
|
||||||
|
### Dev backup strategy
|
||||||
|
- define dev-container backup ownership and user-facing restore contract
|
||||||
|
- current likely direction: prefer LXC snapshot-based backup/restore for dev containers instead of agent-managed dev backups
|
||||||
|
- keep game backup ownership separate from dev backup ownership unless that decision changes
|
||||||
|
- confirm how snapshot creation, retention, restore UX, and API/Portal exposure should work for dev containers
|
||||||
|
|
||||||
### Service discovery / launch validation
|
### Service discovery / launch validation
|
||||||
- service discovery migration for remaining hot-path references
|
- service discovery migration for remaining hot-path references
|
||||||
- provisioning validation across current API/Agent/Portal assumptions
|
- provisioning validation across current API/Agent/Portal assumptions
|
||||||
|
|||||||
Loading…
Reference in New Issue
Block a user