alex/headquarter
1
1
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

fix: disable native touch panning on mobile terminal and archive specs

Browse Source 
- 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
Download Patch File Download Diff File Expand all files Collapse all files
openspec/changes/archive/2026-06-12-completed-changes-archive/tool-config-mount-cleanup/.pi-map.index.md
+7 -20
View File
@@ -1,24 +1,11 @@
# . (index)
dir: .
## Project Map Protocol
1. Read this protocol and the root `.pi-map.index.md` first.
2. Use `index:` / `map:` references to open relevant directory indexes and maps.
3. Load indexes before rich maps during task-start navigation.
4. Read the local rich map and actual source before editing.
5. Treat non-empty `## dirty` sections in either artifact as stale.
6. If source and generated artifacts disagree, trust source.
7. If map and index disagree, trust neither blindly; verify from source and regenerate the pair.
8. After editing source, run `project_map_patch` for each changed file.
9. Before broad architectural claims or final handoff, run `project_map_validate` when freshness matters.
Trust boundary: index routes, map orients, source decides.
# 2026-06-12-completed-changes-archive/tool-config-mount-cleanup (index)
dir: 2026-06-12-completed-changes-archive/tool-config-mount-cleanup
## role
Package containing completed specification, proposal, and task tracking for a tool configuration mount cleanup feature that separates built-in tool definitions from user-specific configuration.
Completed change archive documenting the removal of configuration/state mounts from built-in tool definitions to enable config-profile-based user-specific configuration.
## parent
-
index: 2026-06-12-completed-changes-archive/.pi-map.index.md
map: 2026-06-12-completed-changes-archive/.pi-map.md
## children
-
## files
@@ -26,8 +13,8 @@ Package containing completed specification, proposal, and task tracking for a to
- proposal.md
- tasks.md
## links
index: ./.pi-map.index.md
map: ./.pi-map.md
index: 2026-06-12-completed-changes-archive/tool-config-mount-cleanup/.pi-map.index.md
map: 2026-06-12-completed-changes-archive/tool-config-mount-cleanup/.pi-map.md
## workflows
-
## dirty
openspec/changes/archive/2026-06-12-completed-changes-archive/tool-config-mount-cleanup/.pi-map.md
+5 -19
View File
@@ -1,30 +1,16 @@
# .
dir: .
# 2026-06-12-completed-changes-archive/tool-config-mount-cleanup
dir: 2026-06-12-completed-changes-archive/tool-config-mount-cleanup
index: ./.pi-map.index.md
## Project Map Protocol
1. Read this protocol and the root `.pi-map.index.md` first.
2. Use `index:` / `map:` references to open relevant directory indexes and maps.
3. Load indexes before rich maps during task-start navigation.
4. Read the local rich map and actual source before editing.
5. Treat non-empty `## dirty` sections in either artifact as stale.
6. If source and generated artifacts disagree, trust source.
7. If map and index disagree, trust neither blindly; verify from source and regenerate the pair.
8. After editing source, run `project_map_patch` for each changed file.
9. Before broad architectural claims or final handoff, run `project_map_validate` when freshness matters.
Trust boundary: index routes, map orients, source decides.
index: 2026-06-12-completed-changes-archive/tool-config-mount-cleanup/.pi-map.index.md
## role
Package containing completed specification, proposal, and task tracking for a tool configuration mount cleanup feature that separates built-in tool definitions from user-specific configuration.
Completed change archive documenting the removal of configuration/state mounts from built-in tool definitions to enable config-profile-based user-specific configuration.
## files
- .openspec.yaml | Defines a completed OpenSpec configuration for a tool named "tool-config-mount-cleanup"
- proposal.md | Proposes removing configuration and state mounts from built-in tool definitions to separate tool setup from user-specific configuration handled by config profiles.
- tasks.md | This is a completed task checklist for modifying built-in tool configurations and database migrations in a codebase. | dep: alembic, pytest, opencode, pi-agent
## arch
Documentation-driven change management with OpenSpec configuration, markdown-based proposal/justification, and structured task checklist for tracking implementation of a configuration separation pattern.
Specification-driven migration pattern using OpenSpec for declarative tool configuration, with separation of concerns between built-in tool setup and user-configurable profiles, plus database migration coordination.
## tags
tool, configuration, completed, config, .openspec, proposal, tasks, defines
## symbols