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/2025-05-18-git-repo-management
|
||||
dir: archive/2025-05-18-git-repo-management
|
||||
# 2025-05-18-git-repo-management
|
||||
dir: 2025-05-18-git-repo-management
|
||||
|
||||
index: archive/2025-05-18-git-repo-management/.pi-map.index.md
|
||||
index: 2025-05-18-git-repo-management/.pi-map.index.md
|
||||
|
||||
## role
|
||||
Proposes and designs a git repository management feature for projects, including bare repo creation, listing, cloning, and deletion across backend and frontend.
|
||||
This package contains design and planning documents for implementing a git repository management feature that enables creating, listing, cloning, and deleting bare git repositories within projects.
|
||||
## files
|
||||
- .openspec.yaml | Defines an OpenSpec configuration file with schema type and creation date metadata
|
||||
- design.md | Design document specifying a bare git repository management system for projects with create/list/clone/delete operations | dep: git, filesystem, database, API, Dockerfile
|
||||
- proposal.md | Proposes a feature to add git repository creation, cloning, and management capabilities within existing projects | dep: project-management, git, backend API, frontend UI, disk storage
|
||||
- tasks.md | Project task checklist tracking implementation of a Git repository management feature across backend API, frontend UI, and project integration with verification steps.
|
||||
## arch
|
||||
Specification-driven development using OpenSpec schema configuration, phased task tracking with verification gates, and layered documentation (proposal → design → implementation tasks).
|
||||
Documentation-driven specification pattern using layered design docs (proposal → design → tasks → API spec) to formally define requirements before implementation, with clear separation between backend API, frontend UI, and project integration concerns.
|
||||
## tags
|
||||
git, management, design, repository, project, creation, .openspec, projects
|
||||
## symbols
|
||||
|
||||
Reference in New Issue
Block a user