chore: patch project maps for multi-session-terminal-ux metadata updates
This commit is contained in:
Developer
@@ -1,44 +1,31 @@
|
||||
# . (index)
|
||||
dir: .
|
||||
|
||||
## Project Map Protocol
|
||||
|
||||
1. Read this protocol and the root `.pi-map.index.md` first.
|
||||
2. Use `index:` / `map:` references to open relevant directory indexes and maps.
|
||||
3. Load indexes before rich maps during task-start navigation.
|
||||
4. Read the local rich map and actual source before editing.
|
||||
5. Treat non-empty `## dirty` sections in either artifact as stale.
|
||||
6. If source and generated artifacts disagree, trust source.
|
||||
7. If map and index disagree, trust neither blindly; verify from source and regenerate the pair.
|
||||
8. After editing source, run `project_map_patch` for each changed file.
|
||||
9. Before broad architectural claims or final handoff, run `project_map_validate` when freshness matters.
|
||||
|
||||
Trust boundary: index routes, map orients, source decides.
|
||||
# openspec/changes (index)
|
||||
dir: openspec/changes
|
||||
|
||||
## role
|
||||
Empty root directory awaiting package initialization or content.
|
||||
Tracks and manages specification changes/versions for OpenAPI documents
|
||||
## parent
|
||||
-
|
||||
index: openspec/.pi-map.index.md
|
||||
map: openspec/.pi-map.md
|
||||
## children
|
||||
- archive
|
||||
index: archive/.pi-map.index.md
|
||||
map: archive/.pi-map.md
|
||||
- multi-session-terminal-ux
|
||||
index: multi-session-terminal-ux/.pi-map.index.md
|
||||
map: multi-session-terminal-ux/.pi-map.md
|
||||
- reorganize-long-files
|
||||
index: reorganize-long-files/.pi-map.index.md
|
||||
map: reorganize-long-files/.pi-map.md
|
||||
- working-copies
|
||||
index: working-copies/.pi-map.index.md
|
||||
map: working-copies/.pi-map.md
|
||||
- workspace-first-ui
|
||||
index: workspace-first-ui/.pi-map.index.md
|
||||
map: workspace-first-ui/.pi-map.md
|
||||
- openspec/changes/archive
|
||||
index: openspec/changes/archive/.pi-map.index.md
|
||||
map: openspec/changes/archive/.pi-map.md
|
||||
- openspec/changes/multi-session-terminal-ux
|
||||
index: openspec/changes/multi-session-terminal-ux/.pi-map.index.md
|
||||
map: openspec/changes/multi-session-terminal-ux/.pi-map.md
|
||||
- openspec/changes/reorganize-long-files
|
||||
index: openspec/changes/reorganize-long-files/.pi-map.index.md
|
||||
map: openspec/changes/reorganize-long-files/.pi-map.md
|
||||
- openspec/changes/working-copies
|
||||
index: openspec/changes/working-copies/.pi-map.index.md
|
||||
map: openspec/changes/working-copies/.pi-map.md
|
||||
- openspec/changes/workspace-first-ui
|
||||
index: openspec/changes/workspace-first-ui/.pi-map.index.md
|
||||
map: openspec/changes/workspace-first-ui/.pi-map.md
|
||||
## files
|
||||
## links
|
||||
index: ./.pi-map.index.md
|
||||
map: ./.pi-map.md
|
||||
index: openspec/changes/.pi-map.index.md
|
||||
map: openspec/changes/.pi-map.md
|
||||
## workflows
|
||||
-
|
||||
## dirty
|
||||
|
||||
@@ -1,27 +1,13 @@
|
||||
# .
|
||||
dir: .
|
||||
# openspec/changes
|
||||
dir: openspec/changes
|
||||
|
||||
index: ./.pi-map.index.md
|
||||
|
||||
## Project Map Protocol
|
||||
|
||||
1. Read this protocol and the root `.pi-map.index.md` first.
|
||||
2. Use `index:` / `map:` references to open relevant directory indexes and maps.
|
||||
3. Load indexes before rich maps during task-start navigation.
|
||||
4. Read the local rich map and actual source before editing.
|
||||
5. Treat non-empty `## dirty` sections in either artifact as stale.
|
||||
6. If source and generated artifacts disagree, trust source.
|
||||
7. If map and index disagree, trust neither blindly; verify from source and regenerate the pair.
|
||||
8. After editing source, run `project_map_patch` for each changed file.
|
||||
9. Before broad architectural claims or final handoff, run `project_map_validate` when freshness matters.
|
||||
|
||||
Trust boundary: index routes, map orients, source decides.
|
||||
index: openspec/changes/.pi-map.index.md
|
||||
|
||||
## role
|
||||
Empty root directory awaiting package initialization or content.
|
||||
Tracks and manages specification changes/versions for OpenAPI documents
|
||||
## files
|
||||
## arch
|
||||
N/A - no files or architectural patterns present to analyze.
|
||||
Simple data structure package with record types for change metadata, likely used by diff/merge tooling
|
||||
## tags
|
||||
-
|
||||
## symbols
|
||||
|
||||
@@ -1,11 +1,11 @@
|
||||
# multi-session-terminal-ux (index)
|
||||
dir: multi-session-terminal-ux
|
||||
# openspec/changes/multi-session-terminal-ux (index)
|
||||
dir: openspec/changes/multi-session-terminal-ux
|
||||
|
||||
## role
|
||||
Design and specification package for implementing multi-session terminal UX support in a web-based tool instance platform.
|
||||
Design specification and implementation documentation for adding multi-session terminal support to a tool instance platform
|
||||
## parent
|
||||
index: ./.pi-map.index.md
|
||||
map: ./.pi-map.md
|
||||
index: openspec/changes/.pi-map.index.md
|
||||
map: openspec/changes/.pi-map.md
|
||||
## children
|
||||
-
|
||||
## files
|
||||
@@ -18,8 +18,8 @@ map: ./.pi-map.md
|
||||
- proposal.md
|
||||
- tasks.md
|
||||
## links
|
||||
index: multi-session-terminal-ux/.pi-map.index.md
|
||||
map: multi-session-terminal-ux/.pi-map.md
|
||||
index: openspec/changes/multi-session-terminal-ux/.pi-map.index.md
|
||||
map: openspec/changes/multi-session-terminal-ux/.pi-map.md
|
||||
## workflows
|
||||
-
|
||||
## dirty
|
||||
|
||||
@@ -1,23 +1,23 @@
|
||||
# multi-session-terminal-ux
|
||||
dir: multi-session-terminal-ux
|
||||
# openspec/changes/multi-session-terminal-ux
|
||||
dir: openspec/changes/multi-session-terminal-ux
|
||||
|
||||
index: multi-session-terminal-ux/.pi-map.index.md
|
||||
index: openspec/changes/multi-session-terminal-ux/.pi-map.index.md
|
||||
|
||||
## role
|
||||
Design and specification package for implementing multi-session terminal UX support in a web-based tool instance platform.
|
||||
Design specification and implementation documentation for adding multi-session terminal support to a tool instance platform
|
||||
## files
|
||||
- .openspec.yaml | Defines an open specification for a multi-session terminal user experience project
|
||||
- .openspec.yaml | Defines metadata for a completed project specification named "multi-session-terminal-ux"
|
||||
- apply-pr1.md | Documents the implementation of database schema, Alembic migration, and TerminalManager multi-session core for a multi-session terminal UX feature. | dep: Alembic, SQLAlchemy, aiosqlite, asyncio, pytest, TerminalSession, TerminalManager, UUIDPrimaryKeyMixin, TimestampMixin, SessionLocal
|
||||
- apply-pr2.md | Empty file with no functionality
|
||||
- apply-pr2.md | Documents the implementation of a multi-session terminal UX with WebSocket routing, REST CRUD endpoints, frontend API client/hook, and auth-focused tests, while maintaining backward compatibility with legacy single-session endpoints. | dep: WebSocket, REST API, React hooks, Python pytest, Docker/PTY, terminal session manager
|
||||
- apply-pr3.md | Documents a pull request implementing a frontend multi-session terminal UI with tabbed management, fullscreen mode, keyboard shortcuts, and mobile support. | dep: React, TypeScript, WebSocket, CSS, Python (backend terminal manager), testing framework
|
||||
- design.md | Software design document specifying architecture and implementation for adding multi-session terminal support (up to 5 concurrent sessions) to an existing tool instance platform | dep: FastAPI, SQLAlchemy, Alembic, React, xterm.js, WebSocket, PTY, docker exec, Python, TypeScript
|
||||
- explore.md | Explores architectural options for adding multi-session terminal support to an existing persistent terminal system, evaluating backend, frontend, protocol, and database design choices with recommendations for MVP implementation. | dep: TerminalManager, TerminalSession, TerminalComponent, TerminalPage, MobileTerminalWrapper, xterm.js, FastAPI, SQLAlchemy, alembic
|
||||
- proposal.md | Proposes architectural changes to support multiple concurrent terminal sessions per tool instance with improved UI/UX features | dep: TerminalManager, TerminalSession, api/terminal.py, TerminalComponent, terminal.tsx, WebSocket protocol, database schema
|
||||
- tasks.md | A software design document detailing a 12-task implementation plan for adding multi-session terminal UX support to a web application, organized across 3 stacked pull requests with TDD acceptance criteria. | dep: Alembic, SQLAlchemy, FastAPI, WebSocket, React, TypeScript, xterm.js, PTY, UUID, pytest, Jest/RTL
|
||||
- tasks.md | A software design document specifying 12 implementation tasks for adding multi-session terminal UX support across backend (Python/FastAPI) and frontend (React/TypeScript) with detailed acceptance criteria, file changes, and TDD testing steps. | dep: Alembic, FastAPI, WebSocket, React, TypeScript, xterm.js (implied), pytest, Jest/npm test
|
||||
## arch
|
||||
Document-driven architecture using stacked PR planning (3 PRs: backend/core, empty/placeholder, frontend/UI), TDD acceptance criteria, and explicit MVP scoping with 5-session concurrency limit.
|
||||
Specification-driven development using phased PR implementation (backend schema/API → WebSocket/REST integration → frontend UI), with FastAPI/Python backend and React/TypeScript frontend, featuring TDD, backward compatibility preservation, and MVP-focused architectural decision records
|
||||
## tags
|
||||
terminal, multi, session, apply, alembic, support, design, implementation
|
||||
terminal, session, multi, apply, implementation, alembic, websocket, support
|
||||
## symbols
|
||||
-
|
||||
## workflows
|
||||
|
||||
Reference in New Issue
Block a user