chore: archive 15 completed OpenSpec changes
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.
This commit is contained in:
+5
-5
@@ -1,14 +1,14 @@
|
||||
# openspec/changes/archive/2026-05-22-tool-config-management/specs/tool-config-management
|
||||
dir: openspec/changes/archive/2026-05-22-tool-config-management/specs/tool-config-management
|
||||
# archive/2026-05-22-tool-config-management/specs/tool-config-management
|
||||
dir: archive/2026-05-22-tool-config-management/specs/tool-config-management
|
||||
|
||||
index: openspec/changes/archive/2026-05-22-tool-config-management/specs/tool-config-management/.pi-map.index.md
|
||||
index: archive/2026-05-22-tool-config-management/specs/tool-config-management/.pi-map.index.md
|
||||
|
||||
## role
|
||||
Defines the specification for a user-scoped tool configuration management system supporting environment and file-based configs with tool categorization and built-in OpenCode tool integration.
|
||||
Defines system requirements for managing user-scoped tool configurations with environment/file types, tool categorization, and built-in OpenCode tool support
|
||||
## files
|
||||
- spec.md | Defines system requirements for user-scoped tool configurations, environment/file config types, tool categorization with interfaces, and built-in OpenCode tool support
|
||||
## arch
|
||||
Specification-driven design using requirements documentation with hierarchical tool categorization (interfaces, built-in, custom), dual configuration storage types (environment variables and file-based), and user-scoped resource isolation.
|
||||
Specification-driven architecture using requirements documents to define configuration management patterns, tool interfaces, and extensible tool categorization system
|
||||
## tags
|
||||
tool, spec, defines, system, requirements, user, scoped, configurations
|
||||
## symbols
|
||||
|
||||
Reference in New Issue
Block a user