Developer
070cd4d5a5
Add generated .pi-map.md and .pi-map.index.md files across the repository so the project navigation maps are shared and versioned. These artifacts are maintained by project_map_init/patch/validate and must be kept in sync with source edits. Note: .cache/ remains ignored (added in previous commit).
23 lines
1.5 KiB
Markdown
23 lines
1.5 KiB
Markdown
# openspec/changes/archive/2026-05-22-tool-config-ui-rework
|
|
dir: openspec/changes/archive/2026-05-22-tool-config-ui-rework
|
|
|
|
index: openspec/changes/archive/2026-05-22-tool-config-ui-rework/.pi-map.index.md
|
|
|
|
## role
|
|
Archive directory preserving historical design documents for a tool configuration UI rework feature from May 2026.
|
|
## files
|
|
- .openspec.yaml | Defines an OpenAPI specification configuration file with schema type and creation date metadata
|
|
- design.md | Design document for redesigning a tool configuration page with split-pane layout, new configuration fields, and improved UX | dep: PostgreSQL, JSON, Docker/container runtime (referenced but not modified)
|
|
- proposal.md | Proposes a UI/UX redesign of a tool configuration management page with backend schema changes to support additional configuration fields | dep: database, API endpoints, frontend components, migration system
|
|
- tasks.md | Project task checklist tracking implementation of container runtime configuration features across database, backend, and frontend | dep: Alembic, SQLAlchemy, Pydantic, FastAPI, React/TypeScript, JSON editor component, ruff, mypy, tsc, eslint
|
|
## arch
|
|
Document-driven specification pattern with phased design-to-implementation workflow (proposal → design → tasks → OpenAPI spec), using markdown-based design documents and YAML schema configuration for cross-stack feature coordination.
|
|
## tags
|
|
configuration, design, schema, .openspec, tool, page, fields, backend
|
|
## symbols
|
|
-
|
|
## workflows
|
|
-
|
|
## dirty
|
|
-
|