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,10 +1,10 @@
# archive/2026-05-17-project-management
dir: archive/2026-05-17-project-management
# 2026-05-17-project-management
dir: 2026-05-17-project-management
index: archive/2026-05-17-project-management/.pi-map.index.md
index: 2026-05-17-project-management/.pi-map.index.md
## role
This package contains archived design documentation and planning artifacts for a project management feature that was implemented with full-stack CRUD operations, ownership enforcement, and SSH key integration.
Defines specifications, design, and implementation tracking for a full-stack project management feature with authenticated CRUD, ownership enforcement, and SSH key integration.
## files
- .openspec.yaml | Defines an OpenAPI specification file metadata with schema type and creation date
- README.md | Defines a project management application that implements create, read, update, delete, listing, and ownership workflows across API and frontend layers
@@ -12,7 +12,7 @@ This package contains archived design documentation and planning artifacts for a
- proposal.md | Proposes a project management feature implementation covering authenticated CRUD APIs, frontend flows, SSH key integration, and cascading deletion behavior. | dep: authentication, data models, frontend foundation, apps/api/src, apps/web/src
- tasks.md | Tracks completed tasks for implementing full-stack project management features with ownership enforcement and verification checks.
## arch
Documentation-driven planning architecture using OpenAPI specification metadata, structured markdown design documents (proposal → design → tasks → README), and explicit separation of API/backend concerns from frontend integration workflows.
Documentation-driven specification pattern using OpenAPI metadata, layered design docs (proposal → design → tasks), and separation of concerns across API/backend and frontend concerns with explicit ownership-based access control.
## tags
project, frontend, management, ownership, design, tasks, defines, .openspec
## symbols