Developer
070cd4d5a5
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).
23 lines
1.4 KiB
Markdown
23 lines
1.4 KiB
Markdown
# openspec/changes/archive/2026-05-25-add-config-profiles
|
|
dir: openspec/changes/archive/2026-05-25-add-config-profiles
|
|
|
|
index: openspec/changes/archive/2026-05-25-add-config-profiles/.pi-map.index.md
|
|
|
|
## role
|
|
Design and planning package for a new config profile system to replace legacy configuration management with user-owned, composable launch configurations.
|
|
## 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.
|
|
## arch
|
|
Specification-driven design using OpenSpec schema with phased implementation planning (design doc → proposal → task tracking) for a backend/frontend integrated feature rollout.
|
|
## tags
|
|
config, design, .openspec, document, profile, system, legacy, user
|
|
## symbols
|
|
-
|
|
## workflows
|
|
-
|
|
## dirty
|
|
-
|