chore: archive 15 completed OpenSpec changes
Move the following audited-and-implemented changes into openspec/changes/archive/2026-06-12-completed-changes-archive/: - backend-frontend-refactoring - config-profile-git-mounts - config-profile-includes-ui - config-profile-multi-repo-mounts - container-monitoring-notifications - git-mount-url-validation - home-path-expansion - mobile-terminal-ux - mount-specificity-ordering - notification-center - persistent-terminal-sessions - session-list-overhaul - ssh-key-mounting - terminal-fullscreen-unified-header - tool-session-progress-and-updates Also regenerated .pi-map*.md files for openspec/changes so the remaining active changes (multi-session-terminal-ux, reorganize-long-files, working-copies, workspace-first-ui) reflect the new layout.
This commit is contained in:
@@ -1,7 +1,7 @@
|
||||
# openspec/changes/archive/2026-05-22-sessions-hub
|
||||
dir: openspec/changes/archive/2026-05-22-sessions-hub
|
||||
# archive/2026-05-22-sessions-hub
|
||||
dir: archive/2026-05-22-sessions-hub
|
||||
|
||||
index: openspec/changes/archive/2026-05-22-sessions-hub/.pi-map.index.md
|
||||
index: archive/2026-05-22-sessions-hub/.pi-map.index.md
|
||||
|
||||
## role
|
||||
Design and planning package for a centralized Sessions Hub feature that manages user workspace sessions across projects.
|
||||
@@ -10,7 +10,7 @@ Design and planning package for a centralized Sessions Hub feature that manages
|
||||
- proposal.md | Proposes a centralized "Sessions Hub" feature for managing active tool instances across projects
|
||||
- tasks.md | Project task tracking document for implementing a Sessions Hub feature across backend and frontend | dep: UserConfig model, Alembic, Pydantic, AppShell, React Router, sessions context, workspace, npm
|
||||
## arch
|
||||
Specification-driven architecture using markdown-based design documents (design.md, proposal.md, tasks.md) to define requirements, API contracts, and implementation tasks before code development.
|
||||
Documentation-driven architecture using markdown-based design documents (design.md, proposal.md, tasks.md) to specify page layouts, navigation flows, data models, and API contracts before implementation.
|
||||
## tags
|
||||
sessions, design, hub, feature, workspace, document, implementing, navigation
|
||||
## symbols
|
||||
|
||||
Reference in New Issue
Block a user