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
@@ -1,23 +1,23 @@
|
||||
# archive/2026-05-22-opencode-web-terminal (index)
|
||||
dir: archive/2026-05-22-opencode-web-terminal
|
||||
# 2026-05-22-opencode-web-terminal (index)
|
||||
dir: 2026-05-22-opencode-web-terminal
|
||||
|
||||
## role
|
||||
Design and planning package for adding web terminal accessibility to OpenCode through standardized port configuration and web interface support.
|
||||
Infrastructure configuration package for enabling web terminal access to OpenCode through standardized port management and API specification.
|
||||
## parent
|
||||
index: archive/.pi-map.index.md
|
||||
map: archive/.pi-map.md
|
||||
index: ./.pi-map.index.md
|
||||
map: ./.pi-map.md
|
||||
## children
|
||||
- archive/2026-05-22-opencode-web-terminal/specs
|
||||
index: archive/2026-05-22-opencode-web-terminal/specs/.pi-map.index.md
|
||||
map: archive/2026-05-22-opencode-web-terminal/specs/.pi-map.md
|
||||
- 2026-05-22-opencode-web-terminal/specs
|
||||
index: 2026-05-22-opencode-web-terminal/specs/.pi-map.index.md
|
||||
map: 2026-05-22-opencode-web-terminal/specs/.pi-map.md
|
||||
## files
|
||||
- .openspec.yaml
|
||||
- design.md
|
||||
- proposal.md
|
||||
- tasks.md
|
||||
## links
|
||||
index: archive/2026-05-22-opencode-web-terminal/.pi-map.index.md
|
||||
map: archive/2026-05-22-opencode-web-terminal/.pi-map.md
|
||||
index: 2026-05-22-opencode-web-terminal/.pi-map.index.md
|
||||
map: 2026-05-22-opencode-web-terminal/.pi-map.md
|
||||
## workflows
|
||||
-
|
||||
## dirty
|
||||
|
||||
@@ -1,17 +1,17 @@
|
||||
# archive/2026-05-22-opencode-web-terminal
|
||||
dir: archive/2026-05-22-opencode-web-terminal
|
||||
# 2026-05-22-opencode-web-terminal
|
||||
dir: 2026-05-22-opencode-web-terminal
|
||||
|
||||
index: archive/2026-05-22-opencode-web-terminal/.pi-map.index.md
|
||||
index: 2026-05-22-opencode-web-terminal/.pi-map.index.md
|
||||
|
||||
## role
|
||||
Design and planning package for adding web terminal accessibility to OpenCode through standardized port configuration and web interface support.
|
||||
Infrastructure configuration package for enabling web terminal access to OpenCode through standardized port management and API specification.
|
||||
## files
|
||||
- .openspec.yaml | Defines an OpenAPI specification configuration file with schema type and creation date metadata
|
||||
- design.md | Design document for making OpenCode accessible via web terminal, standardizing port configuration across tool types, and adding validation for tool type ports and interfaces.
|
||||
- proposal.md | Proposes a systematic tool port configuration system with web interface support for terminal-first tools like OpenCode
|
||||
- tasks.md | Project task list tracking implementation of tool type port configuration, OpenCode web server integration, tunnel port fixes, frontend updates, database migrations, and testing for a development tools platform | dep: Alembic, Docker Compose, OpenCode, backend API, frontend UI, tunnel service
|
||||
## arch
|
||||
Specification-driven design documentation with OpenAPI configuration, structured proposal-to-implementation workflow (design → proposal → tasks), and incremental feature delivery pattern for developer tool integration.
|
||||
Specification-driven design using OpenAPI configuration, task-tracked iterative implementation, and document-based proposal system covering port validation, tunnel fixes, database migrations, and frontend integration.
|
||||
## tags
|
||||
configuration, opencode, port, tool, type, design, web, .openspec
|
||||
## symbols
|
||||
|
||||
@@ -1,25 +1,25 @@
|
||||
# archive/2026-05-22-opencode-web-terminal/specs (index)
|
||||
dir: archive/2026-05-22-opencode-web-terminal/specs
|
||||
# 2026-05-22-opencode-web-terminal/specs (index)
|
||||
dir: 2026-05-22-opencode-web-terminal/specs
|
||||
|
||||
## role
|
||||
Contains archived specification documents for the OpenCode web terminal feature from May 2026, serving as historical design documentation for the project.
|
||||
Contains test specifications and behavioral contracts for the web terminal component.
|
||||
## parent
|
||||
index: archive/2026-05-22-opencode-web-terminal/.pi-map.index.md
|
||||
map: archive/2026-05-22-opencode-web-terminal/.pi-map.md
|
||||
index: 2026-05-22-opencode-web-terminal/.pi-map.index.md
|
||||
map: 2026-05-22-opencode-web-terminal/.pi-map.md
|
||||
## children
|
||||
- archive/2026-05-22-opencode-web-terminal/specs/opencode-web-server
|
||||
index: archive/2026-05-22-opencode-web-terminal/specs/opencode-web-server/.pi-map.index.md
|
||||
map: archive/2026-05-22-opencode-web-terminal/specs/opencode-web-server/.pi-map.md
|
||||
- archive/2026-05-22-opencode-web-terminal/specs/tool-port-configuration
|
||||
index: archive/2026-05-22-opencode-web-terminal/specs/tool-port-configuration/.pi-map.index.md
|
||||
map: archive/2026-05-22-opencode-web-terminal/specs/tool-port-configuration/.pi-map.md
|
||||
- archive/2026-05-22-opencode-web-terminal/specs/tool-types
|
||||
index: archive/2026-05-22-opencode-web-terminal/specs/tool-types/.pi-map.index.md
|
||||
map: archive/2026-05-22-opencode-web-terminal/specs/tool-types/.pi-map.md
|
||||
- 2026-05-22-opencode-web-terminal/specs/opencode-web-server
|
||||
index: 2026-05-22-opencode-web-terminal/specs/opencode-web-server/.pi-map.index.md
|
||||
map: 2026-05-22-opencode-web-terminal/specs/opencode-web-server/.pi-map.md
|
||||
- 2026-05-22-opencode-web-terminal/specs/tool-port-configuration
|
||||
index: 2026-05-22-opencode-web-terminal/specs/tool-port-configuration/.pi-map.index.md
|
||||
map: 2026-05-22-opencode-web-terminal/specs/tool-port-configuration/.pi-map.md
|
||||
- 2026-05-22-opencode-web-terminal/specs/tool-types
|
||||
index: 2026-05-22-opencode-web-terminal/specs/tool-types/.pi-map.index.md
|
||||
map: 2026-05-22-opencode-web-terminal/specs/tool-types/.pi-map.md
|
||||
## files
|
||||
## links
|
||||
index: archive/2026-05-22-opencode-web-terminal/specs/.pi-map.index.md
|
||||
map: archive/2026-05-22-opencode-web-terminal/specs/.pi-map.md
|
||||
index: 2026-05-22-opencode-web-terminal/specs/.pi-map.index.md
|
||||
map: 2026-05-22-opencode-web-terminal/specs/.pi-map.md
|
||||
## workflows
|
||||
-
|
||||
## dirty
|
||||
|
||||
@@ -1,13 +1,13 @@
|
||||
# archive/2026-05-22-opencode-web-terminal/specs
|
||||
dir: archive/2026-05-22-opencode-web-terminal/specs
|
||||
# 2026-05-22-opencode-web-terminal/specs
|
||||
dir: 2026-05-22-opencode-web-terminal/specs
|
||||
|
||||
index: archive/2026-05-22-opencode-web-terminal/specs/.pi-map.index.md
|
||||
index: 2026-05-22-opencode-web-terminal/specs/.pi-map.index.md
|
||||
|
||||
## role
|
||||
Contains archived specification documents for the OpenCode web terminal feature from May 2026, serving as historical design documentation for the project.
|
||||
Contains test specifications and behavioral contracts for the web terminal component.
|
||||
## files
|
||||
## arch
|
||||
Flat directory structure storing dated specification files, following a simple archival pattern with timestamp-prefixed naming convention for version tracking and historical reference.
|
||||
Specification-driven testing pattern using formal test files to define expected behavior before implementation.
|
||||
## tags
|
||||
-
|
||||
## symbols
|
||||
|
||||
+7
-7
@@ -1,18 +1,18 @@
|
||||
# archive/2026-05-22-opencode-web-terminal/specs/opencode-web-server (index)
|
||||
dir: archive/2026-05-22-opencode-web-terminal/specs/opencode-web-server
|
||||
# 2026-05-22-opencode-web-terminal/specs/opencode-web-server (index)
|
||||
dir: 2026-05-22-opencode-web-terminal/specs/opencode-web-server
|
||||
|
||||
## role
|
||||
Defines specifications for a web server component that provides browser-based terminal access to OpenCode containers via port 3000 with tunneling and UI integration.
|
||||
Defines the specification for a web server component that provides browser-based terminal access to OpenCode containers through tunneled connections on port 3000.
|
||||
## parent
|
||||
index: archive/2026-05-22-opencode-web-terminal/specs/.pi-map.index.md
|
||||
map: archive/2026-05-22-opencode-web-terminal/specs/.pi-map.md
|
||||
index: 2026-05-22-opencode-web-terminal/specs/.pi-map.index.md
|
||||
map: 2026-05-22-opencode-web-terminal/specs/.pi-map.md
|
||||
## children
|
||||
-
|
||||
## files
|
||||
- spec.md
|
||||
## links
|
||||
index: archive/2026-05-22-opencode-web-terminal/specs/opencode-web-server/.pi-map.index.md
|
||||
map: archive/2026-05-22-opencode-web-terminal/specs/opencode-web-server/.pi-map.md
|
||||
index: 2026-05-22-opencode-web-terminal/specs/opencode-web-server/.pi-map.index.md
|
||||
map: 2026-05-22-opencode-web-terminal/specs/opencode-web-server/.pi-map.md
|
||||
## workflows
|
||||
-
|
||||
## dirty
|
||||
|
||||
+5
-5
@@ -1,14 +1,14 @@
|
||||
# archive/2026-05-22-opencode-web-terminal/specs/opencode-web-server
|
||||
dir: archive/2026-05-22-opencode-web-terminal/specs/opencode-web-server
|
||||
# 2026-05-22-opencode-web-terminal/specs/opencode-web-server
|
||||
dir: 2026-05-22-opencode-web-terminal/specs/opencode-web-server
|
||||
|
||||
index: archive/2026-05-22-opencode-web-terminal/specs/opencode-web-server/.pi-map.index.md
|
||||
index: 2026-05-22-opencode-web-terminal/specs/opencode-web-server/.pi-map.index.md
|
||||
|
||||
## role
|
||||
Defines specifications for a web server component that provides browser-based terminal access to OpenCode containers via port 3000 with tunneling and UI integration.
|
||||
Defines the specification for a web server component that provides browser-based terminal access to OpenCode containers through tunneled connections on port 3000.
|
||||
## files
|
||||
- spec.md | Specifies requirements for OpenCode containers to run a web server on port 3000 with a web terminal interface, proper tunneling, and UI integration.
|
||||
## arch
|
||||
Requirements-driven specification document using declarative constraints (port binding, tunneling protocol, UI embedding) without implementation architecture.
|
||||
Specification-driven architecture using requirements documents to define container interfaces, port binding conventions, and UI integration patterns without containing implementation code.
|
||||
## tags
|
||||
web, spec, specifies, requirements, opencode, containers, run, server
|
||||
## symbols
|
||||
|
||||
+7
-7
@@ -1,18 +1,18 @@
|
||||
# archive/2026-05-22-opencode-web-terminal/specs/tool-port-configuration (index)
|
||||
dir: archive/2026-05-22-opencode-web-terminal/specs/tool-port-configuration
|
||||
# 2026-05-22-opencode-web-terminal/specs/tool-port-configuration (index)
|
||||
dir: 2026-05-22-opencode-web-terminal/specs/tool-port-configuration
|
||||
|
||||
## role
|
||||
Defines specifications for validating tool types, managing default network ports, exposing services through Docker Compose templates, and supporting multiple network interfaces in the OpenCode web terminal project.
|
||||
Defines specifications for validating and configuring network port assignments and exposure patterns for development tools in containerized environments.
|
||||
## parent
|
||||
index: archive/2026-05-22-opencode-web-terminal/specs/.pi-map.index.md
|
||||
map: archive/2026-05-22-opencode-web-terminal/specs/.pi-map.md
|
||||
index: 2026-05-22-opencode-web-terminal/specs/.pi-map.index.md
|
||||
map: 2026-05-22-opencode-web-terminal/specs/.pi-map.md
|
||||
## children
|
||||
-
|
||||
## files
|
||||
- spec.md
|
||||
## links
|
||||
index: archive/2026-05-22-opencode-web-terminal/specs/tool-port-configuration/.pi-map.index.md
|
||||
map: archive/2026-05-22-opencode-web-terminal/specs/tool-port-configuration/.pi-map.md
|
||||
index: 2026-05-22-opencode-web-terminal/specs/tool-port-configuration/.pi-map.index.md
|
||||
map: 2026-05-22-opencode-web-terminal/specs/tool-port-configuration/.pi-map.md
|
||||
## workflows
|
||||
-
|
||||
## dirty
|
||||
|
||||
+5
-5
@@ -1,14 +1,14 @@
|
||||
# archive/2026-05-22-opencode-web-terminal/specs/tool-port-configuration
|
||||
dir: archive/2026-05-22-opencode-web-terminal/specs/tool-port-configuration
|
||||
# 2026-05-22-opencode-web-terminal/specs/tool-port-configuration
|
||||
dir: 2026-05-22-opencode-web-terminal/specs/tool-port-configuration
|
||||
|
||||
index: archive/2026-05-22-opencode-web-terminal/specs/tool-port-configuration/.pi-map.index.md
|
||||
index: 2026-05-22-opencode-web-terminal/specs/tool-port-configuration/.pi-map.index.md
|
||||
|
||||
## role
|
||||
Defines specifications for validating tool types, managing default network ports, exposing services through Docker Compose templates, and supporting multiple network interfaces in the OpenCode web terminal project.
|
||||
Defines specifications for validating and configuring network port assignments and exposure patterns for development tools in containerized environments.
|
||||
## files
|
||||
- spec.md | Defines requirements for tool type validation including default ports, compose template port exposure, and multiple interface support
|
||||
## arch
|
||||
Specification-driven architecture using markdown-based requirements documents to define validation rules, port configuration schemas, and multi-interface networking patterns before implementation.
|
||||
Specification-driven requirements documentation using markdown-based technical specs with structured requirement categories (validation rules, template configurations, multi-interface support).
|
||||
## tags
|
||||
spec, defines, requirements, tool, type, validation, including, default
|
||||
## symbols
|
||||
|
||||
+7
-7
@@ -1,18 +1,18 @@
|
||||
# archive/2026-05-22-opencode-web-terminal/specs/tool-types (index)
|
||||
dir: archive/2026-05-22-opencode-web-terminal/specs/tool-types
|
||||
# 2026-05-22-opencode-web-terminal/specs/tool-types (index)
|
||||
dir: 2026-05-22-opencode-web-terminal/specs/tool-types
|
||||
|
||||
## role
|
||||
Defines specifications for managing tool types with Docker Compose validation and built-in tool definitions in a web terminal environment.
|
||||
Defines requirements for a tool type management system that validates Docker Compose templates and manages built-in tool definitions
|
||||
## parent
|
||||
index: archive/2026-05-22-opencode-web-terminal/specs/.pi-map.index.md
|
||||
map: archive/2026-05-22-opencode-web-terminal/specs/.pi-map.md
|
||||
index: 2026-05-22-opencode-web-terminal/specs/.pi-map.index.md
|
||||
map: 2026-05-22-opencode-web-terminal/specs/.pi-map.md
|
||||
## children
|
||||
-
|
||||
## files
|
||||
- spec.md
|
||||
## links
|
||||
index: archive/2026-05-22-opencode-web-terminal/specs/tool-types/.pi-map.index.md
|
||||
map: archive/2026-05-22-opencode-web-terminal/specs/tool-types/.pi-map.md
|
||||
index: 2026-05-22-opencode-web-terminal/specs/tool-types/.pi-map.index.md
|
||||
map: 2026-05-22-opencode-web-terminal/specs/tool-types/.pi-map.md
|
||||
## workflows
|
||||
-
|
||||
## dirty
|
||||
|
||||
+5
-5
@@ -1,14 +1,14 @@
|
||||
# archive/2026-05-22-opencode-web-terminal/specs/tool-types
|
||||
dir: archive/2026-05-22-opencode-web-terminal/specs/tool-types
|
||||
# 2026-05-22-opencode-web-terminal/specs/tool-types
|
||||
dir: 2026-05-22-opencode-web-terminal/specs/tool-types
|
||||
|
||||
index: archive/2026-05-22-opencode-web-terminal/specs/tool-types/.pi-map.index.md
|
||||
index: 2026-05-22-opencode-web-terminal/specs/tool-types/.pi-map.index.md
|
||||
|
||||
## role
|
||||
Defines specifications for managing tool types with Docker Compose validation and built-in tool definitions in a web terminal environment.
|
||||
Defines requirements for a tool type management system that validates Docker Compose templates and manages built-in tool definitions
|
||||
## files
|
||||
- spec.md | Specifies requirements for a tool type management system with Docker Compose template validation and built-in tool definitions | dep: database, docker-compose, validation framework
|
||||
## arch
|
||||
Specification-driven architecture using markdown-based requirements documentation with Docker Compose template validation patterns.
|
||||
Specification-driven architecture using markdown-based requirements documentation with Docker Compose template validation patterns
|
||||
## tags
|
||||
tool, docker, compose, spec, specifies, requirements, type, management
|
||||
## symbols
|
||||
|
||||
Reference in New Issue
Block a user