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-19-file-editor
|
||||
dir: archive/2026-05-19-file-editor
|
||||
# 2026-05-19-file-editor
|
||||
dir: 2026-05-19-file-editor
|
||||
|
||||
index: archive/2026-05-19-file-editor/.pi-map.index.md
|
||||
index: 2026-05-19-file-editor/.pi-map.index.md
|
||||
|
||||
## role
|
||||
Archive directory containing historical design documents and specifications for a file editor component that was planned to replace FileViewer with editing, syntax highlighting, and git commit capabilities.
|
||||
Design and planning documentation for a next-generation file editor component with view/edit modes, syntax highlighting, and git integration
|
||||
## files
|
||||
- .openspec.yaml | Defines an OpenSpec configuration file with schema type and creation date metadata
|
||||
- design.md | Design specification for a file editor component that replaces FileViewer with view/edit modes, syntax highlighting, and git commit integration | dep: react-simple-code-editor, prismjs, existing API endpoints (GET/POST /projects/{id}/repositories/{id}/files/content)
|
||||
- proposal.md | Design proposal for adding syntax highlighting and in-browser editing capabilities to a repository file viewer with Git commit integration | dep: react-simple-code-editor, Prism.js, existing PUT /files/content API endpoint
|
||||
- tasks.md | Project task list tracking implementation phases for a file editor component with syntax highlighting, editing, and commit capabilities | dep: react-simple-code-editor, prismjs, @types/prismjs, TypeScript, ESLint, ruff, mypy
|
||||
## arch
|
||||
Documentation-driven specification package with OpenSpec configuration, design docs, proposal, and task tracking—no actual implementation code, representing a waterfall-style planning artifact from a completed or abandoned feature cycle.
|
||||
Specification-driven development using OpenSpec schema definitions, phased milestone tracking, and iterative design documentation (design doc → proposal → task breakdown)
|
||||
## tags
|
||||
editor, design, syntax, highlighting, commit, react, simple, code
|
||||
## symbols
|
||||
|
||||
Reference in New Issue
Block a user