chore: patch project maps after stale backend test cleanup

Regenerate .pi-map*.md artifacts for source changes in:
- apps/api/src/api/tool/tool_types_validation.py
- apps/api/src/schemas/tool/tool_type.py
- apps/api/tests/integration/test_tool_types_api_extended.py
- and all affected test files from backend-frontend refactoring cleanup

apps/api/src/schemas/user/.pi-map.index.md

@@ -2,7 +2,7 @@
 dir: apps/api/src/schemas/user
 
 ## role
-Provides centralized Pydantic data validation schemas for user-related API requests and responses.
+Provides Pydantic data validation schemas for user-related API requests and responses.
 ## parent
 index: apps/api/src/schemas/.pi-map.index.md
 map: apps/api/src/schemas/.pi-map.md

apps/api/src/schemas/user/.pi-map.md

@@ -4,13 +4,13 @@ dir: apps/api/src/schemas/user
 index: apps/api/src/schemas/user/.pi-map.index.md
 
 ## role
-Provides centralized Pydantic data validation schemas for user-related API requests and responses.
+Provides Pydantic data validation schemas for user-related API requests and responses.
 ## files
 - __init__.py | Re-exports user-related Pydantic schemas from submodules to provide a unified public API for the user schemas package. | dep: src.schemas.user.user, src.schemas.user.user_config
 - user.py | Defines Pydantic response and update schemas for user profile data | exp: class:UserProfileResponse, class:UserProfileUpdate | dep: uuid, pydantic
 - user_config.py | Defines Pydantic models for user configuration data transfer objects (response and update schemas). | exp: class:UserConfigResponse, class:UserConfigUpdate | dep: pydantic
 ## arch
-Modular package pattern with submodule separation of concerns (user profile vs. user config) and unified public API via `__init__.py` re-exports.
+Modular schema organization with submodule separation of concerns and unified package-level re-exports for clean imports.
 ## tags
 user, schemas, response, update, config, pydantic, profile, src
 ## symbols