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).
1.6 KiB
1.6 KiB
openspec/changes/archive/2026-05-23-remove-built-in-tools
dir: openspec/changes/archive/2026-05-23-remove-built-in-tools
index: openspec/changes/archive/2026-05-23-remove-built-in-tools/.pi-map.index.md
role
Contains planning and design documents for a refactoring initiative to remove the special-cased "built-in" tool type classification and migrate to a unified database-driven tool type system.
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_builtinfunctionality 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
arch
Specification-driven change management using OpenSpec schema with structured documentation (design doc, proposal, task tracking) for cross-stack database migration and feature removal.
tags
tool, type, design, database, alembic, frontend, .openspec, records