Add Console Development as highest priority - planned order, constraints, architecture, deferred items
This commit is contained in:
parent
d2b58337ac
commit
ed215ae89f
@ -6,6 +6,30 @@ This document tracks **known open questions and deferred decisions**.
|
||||
|
||||
## High Priority
|
||||
|
||||
### Console Development (Next Phase)
|
||||
|
||||
#### Planned Order
|
||||
1. Read-only console output
|
||||
2. Interactive input (PTY / stdin)
|
||||
3. Permissions & safety controls
|
||||
|
||||
#### Known Constraints
|
||||
- Console state is ephemeral
|
||||
- No persistence of logs
|
||||
- No agent push yet (polling only)
|
||||
|
||||
#### Architecture Direction
|
||||
- Agent owns PTY
|
||||
- API brokers WebSocket sessions
|
||||
- Portal renders terminal (xterm.js)
|
||||
|
||||
#### Explicitly Deferred
|
||||
- Proxmox-based live status polling
|
||||
- Agent push model
|
||||
- Multi-viewer consoles
|
||||
|
||||
---
|
||||
|
||||
### Server Detail / System View
|
||||
- Define System View layout
|
||||
- Decide runtime vs metadata sections
|
||||
|
||||
Loading…
Reference in New Issue
Block a user