c8db6ce933
- Change mobile terminal CSS to use touch-action: none and overscroll-behavior: none so the custom touch handler owns swipes - Archive completed/partial OpenSpec specs to openspec/changes/archive/2026-06-14-completed-specs-archive/ - Regenerate project maps Quality gates: npm run typecheck, npm run lint (apps/web)
1.6 KiB
1.6 KiB
2026-05-23-remove-built-in-tools
dir: 2026-05-23-remove-built-in-tools
index: 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.
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
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.
tags
tool, type, design, database, alembic, frontend, .openspec, records