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-06-14-completed-specs-archive/tool-instances/.pi-map.md
+7 -7
View File
@@ -1,16 +1,16 @@
# 2026-06-14-completed-specs-archive/tool-instances
dir: 2026-06-14-completed-specs-archive/tool-instances
# openspec/changes/archive/2026-06-14-completed-specs-archive/tool-instances
dir: openspec/changes/archive/2026-06-14-completed-specs-archive/tool-instances
index: 2026-06-14-completed-specs-archive/tool-instances/.pi-map.index.md
index: openspec/changes/archive/2026-06-14-completed-specs-archive/tool-instances/.pi-map.index.md
## role
Defines requirements for a tool instance management system handling lifecycle, networking, and operational state of deployed tool environments.
Defines technical requirements for a tool instance management system that handles container lifecycle, health monitoring, and git-based workspace provisioning.
## files
- spec.md | Define modified and added requirements for a tool instance management system including status monitoring, health checks, tunnel management, clone mode operations, and SSH key handling
- spec.md | Technical specification document defining requirements for a tool instance management system with container status tracking, health monitoring, tunnel management, and git clone/mount modes. | dep: Docker containers, HTTP API endpoints, SSH keys, git operations, tunneling service, compose files
## arch
Specification-driven requirements document using structured markdown with sections for functional requirements, status definitions, health check protocols, tunnel/clone/SSH subsystems, and explicit "do not implement" exclusions.
Specification-driven architecture with four core subsystems (container status tracking, health monitoring, tunnel management, git clone/mount modes) designed for infrastructure-as-code deployment patterns.
## tags
management, spec, define, modified, added, requirements, tool, instance
management, spec, technical, specification, document, defining, requirements, tool
## symbols
-
## workflows