Developer
caadd59441
Move the following audited-and-implemented changes into openspec/changes/archive/2026-06-12-completed-changes-archive/: - backend-frontend-refactoring - config-profile-git-mounts - config-profile-includes-ui - config-profile-multi-repo-mounts - container-monitoring-notifications - git-mount-url-validation - home-path-expansion - mobile-terminal-ux - mount-specificity-ordering - notification-center - persistent-terminal-sessions - session-list-overhaul - ssh-key-mounting - terminal-fullscreen-unified-header - tool-session-progress-and-updates Also regenerated .pi-map*.md files for openspec/changes so the remaining active changes (multi-session-terminal-ux, reorganize-long-files, working-copies, workspace-first-ui) reflect the new layout.
23 lines
1.4 KiB
Markdown
23 lines
1.4 KiB
Markdown
# archive/2026-05-25-add-config-profiles
|
|
dir: archive/2026-05-25-add-config-profiles
|
|
|
|
index: archive/2026-05-25-add-config-profiles/.pi-map.index.md
|
|
|
|
## role
|
|
Archive directory preserving the historical design documentation for a config profiles feature that restructured tool instance configuration management.
|
|
## 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 with phased implementation planning (backend → frontend → integration) using OpenSpec schema definitions and markdown-based design/proposal documentation.
|
|
## tags
|
|
config, design, .openspec, document, profile, system, legacy, user
|
|
## symbols
|
|
-
|
|
## workflows
|
|
-
|
|
## dirty
|
|
-
|