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

- 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)
2026-06-14 18:07:01 +00:00
parent 896674195c
commit c8db6ce933
580 changed files with 4678 additions and 4333 deletions
@@ -0,0 +1,19 @@
+# 2026-06-14-completed-specs-archive/session-lifecycle-ux (index)
+dir: 2026-06-14-completed-specs-archive/session-lifecycle-ux
+
+## role
+Defines UI/UX requirements for session lifecycle management including confirmation flows and real-time deletion feedback.
+## parent
+index: 2026-06-14-completed-specs-archive/.pi-map.index.md
+map: 2026-06-14-completed-specs-archive/.pi-map.md
+## children
+-
+## files
+- spec.md
+## links
+index: 2026-06-14-completed-specs-archive/session-lifecycle-ux/.pi-map.index.md
+map: 2026-06-14-completed-specs-archive/session-lifecycle-ux/.pi-map.md
+## workflows
+-
+## dirty
+-
@@ -0,0 +1,19 @@
+# 2026-06-14-completed-specs-archive/session-lifecycle-ux
+dir: 2026-06-14-completed-specs-archive/session-lifecycle-ux
+
+index: 2026-06-14-completed-specs-archive/session-lifecycle-ux/.pi-map.index.md
+
+## role
+Defines UI/UX requirements for session lifecycle management including confirmation flows and real-time deletion feedback.
+## files
+- spec.md | Defines software requirements for session management UI behaviors including stop confirmation dialogs and immediate deletion updates
+## arch
+Specification-driven design using requirements documentation with behavioral definitions for user-facing state transitions.
+## tags
+spec, defines, software, requirements, session, management, behaviors, including
+## symbols
+-
+## workflows
+-
+## dirty
+-
@@ -0,0 +1,34 @@
+## ADDED Requirements
+
+### Requirement: Stopping a session requires confirmation
+The system SHALL display a confirmation dialog before stopping a running session.
+
+#### Scenario: User initiates stop
+- **WHEN** user clicks the "Stop" button on a running session
+- **THEN** a confirmation dialog appears asking "Are you sure you want to stop this session?"
+- **AND** the dialog provides "Cancel" and "Stop" options
+
+#### Scenario: User confirms stop
+- **WHEN** user clicks "Stop" in the confirmation dialog
+- **THEN** the session stops
+- **AND** the dialog closes
+
+#### Scenario: User cancels stop
+- **WHEN** user clicks "Cancel" in the confirmation dialog
+- **THEN** the dialog closes
+- **AND** the session remains running
+
+### Requirement: Deleted sessions disappear from UI immediately
+The system SHALL update the frontend state immediately after a session is successfully deleted.
+
+#### Scenario: Delete session
+- **WHEN** user deletes a session
+- **AND** the delete API call returns success
+- **THEN** the session is removed from the visible list
+- **AND** no page reload is required
+
+#### Scenario: Delete session failure
+- **WHEN** user deletes a session
+- **AND** the delete API call fails
+- **THEN** the session remains in the list
+- **AND** an error message is displayed