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:
@@ -1,17 +1,17 @@
|
||||
# archive/2026-05-22-tool-config-management
|
||||
dir: archive/2026-05-22-tool-config-management
|
||||
# 2026-05-22-tool-config-management
|
||||
dir: 2026-05-22-tool-config-management
|
||||
|
||||
index: archive/2026-05-22-tool-config-management/.pi-map.index.md
|
||||
index: 2026-05-22-tool-config-management/.pi-map.index.md
|
||||
|
||||
## role
|
||||
Designs and tracks implementation of a per-user/per-project tool configuration management system with environment variables and file-based configs for containerized development tools.
|
||||
Designs and tracks implementation of a flexible tool configuration management system for containerized development tools with user-global and project-scoped environment variables and file-based configurations.
|
||||
## files
|
||||
- .openspec.yaml | Defines an OpenAPI specification configuration file with schema type and creation date metadata
|
||||
- design.md | Design document for implementing a flexible tool configuration system with user-global and project-scoped env vars and file-based configs for containerized tools
|
||||
- proposal.md | Proposes a feature to add per-user/per-project tool configuration management with categorization and container mounting for a development tools platform. | dep: database, container-runtime, API, frontend
|
||||
- tasks.md | Project task checklist tracking implementation of tool configuration system with database models, backend APIs, frontend UI, and OpenCode integration
|
||||
## arch
|
||||
Documentation-driven design using markdown specs (design.md, proposal.md) with task tracking (tasks.md) and OpenAPI schema configuration (.openspec.yaml), following a phased implementation approach across database, backend API, frontend UI, and external integration layers.
|
||||
Specification-driven development using OpenAPI standards, phased implementation tracking (database → backend → frontend → IDE integration), and hierarchical configuration scoping (user-global vs project-specific) with container mount integration.
|
||||
## tags
|
||||
configuration, design, tool, project, .openspec, system, user, tools
|
||||
## symbols
|
||||
|
||||
Reference in New Issue
Block a user