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-05-22-tool-workshop/specs/.pi-map.md
+9 -9
View File
@@ -1,18 +1,18 @@
# 2026-05-22-tool-workshop/specs
dir: 2026-05-22-tool-workshop/specs
# openspec/changes/archive/2026-05-22-tool-workshop/specs
dir: openspec/changes/archive/2026-05-22-tool-workshop/specs
index: 2026-05-22-tool-workshop/specs/.pi-map.index.md
index: openspec/changes/archive/2026-05-22-tool-workshop/specs/.pi-map.index.md
## role
Defines technical specifications and requirements for a containerized development tool management system including configuration, lifecycle, and orchestration concerns.
Defines core specifications for a containerized development tool management system enabling reproducible, project-configured tool instances with lifecycle health verification.
## files
- config-folders.md | Defines requirements and design for a reusable config folder system that mounts user configuration files into tool instances with project-specific override support
- readiness-probes.md | Defines functional requirements and specifications for container readiness probes that determine when tool instances are fully initialized and marked as running. | dep: docker, pydantic/BaseModel, shell commands (curl, nc, pg_isready), JSON
- tool-workshop.md | Defines requirements and specifications for a unified tool management system that handles Docker-based development tools through type definitions, configurations, config folders, and readiness probes. | dep: Docker Compose, Dockerfile, container runtime, design.md
- config-folders.md | Defines requirements and design for a reusable configuration folder system that mounts user dotfiles and settings into containerized tool instances with project-specific override support
- readiness-probes.md | Defines functional requirements and behavior for container readiness probes that verify tool instances are fully initialized before being marked as "running" | dep: docker, pydantic, BaseModel, json
- tool-workshop.md | Defines requirements and specifications for a unified Tool Workshop system that manages Docker-based development tools through type definitions, configurations, folders, and instance lifecycle management with readiness probes. | dep: Docker, Docker Compose, design.md (external reference)
## arch
Specification-driven design with layered documentation architecture: base system spec (tool-workshop.md), and modular sub-specs (config-folders.md, readiness-probes.md) that decompose concerns into independently specified, composable components.
Specification-driven architecture using layered configuration (base/user/project), Docker container orchestration with readiness probe health checks, and declarative type-based tool definitions with mountable config folder overlays.
## tags
tool, config, readiness, probes, defines, requirements, folders, design
tool, readiness, probes, defines, requirements, folders, docker, workshop
## symbols
-
## workflows