chore(project-map): regenerate .pi-map artifacts across the repo
This commit is contained in:
Developer
@@ -1,22 +1,22 @@
|
||||
# 2026-05-22-tool-workshop (index)
|
||||
dir: 2026-05-22-tool-workshop
|
||||
# openspec/changes/archive/2026-05-22-tool-workshop (index)
|
||||
dir: openspec/changes/archive/2026-05-22-tool-workshop
|
||||
|
||||
## role
|
||||
Design and planning documentation for a "Tool Workshop" system that enables user-defined Docker-based tools with rich configuration, reusable configs, and readiness probes through a unified management interface.
|
||||
Design documentation package for a "Tool Workshop" system that enables flexible, Docker-based tool definitions with reusable configurations and readiness probes.
|
||||
## parent
|
||||
index: ./.pi-map.index.md
|
||||
map: ./.pi-map.md
|
||||
index: openspec/changes/archive/.pi-map.index.md
|
||||
map: openspec/changes/archive/.pi-map.md
|
||||
## children
|
||||
- 2026-05-22-tool-workshop/specs
|
||||
index: 2026-05-22-tool-workshop/specs/.pi-map.index.md
|
||||
map: 2026-05-22-tool-workshop/specs/.pi-map.md
|
||||
- openspec/changes/archive/2026-05-22-tool-workshop/specs
|
||||
index: openspec/changes/archive/2026-05-22-tool-workshop/specs/.pi-map.index.md
|
||||
map: openspec/changes/archive/2026-05-22-tool-workshop/specs/.pi-map.md
|
||||
## files
|
||||
- design.md
|
||||
- proposal.md
|
||||
- tasks.md
|
||||
## links
|
||||
index: 2026-05-22-tool-workshop/.pi-map.index.md
|
||||
map: 2026-05-22-tool-workshop/.pi-map.md
|
||||
index: openspec/changes/archive/2026-05-22-tool-workshop/.pi-map.index.md
|
||||
map: openspec/changes/archive/2026-05-22-tool-workshop/.pi-map.md
|
||||
## workflows
|
||||
-
|
||||
## dirty
|
||||
|
||||
@@ -1,18 +1,18 @@
|
||||
# 2026-05-22-tool-workshop
|
||||
dir: 2026-05-22-tool-workshop
|
||||
# openspec/changes/archive/2026-05-22-tool-workshop
|
||||
dir: openspec/changes/archive/2026-05-22-tool-workshop
|
||||
|
||||
index: 2026-05-22-tool-workshop/.pi-map.index.md
|
||||
index: openspec/changes/archive/2026-05-22-tool-workshop/.pi-map.index.md
|
||||
|
||||
## role
|
||||
Design and planning documentation for a "Tool Workshop" system that enables user-defined Docker-based tools with rich configuration, reusable configs, and readiness probes through a unified management interface.
|
||||
Design documentation package for a "Tool Workshop" system that enables flexible, Docker-based tool definitions with reusable configurations and readiness probes.
|
||||
## files
|
||||
- design.md | Design specification for a "Tool Workshop" system that extends an existing tool management platform to support Docker Compose and Dockerfile definitions, readiness probes, reusable config file collections, rich configuration fields, and a unified management UI. | dep: Docker Compose, Docker, Python, JSONB, Cloudflare tunnels, database (implied), web framework (implied)
|
||||
- proposal.md | Proposes a comprehensive redesign of a tool system to support user-defined Docker tools, rich configuration, reusable config folders, and readiness probes through a unified "Tool Workshop" interface. | dep: Docker Compose, Dockerfiles, database migration system, frontend routing/navigation system, Docker build service
|
||||
- tasks.md | A comprehensive project task list tracking the implementation of a Docker-based tool management platform with backend API, frontend UI, and deployment phases, all marked as complete. | dep: Alembic, Pydantic, Docker, React/TypeScript, FastAPI, SQLAlchemy
|
||||
- design.md | Design document for a "Tool Workshop" system that extends an existing tool management platform to support richer Docker Compose/Dockerfile-based tool definitions, reusable config file collections, readiness probes, and a unified management UI. | dep: Docker Compose, Docker, Cloudflare tunnels, JSONB storage, Python (dataclasses/models), backend API framework, database with UUID support
|
||||
- proposal.md | Design proposal for transforming a rigid hardcoded tool system into a flexible user-defined "tool workshop" with Docker Compose/Dockerfile support, rich configuration, reusable config folders, and readiness probes. | dep: Docker Compose, Dockerfiles, database migration system, frontend routing/navigation, Docker build service
|
||||
- tasks.md | Project task tracking document outlining phased backend/frontend development for a tool management platform with Docker integration, config folders, and readiness probes
|
||||
## arch
|
||||
Specification-driven design documents using markdown-based technical proposals with phased implementation tracking (design spec → proposal → task breakdown), covering backend API extensions, frontend UI components, and Docker/container orchestration patterns.
|
||||
Specification-driven architecture with phased implementation (backend → frontend), transitioning from hardcoded to user-defined tools via Docker Compose/Dockerfile abstractions, config folder collections, and probe-based health checking.
|
||||
## tags
|
||||
tool, docker, design, management, workshop, system, platform, support
|
||||
tool, design, docker, management, config, readiness, probes, proposal
|
||||
## symbols
|
||||
-
|
||||
## workflows
|
||||
|
||||
@@ -1,11 +1,11 @@
|
||||
# 2026-05-22-tool-workshop/specs (index)
|
||||
dir: 2026-05-22-tool-workshop/specs
|
||||
# openspec/changes/archive/2026-05-22-tool-workshop/specs (index)
|
||||
dir: openspec/changes/archive/2026-05-22-tool-workshop/specs
|
||||
|
||||
## 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.
|
||||
## parent
|
||||
index: 2026-05-22-tool-workshop/.pi-map.index.md
|
||||
map: 2026-05-22-tool-workshop/.pi-map.md
|
||||
index: openspec/changes/archive/2026-05-22-tool-workshop/.pi-map.index.md
|
||||
map: openspec/changes/archive/2026-05-22-tool-workshop/.pi-map.md
|
||||
## children
|
||||
-
|
||||
## files
|
||||
@@ -13,8 +13,8 @@ map: 2026-05-22-tool-workshop/.pi-map.md
|
||||
- readiness-probes.md
|
||||
- tool-workshop.md
|
||||
## links
|
||||
index: 2026-05-22-tool-workshop/specs/.pi-map.index.md
|
||||
map: 2026-05-22-tool-workshop/specs/.pi-map.md
|
||||
index: openspec/changes/archive/2026-05-22-tool-workshop/specs/.pi-map.index.md
|
||||
map: openspec/changes/archive/2026-05-22-tool-workshop/specs/.pi-map.md
|
||||
## workflows
|
||||
-
|
||||
## dirty
|
||||
|
||||
@@ -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
|
||||
|
||||
Reference in New Issue
Block a user