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:
+19
@@ -0,0 +1,19 @@
|
||||
# openspec/changes/archive/2025-05-17-oauth-traefik-integration/specs/docker-infrastructure (index)
|
||||
dir: openspec/changes/archive/2025-05-17-oauth-traefik-integration/specs/docker-infrastructure
|
||||
|
||||
## role
|
||||
Defines Docker infrastructure requirements for OAuth-Traefik integration using behavior-driven specification examples.
|
||||
## parent
|
||||
index: openspec/changes/archive/2025-05-17-oauth-traefik-integration/specs/.pi-map.index.md
|
||||
map: openspec/changes/archive/2025-05-17-oauth-traefik-integration/specs/.pi-map.md
|
||||
## children
|
||||
-
|
||||
## files
|
||||
- spec.md
|
||||
## links
|
||||
index: openspec/changes/archive/2025-05-17-oauth-traefik-integration/specs/docker-infrastructure/.pi-map.index.md
|
||||
map: openspec/changes/archive/2025-05-17-oauth-traefik-integration/specs/docker-infrastructure/.pi-map.md
|
||||
## workflows
|
||||
-
|
||||
## dirty
|
||||
-
|
||||
+19
@@ -0,0 +1,19 @@
|
||||
# openspec/changes/archive/2025-05-17-oauth-traefik-integration/specs/docker-infrastructure
|
||||
dir: openspec/changes/archive/2025-05-17-oauth-traefik-integration/specs/docker-infrastructure
|
||||
|
||||
index: openspec/changes/archive/2025-05-17-oauth-traefik-integration/specs/docker-infrastructure/.pi-map.index.md
|
||||
|
||||
## role
|
||||
Defines Docker infrastructure requirements for OAuth-Traefik integration using behavior-driven specification examples.
|
||||
## files
|
||||
- spec.md | Defines modified requirements for Docker Compose setup and environment configuration using specification by example (Gherkin-style scenarios) | dep: Docker Compose, Traefik
|
||||
## arch
|
||||
Specification-by-example pattern with Gherkin-style scenarios for declarative infrastructure requirements, separating environment configuration concerns from implementation details.
|
||||
## tags
|
||||
spec, defines, modified, requirements, docker, compose, setup, environment
|
||||
## symbols
|
||||
-
|
||||
## workflows
|
||||
-
|
||||
## dirty
|
||||
-
|
||||
Reference in New Issue
Block a user