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-user-config-management
|
||||
dir: archive/2025-05-18-user-config-management
|
||||
# 2025-05-18-user-config-management
|
||||
dir: 2025-05-18-user-config-management
|
||||
|
||||
index: archive/2025-05-18-user-config-management/.pi-map.index.md
|
||||
index: 2025-05-18-user-config-management/.pi-map.index.md
|
||||
|
||||
## role
|
||||
Archive directory containing historical design documents and planning artifacts for a user configuration management feature that was proposed but not yet implemented.
|
||||
Design and planning package for a JSONB-backed user configuration management feature with API and UI components.
|
||||
## files
|
||||
- .openspec.yaml | Defines an OpenSpec configuration file with schema type and creation date metadata
|
||||
- design.md | Design document for a simple key-value user configuration system using PostgreSQL JSONB | dep: PostgreSQL, JSONB
|
||||
- proposal.md | Proposes a feature to add persistent user preference storage and management through a JSONB-backed config system with API endpoints and frontend settings UI. | dep: database, API, frontend, UserConfig model, AppShell
|
||||
- tasks.md | Project task tracking document for implementing a user settings/config feature with backend API, frontend UI, and verification steps | dep: SQLAlchemy, Alembic, FastAPI/HTTP endpoints, React/frontend router, Docker Compose, ruff, mypy, pytest, TypeScript tooling
|
||||
## arch
|
||||
Document-driven design with OpenSpec schema definitions, Markdown-based design/proposal/task tracking, and a planned JSONB-backed key-value storage architecture with REST API and frontend UI components.
|
||||
Specification-driven development using OpenSpec schema definitions, paired with markdown-based design documents (design.md, proposal.md, tasks.md) following a proposal → design → task breakdown workflow pattern.
|
||||
## tags
|
||||
design, user, jsonb, api, frontend, configuration, .openspec, document
|
||||
## symbols
|
||||
|
||||
Reference in New Issue
Block a user