chore(project-map): regenerate .pi-map artifacts across the repo

This commit is contained in:
Developer
2026-06-17 11:31:24 +00:00
parent 0dd5f2317b
commit 93da9b42a2
683 changed files with 5075 additions and 4965 deletions
@@ -1,18 +1,18 @@
# 2026-05-22-sessions-hub
dir: 2026-05-22-sessions-hub
# openspec/changes/archive/2026-05-22-sessions-hub
dir: openspec/changes/archive/2026-05-22-sessions-hub
index: 2026-05-22-sessions-hub/.pi-map.index.md
index: openspec/changes/archive/2026-05-22-sessions-hub/.pi-map.index.md
## role
Centralized workspace session management feature enabling users to view, organize, and control active tool instances across projects.
This package contains archived planning documents for a "Sessions Hub" feature that would provide centralized workspace session management in the OpenSpec project.
## files
- design.md | Design document for implementing a Sessions Hub feature with page layout, navigation, data flow, and API changes for managing user workspace sessions. | dep: Navigation, AppShell, SessionsPage, UserConfig, API endpoints (/users/me/sessions, /users/me/config), workspace, state management, polling
- 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
- design.md | Design document for a "Sessions Hub" feature that provides a central UI for managing, creating, and resuming user workspace sessions with navigation integration and persistent last-session tracking. | dep: Navigation/AppShell, SessionsPage, UserConfig API, sessions API, workspace navigation, project/repository selectors
- proposal.md | Product proposal document defining a Sessions Hub feature for centralized management of active tool instances/sessions
- tasks.md | Project task checklist tracking implementation of a Sessions Hub feature across backend, frontend, and quality gates
## arch
Product design documents following a structured proposal-to-design-to-tasks workflow, with API-driven backend/frontend coordination and hub-and-spoke navigation pattern.
Document-driven waterfall planning with separate design, proposal, and task tracking artifacts for cross-functional (backend/frontend/QA) feature implementation.
## tags
sessions, design, hub, feature, workspace, document, implementing, navigation
sessions, design, hub, feature, proposal, document, navigation, tracking
## symbols
-
## workflows