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
@@ -1,17 +1,17 @@
# archive/2026-05-22-instance-proxy
dir: archive/2026-05-22-instance-proxy
# 2026-05-22-instance-proxy
dir: 2026-05-22-instance-proxy
index: archive/2026-05-22-instance-proxy/.pi-map.index.md
index: 2026-05-22-instance-proxy/.pi-map.index.md
## role
Provides design documentation and planning artifacts for an authenticated HTTP/WebSocket proxy service that enables secure user access to internal Docker containerized tool instances.
Provides an authenticated HTTP/WebSocket proxy layer to expose internal Docker containerized tool instances to users through a single API endpoint, replacing broken localhost links.
## files
- .openspec.yaml | Defines an OpenAPI specification configuration file with schema type and creation date metadata
- design.md | Design document for implementing a FastAPI-based HTTP/WebSocket proxy to allow users to access internal Docker tool instances through a single authenticated API endpoint. | dep: FastAPI, httpx, starlette.websockets, Docker
- proposal.md | Proposes adding an HTTP/WebSocket proxy endpoint to expose Docker containerized tool instances to users over HTTPS instead of broken localhost links | dep: docker, backend API, frontend, WebSocket, HTTPS
- tasks.md | Project task tracking checklist for implementing a proxy endpoint system that routes HTTP/WebSocket traffic to Docker container instances | dep: Docker, FastAPI/httpx, WebSocket, code-server, ruff, mypy
## arch
Document-driven design specification using markdown-based design docs, proposals, and task tracking; intended FastAPI implementation with OpenAPI spec for a reverse proxy routing layer between external HTTPS and internal Docker instances.
FastAPI-based reverse proxy architecture with WebSocket support, using OpenAPI-specified endpoints for authenticated traffic routing to dynamic Docker container instances.
## tags
docker, websocket, design, fastapi, http, proxy, instances, endpoint
## symbols