chore(project-map): regenerate .pi-map artifacts across the repo
This commit is contained in:
+7
-7
@@ -1,16 +1,16 @@
|
||||
# 2026-06-14-completed-specs-archive/tool-terminal
|
||||
dir: 2026-06-14-completed-specs-archive/tool-terminal
|
||||
# openspec/changes/archive/2026-06-14-completed-specs-archive/tool-terminal
|
||||
dir: openspec/changes/archive/2026-06-14-completed-specs-archive/tool-terminal
|
||||
|
||||
index: 2026-06-14-completed-specs-archive/tool-terminal/.pi-map.index.md
|
||||
index: openspec/changes/archive/2026-06-14-completed-specs-archive/tool-terminal/.pi-map.index.md
|
||||
|
||||
## role
|
||||
Defines requirements for a browser-based WebSocket terminal interface that enables secure, session-managed access to running Docker containers with bidirectional I/O streaming.
|
||||
Defines requirements for a browser-based WebSocket terminal system providing shell access to running Docker containers with session management, I/O streaming, and access control.
|
||||
## files
|
||||
- spec.md | Specifies requirements for a browser-based WebSocket terminal system for accessing running Docker containers with session management, I/O streaming, and access control. | dep: tool-instances, auth-oauth, xterm.js, ptyprocess
|
||||
- spec.md | Specifies requirements for a browser-based WebSocket terminal system that provides shell access to running Docker containers with session management, I/O streaming, and access control. | dep: tool-instances, auth-oauth, xterm.js, ptyprocess
|
||||
## arch
|
||||
Event-driven WebSocket architecture with session-based multiplexing, container-attach abstraction layer, and token-based access control for real-time bidirectional streaming between browser clients and Docker container TTY/stdout/stderr interfaces.
|
||||
Specification-driven architecture using markdown-based requirements document defining a real-time bidirectional communication system with WebSocket protocol, session state management, and containerized runtime integration.
|
||||
## tags
|
||||
spec, specifies, requirements, browser, websocket, terminal, system, accessing
|
||||
access, spec, specifies, requirements, browser, websocket, terminal, system
|
||||
## symbols
|
||||
-
|
||||
## workflows
|
||||
|
||||
Reference in New Issue
Block a user