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,22 +1,22 @@
|
||||
# archive/2026-05-22-tool-workshop (index)
|
||||
dir: archive/2026-05-22-tool-workshop
|
||||
# 2026-05-22-tool-workshop (index)
|
||||
dir: 2026-05-22-tool-workshop
|
||||
|
||||
## role
|
||||
Design and planning documentation for a "Tool Workshop" feature that extends a tool management platform to support Docker-based tools with rich configuration, reusable configs, and readiness probes.
|
||||
Design and planning documentation for a "Tool Workshop" system that enables user-defined Docker-based tools with rich configuration, reusable configs, and readiness probes through a unified management interface.
|
||||
## 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-tool-workshop/specs
|
||||
index: archive/2026-05-22-tool-workshop/specs/.pi-map.index.md
|
||||
map: archive/2026-05-22-tool-workshop/specs/.pi-map.md
|
||||
- 2026-05-22-tool-workshop/specs
|
||||
index: 2026-05-22-tool-workshop/specs/.pi-map.index.md
|
||||
map: 2026-05-22-tool-workshop/specs/.pi-map.md
|
||||
## files
|
||||
- design.md
|
||||
- proposal.md
|
||||
- tasks.md
|
||||
## links
|
||||
index: archive/2026-05-22-tool-workshop/.pi-map.index.md
|
||||
map: archive/2026-05-22-tool-workshop/.pi-map.md
|
||||
index: 2026-05-22-tool-workshop/.pi-map.index.md
|
||||
map: 2026-05-22-tool-workshop/.pi-map.md
|
||||
## workflows
|
||||
-
|
||||
## dirty
|
||||
|
||||
@@ -1,16 +1,16 @@
|
||||
# archive/2026-05-22-tool-workshop
|
||||
dir: archive/2026-05-22-tool-workshop
|
||||
# 2026-05-22-tool-workshop
|
||||
dir: 2026-05-22-tool-workshop
|
||||
|
||||
index: archive/2026-05-22-tool-workshop/.pi-map.index.md
|
||||
index: 2026-05-22-tool-workshop/.pi-map.index.md
|
||||
|
||||
## role
|
||||
Design and planning documentation for a "Tool Workshop" feature that extends a tool management platform to support Docker-based tools with rich configuration, reusable configs, and readiness probes.
|
||||
Design and planning documentation for a "Tool Workshop" system that enables user-defined Docker-based tools with rich configuration, reusable configs, and readiness probes through a unified management interface.
|
||||
## files
|
||||
- design.md | Design specification for a "Tool Workshop" system that extends an existing tool management platform to support Docker Compose and Dockerfile definitions, readiness probes, reusable config file collections, rich configuration fields, and a unified management UI. | dep: Docker Compose, Docker, Python, JSONB, Cloudflare tunnels, database (implied), web framework (implied)
|
||||
- proposal.md | Proposes a comprehensive redesign of a tool system to support user-defined Docker tools, rich configuration, reusable config folders, and readiness probes through a unified "Tool Workshop" interface. | dep: Docker Compose, Dockerfiles, database migration system, frontend routing/navigation system, Docker build service
|
||||
- tasks.md | A comprehensive project task list tracking the implementation of a Docker-based tool management platform with backend API, frontend UI, and deployment phases, all marked as complete. | dep: Alembic, Pydantic, Docker, React/TypeScript, FastAPI, SQLAlchemy
|
||||
## arch
|
||||
Specification-driven design documents following a proposal-to-design-to-tasks workflow; the system architecture centers on Docker Compose/Dockerfile-based tool definitions, reusable configuration file collections, readiness probe health checks, and a unified management UI with backend API and frontend components.
|
||||
Specification-driven design documents using markdown-based technical proposals with phased implementation tracking (design spec → proposal → task breakdown), covering backend API extensions, frontend UI components, and Docker/container orchestration patterns.
|
||||
## tags
|
||||
tool, docker, design, management, workshop, system, platform, support
|
||||
## symbols
|
||||
|
||||
@@ -1,11 +1,11 @@
|
||||
# archive/2026-05-22-tool-workshop/specs (index)
|
||||
dir: archive/2026-05-22-tool-workshop/specs
|
||||
# 2026-05-22-tool-workshop/specs (index)
|
||||
dir: 2026-05-22-tool-workshop/specs
|
||||
|
||||
## role
|
||||
Defines specifications and requirements for a unified Docker-based development tool management system with configuration mounting and health checking capabilities.
|
||||
Defines technical specifications and requirements for a containerized development tool management system including configuration, lifecycle, and orchestration concerns.
|
||||
## parent
|
||||
index: archive/2026-05-22-tool-workshop/.pi-map.index.md
|
||||
map: archive/2026-05-22-tool-workshop/.pi-map.md
|
||||
index: 2026-05-22-tool-workshop/.pi-map.index.md
|
||||
map: 2026-05-22-tool-workshop/.pi-map.md
|
||||
## children
|
||||
-
|
||||
## files
|
||||
@@ -13,8 +13,8 @@ map: archive/2026-05-22-tool-workshop/.pi-map.md
|
||||
- readiness-probes.md
|
||||
- tool-workshop.md
|
||||
## links
|
||||
index: archive/2026-05-22-tool-workshop/specs/.pi-map.index.md
|
||||
map: archive/2026-05-22-tool-workshop/specs/.pi-map.md
|
||||
index: 2026-05-22-tool-workshop/specs/.pi-map.index.md
|
||||
map: 2026-05-22-tool-workshop/specs/.pi-map.md
|
||||
## workflows
|
||||
-
|
||||
## dirty
|
||||
|
||||
@@ -1,16 +1,16 @@
|
||||
# archive/2026-05-22-tool-workshop/specs
|
||||
dir: archive/2026-05-22-tool-workshop/specs
|
||||
# 2026-05-22-tool-workshop/specs
|
||||
dir: 2026-05-22-tool-workshop/specs
|
||||
|
||||
index: archive/2026-05-22-tool-workshop/specs/.pi-map.index.md
|
||||
index: 2026-05-22-tool-workshop/specs/.pi-map.index.md
|
||||
|
||||
## role
|
||||
Defines specifications and requirements for a unified Docker-based development tool management system with configuration mounting and health checking capabilities.
|
||||
Defines technical specifications and requirements for a containerized development tool management system including configuration, lifecycle, and orchestration concerns.
|
||||
## files
|
||||
- config-folders.md | Defines requirements and design for a reusable config folder system that mounts user configuration files into tool instances with project-specific override support
|
||||
- readiness-probes.md | Defines functional requirements and specifications for container readiness probes that determine when tool instances are fully initialized and marked as running. | dep: docker, pydantic/BaseModel, shell commands (curl, nc, pg_isready), JSON
|
||||
- tool-workshop.md | Defines requirements and specifications for a unified tool management system that handles Docker-based development tools through type definitions, configurations, config folders, and readiness probes. | dep: Docker Compose, Dockerfile, container runtime, design.md
|
||||
## arch
|
||||
Documentation-driven specification architecture using modular requirement documents (config folders, readiness probes, tool workshop) that compose into a complete system design through hierarchical dependency (tool-workshop.md orchestrates config-folders.md and readiness-probes.md).
|
||||
Specification-driven design with layered documentation architecture: base system spec (tool-workshop.md), and modular sub-specs (config-folders.md, readiness-probes.md) that decompose concerns into independently specified, composable components.
|
||||
## tags
|
||||
tool, config, readiness, probes, defines, requirements, folders, design
|
||||
## symbols
|
||||
|
||||
Reference in New Issue
Block a user