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,23 +1,23 @@
|
||||
# archive/2026-05-19-git-control (index)
|
||||
dir: archive/2026-05-19-git-control
|
||||
# 2026-05-19-git-control (index)
|
||||
dir: 2026-05-19-git-control
|
||||
|
||||
## role
|
||||
Archive of design documents and specifications for adding Git version control capabilities to a browser-based repository workspace
|
||||
Defines specifications and planning documents for implementing Git version control capabilities in a browser-based repository management interface.
|
||||
## parent
|
||||
index: archive/.pi-map.index.md
|
||||
map: archive/.pi-map.md
|
||||
index: ./.pi-map.index.md
|
||||
map: ./.pi-map.md
|
||||
## children
|
||||
- archive/2026-05-19-git-control/specs
|
||||
index: archive/2026-05-19-git-control/specs/.pi-map.index.md
|
||||
map: archive/2026-05-19-git-control/specs/.pi-map.md
|
||||
- 2026-05-19-git-control/specs
|
||||
index: 2026-05-19-git-control/specs/.pi-map.index.md
|
||||
map: 2026-05-19-git-control/specs/.pi-map.md
|
||||
## files
|
||||
- .openspec.yaml
|
||||
- design.md
|
||||
- proposal.md
|
||||
- tasks.md
|
||||
## links
|
||||
index: archive/2026-05-19-git-control/.pi-map.index.md
|
||||
map: archive/2026-05-19-git-control/.pi-map.md
|
||||
index: 2026-05-19-git-control/.pi-map.index.md
|
||||
map: 2026-05-19-git-control/.pi-map.md
|
||||
## workflows
|
||||
-
|
||||
## dirty
|
||||
|
||||
@@ -1,17 +1,17 @@
|
||||
# archive/2026-05-19-git-control
|
||||
dir: archive/2026-05-19-git-control
|
||||
# 2026-05-19-git-control
|
||||
dir: 2026-05-19-git-control
|
||||
|
||||
index: archive/2026-05-19-git-control/.pi-map.index.md
|
||||
index: 2026-05-19-git-control/.pi-map.index.md
|
||||
|
||||
## role
|
||||
Archive of design documents and specifications for adding Git version control capabilities to a browser-based repository workspace
|
||||
Defines specifications and planning documents for implementing Git version control capabilities in a browser-based repository management interface.
|
||||
## files
|
||||
- .openspec.yaml | Defines an OpenSpec configuration file with schema type and creation date metadata
|
||||
- design.md | Design specification for a Git-based repository management UI with backend API and frontend workspace components | dep: Git, React/TypeScript, REST API, file tree UI components, dialog/modal system
|
||||
- proposal.md | Proposes adding git control capabilities (branch management, commit, push/pull, merge) to a browser-based repository workspace that currently only provides read-only access | dep: git, repository workspace, file viewer, branch selector, toolbar
|
||||
- tasks.md | Project task tracking document outlining implementation phases for a Git version control feature in a full-stack application | dep: GitPython, FastAPI, React/Vue frontend, pytest, ruff, mypy
|
||||
## arch
|
||||
Document-driven design with phased implementation planning, separating concerns into backend API (REST/JSON) and frontend workspace components, using Git CLI integration over libgit2 for simplicity
|
||||
Documentation-driven specification pattern using OpenSpec schema configuration, phased task tracking, and separation of concerns between design specification (backend API + frontend workspace) and feature proposal (read-only to full read/write Git operations).
|
||||
## tags
|
||||
git, design, .openspec, repository, management, workspace, react, control
|
||||
## symbols
|
||||
|
||||
@@ -1,18 +1,18 @@
|
||||
# archive/2026-05-19-git-control/specs (index)
|
||||
dir: archive/2026-05-19-git-control/specs
|
||||
# 2026-05-19-git-control/specs (index)
|
||||
dir: 2026-05-19-git-control/specs
|
||||
|
||||
## role
|
||||
Defines specifications for a Git version control interface with REST API and frontend capabilities for branch management, commits, remote sync, and merge operations.
|
||||
Defines the API contract and UI specification for a Git version control interface that enables branch management, commits, remote sync, and merge operations.
|
||||
## parent
|
||||
index: archive/2026-05-19-git-control/.pi-map.index.md
|
||||
map: archive/2026-05-19-git-control/.pi-map.md
|
||||
index: 2026-05-19-git-control/.pi-map.index.md
|
||||
map: 2026-05-19-git-control/.pi-map.md
|
||||
## children
|
||||
-
|
||||
## files
|
||||
- spec.md
|
||||
## links
|
||||
index: archive/2026-05-19-git-control/specs/.pi-map.index.md
|
||||
map: archive/2026-05-19-git-control/specs/.pi-map.md
|
||||
index: 2026-05-19-git-control/specs/.pi-map.index.md
|
||||
map: 2026-05-19-git-control/specs/.pi-map.md
|
||||
## workflows
|
||||
-
|
||||
## dirty
|
||||
|
||||
@@ -1,14 +1,14 @@
|
||||
# archive/2026-05-19-git-control/specs
|
||||
dir: archive/2026-05-19-git-control/specs
|
||||
# 2026-05-19-git-control/specs
|
||||
dir: 2026-05-19-git-control/specs
|
||||
|
||||
index: archive/2026-05-19-git-control/specs/.pi-map.index.md
|
||||
index: 2026-05-19-git-control/specs/.pi-map.index.md
|
||||
|
||||
## role
|
||||
Defines specifications for a Git version control interface with REST API and frontend capabilities for branch management, commits, remote sync, and merge operations.
|
||||
Defines the API contract and UI specification for a Git version control interface that enables branch management, commits, remote sync, and merge operations.
|
||||
## files
|
||||
- spec.md | Defines a REST API and frontend specification for a Git version control interface enabling branch management, commits, remote sync, and merge operations
|
||||
## arch
|
||||
Specification-driven design using Markdown-based API documentation with clear separation between backend REST endpoints and frontend UI requirements.
|
||||
Specification-driven design using REST API documentation paired with frontend requirements, establishing clear interfaces between backend services and client implementation.
|
||||
## tags
|
||||
spec, defines, rest, api, frontend, specification, git, version
|
||||
## symbols
|
||||
|
||||
Reference in New Issue
Block a user