alex/headquarter
1
1
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

chore(project-map): regenerate .pi-map artifacts across the repo

Browse Source
This commit is contained in:
Developer
2026-06-17 11:31:24 +00:00
parent 0dd5f2317b
commit 93da9b42a2
683 changed files with 5075 additions and 4965 deletions
Download Patch File Download Diff File Expand all files Collapse all files
openspec/changes/archive/2026-05-25-add-config-profiles/.pi-map.md
+10 -10
View File
@@ -1,19 +1,19 @@
# 2026-05-25-add-config-profiles
dir: 2026-05-25-add-config-profiles
# openspec/changes/archive/2026-05-25-add-config-profiles
dir: openspec/changes/archive/2026-05-25-add-config-profiles
index: 2026-05-25-add-config-profiles/.pi-map.index.md
index: openspec/changes/archive/2026-05-25-add-config-profiles/.pi-map.index.md
## role
Design and planning package for a new config profiles feature that replaces legacy config folder mounting with reusable, composable, user-owned launch configurations for tool sessions.
Design specification package for a config profile system that replaces legacy tool config folders with user-owned, composable launch configurations for tool instances.
## files
- .openspec.yaml | Defines an OpenSpec configuration file with schema version and creation date metadata
- design.md | Design document for a config profile system that replaces legacy config folders with user-owned, composable, selectable launch configurations for tool instances. | dep: Docker Compose, tool instance start system, config folder system (legacy), database tables (profiles, profile includes, instance profile selection)
- proposal.md | Proposes a new "config profiles" feature to replace legacy config folder mounting with reusable, composable, user-owned launch configurations for tool sessions.
- tasks.md | Project task tracking document outlining a multi-phase software development plan for implementing a config profile system with backend/frontend integration and quality gates.
- .openspec.yaml | Defines an OpenSpec schema configuration file with metadata
- design.md | Design document for a config profile system that replaces legacy tool config folders with user-owned, composable, selectable launch configurations for tool instances. | dep: Docker Compose, tool instance system, project/tool type models, config folder (legacy), UTF-8 text handling, graph resolution engine
- proposal.md | Proposes a new config profile system to replace legacy config folder mounting with reusable, composable, user-owned launch configurations for tool instances.
- tasks.md | Project task tracking document for implementing a configuration profile system with backend/frontend integration, dependency resolution, and quality gates.
## arch
Document-driven design process using structured markdown specifications (design.md, proposal.md) with formal schema definition (.openspec.yaml) and phased task tracking (tasks.md) following a requirements → proposal → design → implementation planning workflow.
Markdown-based design documentation pattern with structured specification files (schema, design, proposal, tasks) using OpenSpec metadata for schema validation and a phased implementation tracking approach.
## tags
config, design, .openspec, document, profile, system, legacy, user
config, design, profile, system, tool, configuration, .openspec, document
## symbols
-
## workflows