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
@@ -0,0 +1,19 @@
# 2026-06-14-completed-specs-archive/user-profile (index)
dir: 2026-06-14-completed-specs-archive/user-profile
## role
Defines functional specifications for user profile retrieval, updates, and local avatar storage.
## parent
index: 2026-06-14-completed-specs-archive/.pi-map.index.md
map: 2026-06-14-completed-specs-archive/.pi-map.md
## children
-
## files
- spec.md
## links
index: 2026-06-14-completed-specs-archive/user-profile/.pi-map.index.md
map: 2026-06-14-completed-specs-archive/user-profile/.pi-map.md
## workflows
-
## dirty
-
@@ -0,0 +1,19 @@
# 2026-06-14-completed-specs-archive/user-profile
dir: 2026-06-14-completed-specs-archive/user-profile
index: 2026-06-14-completed-specs-archive/user-profile/.pi-map.index.md
## role
Defines functional specifications for user profile retrieval, updates, and local avatar storage.
## files
- spec.md | Defines functional specifications for a user profile management system including profile retrieval, updates, and local avatar storage | dep: auth-oauth, User database model, pytest, mypy, ruff, npm/typecheck, npm/lint
## arch
Specification-driven design with clear functional requirements documentation.
## tags
profile, npm, spec, defines, functional, specifications, user, management
## symbols
-
## workflows
-
## dirty
-
@@ -0,0 +1,50 @@
# User Profile Management Specification
## Purpose
Manage user profiles including personal information and avatar.
## Requirements
### Requirement: Profile Retrieval
The system SHALL allow users to view their profile.
#### Scenario: View profile
- GIVEN an authenticated user
- WHEN they access the profile page
- THEN their name, email, and avatar are displayed
### Requirement: Profile Updates
The system SHALL allow users to update their profile.
#### Scenario: Update name and email
- GIVEN an authenticated user
- WHEN they submit profile changes
- THEN the system validates the input
- AND updates the user record
### Requirement: Avatar Upload
The system SHALL support local avatar storage.
#### Scenario: Upload avatar
- GIVEN an authenticated user
- WHEN they upload an image file
- THEN the system validates the file type and size
- AND stores it locally
- AND updates the user's avatar URL
## Dependencies
- auth-oauth (authenticated users)
- Database models: User
## Quality Gates
- `pytest` must pass
- `mypy .` must pass
- `ruff check .` must pass
- `npm run typecheck` must pass
- `npm run lint` must pass