chore: track all project map and index files

Add generated .pi-map.md and .pi-map.index.md files across the repository
so the project navigation maps are shared and versioned. These artifacts
are maintained by project_map_init/patch/validate and must be kept in
sync with source edits.

Note: .cache/ remains ignored (added in previous commit).

openspec/changes/archive/2025-05-17-user-profile/.pi-map.md

@@ -0,0 +1,23 @@
+# openspec/changes/archive/2025-05-17-user-profile
+dir: openspec/changes/archive/2025-05-17-user-profile
+
+index: openspec/changes/archive/2025-05-17-user-profile/.pi-map.index.md
+
+## role
+Contains archived specification documents for a 2025 user profile feature implementation, capturing design proposals, task tracking, and documentation for an authenticated profile read/update flow with avatar upload.
+## files
+- .openspec.yaml | Defines an OpenAPI specification file metadata with schema type and creation date
+- README.md | Documents the implementation of an authenticated user profile read/update flow across API and frontend
+- design.md | Design document for implementing a user profile management feature with backend API endpoints and frontend page | dep: FastAPI, JWT authentication, cookie-based auth, static file serving, React/frontend framework
+- proposal.md | Proposes implementing authenticated user profile management with read/update endpoints, frontend page, and avatar upload functionality. | dep: apps/api/src/api/, apps/web/src/, auth-oauth, User model
+- tasks.md | Tracks implementation tasks for a user profile feature across backend API and frontend, with completion status and follow-up notes.
+## arch
+Documentation-driven specification archive using lightweight YAML metadata, markdown-based design docs (proposal → design → tasks → README progression), and OpenAPI schema conventions for cross-stack (backend API + frontend) feature planning.
+## tags
+api, user, profile, frontend, design, tasks, .openspec, implementation
+## symbols
+-
+## workflows
+-
+## dirty
+-