# 2026-05-22-enforce-single-tool-type-with-port-config
dir: 2026-05-22-enforce-single-tool-type-with-port-config

index: 2026-05-22-enforce-single-tool-type-with-port-config/.pi-map.index.md

## role
Design and planning package for a system-wide refactoring to enforce single interface types per tool with port configuration requirements
## files
- .openspec.yaml | Defines an OpenSpec configuration file with schema type and creation date metadata
- design.md | Design document for migrating tool types from a JSON interfaces array to a single interface_type string with requires_port boolean | dep: Alembic, Pydantic, SQLAlchemy, frontend API client, database
- proposal.md | Proposes a breaking change to simplify tool types from supporting multiple interfaces to a single interface type, with conditional port configuration based on interface type.
- tasks.md | Task checklist tracking database migration, backend/frontend API updates, UI changes, and verification steps for refactoring a tool types system from multiple interfaces to single interface_type with requires_port flag | dep: Alembic, SQLAlchemy, Pydantic, TypeScript, React, pytest, npm
## arch
Specification-driven change management using OpenSpec schema definitions, phased design documents (proposal → design → tasks), and migration-based architecture with explicit backend/frontend/UI coordination
## tags
type, interface, design, tool, types, interfaces, single, port
## symbols
-
## workflows
-
## dirty
-
