alex/headquarter
1
1
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

fix: disable native touch panning on mobile terminal and archive specs

Browse Source 
- Change mobile terminal CSS to use touch-action: none and
  overscroll-behavior: none so the custom touch handler owns swipes
- Archive completed/partial OpenSpec specs to
  openspec/changes/archive/2026-06-14-completed-specs-archive/
- Regenerate project maps

Quality gates: npm run typecheck, npm run lint (apps/web)
This commit is contained in:
Developer
2026-06-14 18:07:01 +00:00
parent 896674195c
commit c8db6ce933
580 changed files with 4678 additions and 4333 deletions
Download Patch File Download Diff File Expand all files Collapse all files
openspec/changes/archive/2026-05-22-sessions-hub/.pi-map.md
+5 -5
View File
@@ -1,16 +1,16 @@
# archive/2026-05-22-sessions-hub
dir: archive/2026-05-22-sessions-hub
# 2026-05-22-sessions-hub
dir: 2026-05-22-sessions-hub
index: archive/2026-05-22-sessions-hub/.pi-map.index.md
index: 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.
Centralized workspace session management feature enabling users to view, organize, and control active tool instances across projects.
## 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
## arch
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.
Product design documents following a structured proposal-to-design-to-tasks workflow, with API-driven backend/frontend coordination and hub-and-spoke navigation pattern.
## tags
sessions, design, hub, feature, workspace, document, implementing, navigation
## symbols