chore(project-map): regenerate .pi-map artifacts across the repo
This commit is contained in:
+6
-6
@@ -1,14 +1,14 @@
|
||||
# 2026-05-22-tool-config-management/specs/tool-config-management
|
||||
dir: 2026-05-22-tool-config-management/specs/tool-config-management
|
||||
# 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
|
||||
|
||||
index: 2026-05-22-tool-config-management/specs/tool-config-management/.pi-map.index.md
|
||||
index: openspec/changes/archive/2026-05-22-tool-config-management/specs/tool-config-management/.pi-map.index.md
|
||||
|
||||
## role
|
||||
Defines system requirements for user-scoped tool configurations, environment/file config types, tool categorization with interfaces, and built-in OpenCode tool support
|
||||
Defines system requirements for user-scoped tool configuration management, including configuration 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
|
||||
- spec.md | Defines system requirements for user-scoped tool configurations, config types (env/file), tool categorization/interfaces, and built-in OpenCode tool support
|
||||
## arch
|
||||
Specification-driven architecture using markdown-based requirements documentation with interface definitions for tool configuration management
|
||||
Specification-driven architecture using markdown-based requirements documents with typed configuration schemas (environment variables, file-based configs), tool interface definitions, and hierarchical tool categorization for extensible tool ecosystem integration.
|
||||
## tags
|
||||
tool, spec, defines, system, requirements, user, scoped, configurations
|
||||
## symbols
|
||||
|
||||
Reference in New Issue
Block a user