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-23-remove-built-in-tools/.pi-map.md
+9 -9
View File
@@ -1,19 +1,19 @@
# 2026-05-23-remove-built-in-tools
dir: 2026-05-23-remove-built-in-tools
# openspec/changes/archive/2026-05-23-remove-built-in-tools
dir: openspec/changes/archive/2026-05-23-remove-built-in-tools
index: 2026-05-23-remove-built-in-tools/.pi-map.index.md
index: openspec/changes/archive/2026-05-23-remove-built-in-tools/.pi-map.index.md
## role
This package contains design documents and planning artifacts for a refactoring initiative to eliminate special-case handling of built-in tool types by converting them to regular database records.
Contains archived specification documents for a completed refactoring that removed the privileged "built-in" tool type classification to make all tool types user-editable database records.
## files
- .openspec.yaml | Defines an OpenSpec configuration file with schema type and creation date metadata
- design.md | Design document for removing built-in tool type special handling by migrating seeded data to regular database records via Alembic migration | dep: Alembic, SQLAlchemy/model layer, main.py startup logic, API layer, frontend
- proposal.md | Proposes a refactoring to eliminate the privileged "built-in" tool type classification and make all tool types equal, first-class database records | dep: ToolType model, main.py, tool_types.py API, database migration system, frontend
- tasks.md | Task checklist tracking the removal of `is_builtin` functionality from tool types across a full-stack application (database, backend, frontend, and testing) | dep: Alembic, SQLAlchemy, Pydantic, FastAPI, PostgreSQL, pytest, ruff, mypy, React/frontend build system
- design.md | Design document for refactoring built-in tool types from hardcoded/seeded entities to regular editable database records | dep: Alembic, ToolType model, main.py, API layer, frontend
- proposal.md | Proposes a system refactoring to eliminate the privileged "built-in" tool type classification, making all tool types equally manageable by users
- tasks.md | A completed task checklist documenting the removal of the `is_builtin` field/column from tool types across a full-stack application (database, backend, frontend, and testing) | dep: Alembic, PostgreSQL, Pydantic, FastAPI, React/TypeScript, pytest, ruff, mypy
## arch
Documentation-driven change management using a structured proposal pipeline (proposal → design → tasks → OpenSpec config) to coordinate a full-stack migration involving database schema changes (Alembic), backend API modifications, frontend updates, and test suite adjustments.
Documentation-driven change management using OpenSpec schema with structured design/proposal/task artifacts tracking a full-stack migration (database → backend → frontend → testing) from hardcoded seeded entities to regular editable records.
## tags
tool, type, design, database, alembic, frontend, .openspec, records
tool, design, types, type, .openspec, refactoring, database, alembic
## symbols
-
## workflows