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:
@@ -0,0 +1,19 @@
|
||||
# openspec/changes/archive/2026-05-22-sessions-hub/specs (index)
|
||||
dir: openspec/changes/archive/2026-05-22-sessions-hub/specs
|
||||
|
||||
## role
|
||||
Defines technical specifications for a Sessions Hub feature that manages user sessions in a web application.
|
||||
## parent
|
||||
index: openspec/changes/archive/2026-05-22-sessions-hub/.pi-map.index.md
|
||||
map: openspec/changes/archive/2026-05-22-sessions-hub/.pi-map.md
|
||||
## children
|
||||
-
|
||||
## files
|
||||
- spec.md
|
||||
## links
|
||||
index: openspec/changes/archive/2026-05-22-sessions-hub/specs/.pi-map.index.md
|
||||
map: openspec/changes/archive/2026-05-22-sessions-hub/specs/.pi-map.md
|
||||
## workflows
|
||||
-
|
||||
## dirty
|
||||
-
|
||||
@@ -0,0 +1,19 @@
|
||||
# openspec/changes/archive/2026-05-22-sessions-hub/specs
|
||||
dir: openspec/changes/archive/2026-05-22-sessions-hub/specs
|
||||
|
||||
index: openspec/changes/archive/2026-05-22-sessions-hub/specs/.pi-map.index.md
|
||||
|
||||
## role
|
||||
Defines technical specifications for a Sessions Hub feature that manages user sessions in a web application.
|
||||
## files
|
||||
- spec.md | Defines technical specifications for a "Sessions Hub" feature including requirements, API endpoints, UI layouts, state management, and quality gates for managing user sessions in a web application. | dep: REST API, TypeScript, React/frontend framework (implied by UI specs and quality gates), polling-based state management, Pydantic/BaseModel
|
||||
## arch
|
||||
Specification-driven design with structured requirements, API contracts, UI wireframes, state management patterns, and defined quality gates for implementation validation.
|
||||
## tags
|
||||
sessions, spec, defines, technical, specifications, hub, feature, including
|
||||
## symbols
|
||||
-
|
||||
## workflows
|
||||
-
|
||||
## dirty
|
||||
-
|
||||
Reference in New Issue
Block a user