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)
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
@@ -0,0 +1,19 @@
# 2026-06-14-completed-specs-archive/tunnel-health-monitoring (index)
dir: 2026-06-14-completed-specs-archive/tunnel-health-monitoring
## role
Defines specifications for automated health monitoring and recovery of cloudflared tunnels to ensure persistent connectivity for running instances.
## 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/tunnel-health-monitoring/.pi-map.index.md
map: 2026-06-14-completed-specs-archive/tunnel-health-monitoring/.pi-map.md
## workflows
-
## dirty
-
@@ -0,0 +1,19 @@
# 2026-06-14-completed-specs-archive/tunnel-health-monitoring
dir: 2026-06-14-completed-specs-archive/tunnel-health-monitoring
index: 2026-06-14-completed-specs-archive/tunnel-health-monitoring/.pi-map.index.md
## role
Defines specifications for automated health monitoring and recovery of cloudflared tunnels to ensure persistent connectivity for running instances.
## files
- spec.md | Defines requirements for monitoring and recreating cloudflared tunnels for running instances | dep: cloudflared, HTTP health checks, UI components
## arch
Requirements-driven specification document using prose-based system design with functional requirements, success criteria, and operational parameters for a tunnel health monitoring subsystem.
## tags
cloudflared, spec, defines, requirements, monitoring, recreating, tunnels, running
## symbols
-
## workflows
-
## dirty
-
@@ -0,0 +1,35 @@
## ADDED Requirements
### Requirement: System monitors tunnel health
The system SHALL periodically check if active tunnel URLs are reachable and mark them as erroneous if not.
#### Scenario: Healthy tunnel
- **WHEN** a tunnel health check is performed on a running instance
- **THEN** the system receives an HTTP 2xx response
- **AND** the instance status remains "running"
#### Scenario: Broken tunnel
- **WHEN** a tunnel health check is performed on a running instance
- **AND** the response is not HTTP 2xx or the request fails
- **THEN** the instance is marked with tunnel_error status
- **AND** a visual error indicator is displayed in the UI
### Requirement: Users can recreate broken tunnels
The system SHALL allow users to regenerate a temporary tunnel for a running instance without restarting the instance.
#### Scenario: Recreate tunnel
- **WHEN** user clicks "Recreate Tunnel" button on an instance with a broken tunnel
- **THEN** the system stops the existing cloudflared process
- **AND** starts a new cloudflared tunnel
- **AND** updates the instance URL
- **AND** the new URL is displayed in the UI
#### Scenario: Recreate tunnel success
- **WHEN** tunnel recreation completes successfully
- **THEN** the error indicator is removed
- **AND** the instance shows as healthy
#### Scenario: Recreate tunnel failure
- **WHEN** tunnel recreation fails
- **THEN** the error indicator remains
- **AND** an error message is displayed to the user