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-25-add-config-profiles
dir: archive/2026-05-25-add-config-profiles
# 2026-05-25-add-config-profiles
dir: 2026-05-25-add-config-profiles
index: archive/2026-05-25-add-config-profiles/.pi-map.index.md
index: 2026-05-25-add-config-profiles/.pi-map.index.md
## role
Archive directory preserving the historical design documentation for a config profiles feature that restructured tool instance configuration management.
Design and planning package for a new config profiles feature that replaces legacy config folder mounting with reusable, composable, user-owned launch configurations for tool sessions.
## files
- .openspec.yaml | Defines an OpenSpec configuration file with schema version and creation date metadata
- design.md | Design document for a config profile system that replaces legacy config folders with user-owned, composable, selectable launch configurations for tool instances. | dep: Docker Compose, tool instance start system, config folder system (legacy), database tables (profiles, profile includes, instance profile selection)
- proposal.md | Proposes a new "config profiles" feature to replace legacy config folder mounting with reusable, composable, user-owned launch configurations for tool sessions.
- tasks.md | Project task tracking document outlining a multi-phase software development plan for implementing a config profile system with backend/frontend integration and quality gates.
## arch
Specification-driven design with phased implementation planning (backend → frontend → integration) using OpenSpec schema definitions and markdown-based design/proposal documentation.
Document-driven design process using structured markdown specifications (design.md, proposal.md) with formal schema definition (.openspec.yaml) and phased task tracking (tasks.md) following a requirements → proposal → design → implementation planning workflow.
## tags
config, design, .openspec, document, profile, system, legacy, user
## symbols