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).
This commit is contained in:
Developer
2026-06-12 13:46:23 +00:00
parent 44ef62271e
commit 070cd4d5a5
642 changed files with 14785 additions and 0 deletions
@@ -0,0 +1,19 @@
# openspec/changes/archive/2026-05-17-frontend-foundation/specs/frontend-foundation (index)
dir: openspec/changes/archive/2026-05-17-frontend-foundation/specs/frontend-foundation
## role
Defines foundational frontend technical specifications for a React 18+ TypeScript web application including routing, authentication, layout, and HTTP client configuration.
## parent
index: openspec/changes/archive/2026-05-17-frontend-foundation/specs/.pi-map.index.md
map: openspec/changes/archive/2026-05-17-frontend-foundation/specs/.pi-map.md
## children
-
## files
- spec.md
## links
index: openspec/changes/archive/2026-05-17-frontend-foundation/specs/frontend-foundation/.pi-map.index.md
map: openspec/changes/archive/2026-05-17-frontend-foundation/specs/frontend-foundation/.pi-map.md
## workflows
-
## dirty
-
@@ -0,0 +1,19 @@
# openspec/changes/archive/2026-05-17-frontend-foundation/specs/frontend-foundation
dir: openspec/changes/archive/2026-05-17-frontend-foundation/specs/frontend-foundation
index: openspec/changes/archive/2026-05-17-frontend-foundation/specs/frontend-foundation/.pi-map.index.md
## role
Defines foundational frontend technical specifications for a React 18+ TypeScript web application including routing, authentication, layout, and HTTP client configuration.
## files
- spec.md | This file specifies frontend requirements for a React 18+ TypeScript web application with routing, authentication, layout, and HTTP client configuration. | dep: React 18+, TypeScript 5+, Vite, React Router, Axios/fetch
## arch
Specification-driven architecture using markdown-based requirements documentation with modular concerns separation (routing, auth, layout, HTTP) for a standards-compliant SPA foundation.
## tags
spec, specifies, frontend, requirements, react, typescript, web, application
## symbols
-
## workflows
-
## dirty
-