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/readiness-probe-integration (index)
+dir: 2026-06-14-completed-specs-archive/readiness-probe-integration
+
+## role
+Defines specifications for container readiness probe integration during instance startup to determine when services are ready to receive traffic.
+## 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/readiness-probe-integration/.pi-map.index.md
+map: 2026-06-14-completed-specs-archive/readiness-probe-integration/.pi-map.md
+## workflows
+-
+## dirty
+-
@@ -0,0 +1,19 @@
+# 2026-06-14-completed-specs-archive/readiness-probe-integration
+dir: 2026-06-14-completed-specs-archive/readiness-probe-integration
+
+index: 2026-06-14-completed-specs-archive/readiness-probe-integration/.pi-map.index.md
+
+## role
+Defines specifications for container readiness probe integration during instance startup to determine when services are ready to receive traffic.
+## files
+- spec.md | Defines requirements for container readiness probe configuration, execution, and result storage during instance startup | dep: docker, container orchestration, health endpoint, logging system
+## arch
+Specification-driven documentation pattern with requirements organized around configuration, execution, and storage concerns.
+## tags
+spec, defines, requirements, container, readiness, probe, configuration, execution
+## symbols
+-
+## workflows
+-
+## dirty
+-
@@ -0,0 +1,51 @@
+## ADDED Requirements
+
+### Requirement: Readiness probe configuration
+The system SHALL use tool type readiness probe configuration during instance startup.
+
+#### Scenario: Web tool with custom probe
+- **GIVEN** a tool type with `readiness_probe` configured as:
+  - `command: "curl -f http://localhost:8080/api/health"`
+  - `timeout: 60`
+  - `interval: 5`
+- **WHEN** an instance of this type starts
+- **THEN** the system executes the probe command inside the container
+- **AND** retries every 5 seconds for up to 60 seconds
+- **AND** the instance remains in "starting" status until probe succeeds
+
+#### Scenario: Web tool with default probe
+- **GIVEN** a web-enabled tool type with no `readiness_probe` configured
+- **WHEN** an instance of this type starts
+- **THEN** the system uses the default probe: `curl -f http://localhost:{port}`
+- **AND** retries every 2 seconds for up to 30 seconds
+
+#### Scenario: Probe command execution
+- **GIVEN** a readiness probe command
+- **WHEN** the system executes it inside the container
+- **THEN** it runs via `docker exec {container_id} sh -c "{command}"`
+- **AND** stdout/stderr are captured for diagnostics
+- **AND** exit code 0 indicates success
+
+### Requirement: Probe result storage
+The system SHALL store readiness probe results for diagnostics.
+
+#### Scenario: Successful probe logged
+- **GIVEN** a readiness probe that succeeds
+- **WHEN** the probe returns exit code 0
+- **THEN** the success is logged with timestamp
+- **AND** the instance status changes to "running"
+
+#### Scenario: Failed probe logged
+- **GIVEN** a readiness probe that fails or times out
+- **WHEN** the probe reaches timeout
+- **THEN** the failure is logged with last stdout/stderr output
+- **AND** the instance status changes to "unhealthy"
+- **AND** the probe output is available via the health endpoint
+
+## MODIFIED Requirements
+
+None.
+
+## REMOVED Requirements
+
+None.