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

docs/features/.pi-map.md

@@ -4,7 +4,7 @@ dir: docs/features
 index: docs/features/.pi-map.index.md
 
 ## role
-User-facing documentation for features of the "Headquarter" developer platform application, covering authentication, project/repository management, git tools, web-based terminals, and workspace editing.
+User-facing documentation for features of a web-based development platform called "Headquarter" that provides project management, Git repositories, containerized development tools, and browser-based IDE capabilities.
 ## files
 - auth.md | Documents the OAuth2 authentication system using Authentik for the Headquarter application | dep: Authentik, OAuth2, session cookies
 - git-history.md | Documents a Git history visualization UI feature showing commit graphs, branch filtering, and commit details with diff viewing | dep: Git, repositories API, branch selector UI component, diff syntax highlighter
@@ -17,7 +17,7 @@ User-facing documentation for features of the "Headquarter" developer platform a
 - tool-types.md | Documents how to define, manage, and use development tool types in Headquarter using Docker Compose templates | dep: Docker Compose, YAML, git, VS Code Server, Jupyter Notebook
 - workspace.md | Documents a repository workspace file browser interface with repository/branch selection, file tree navigation, file viewing with syntax highlighting, and quick editing capabilities. | dep: Git, Repositories API, Git History, Git Repositories
 ## arch
-Flat markdown documentation structure organized by feature domain, with each file independently documenting a specific subsystem; no code or cross-references, purely descriptive end-user guides for a containerized development environment platform.
+Feature-oriented documentation structure with each markdown file independently documenting a distinct system capability; content follows a consistent pattern of overview, usage instructions, and UI element descriptions; docs cover a full-stack developer platform spanning authentication (OAuth2/Authentik), Git operations, Docker-based tooling, and in-browser terminals/editors.
 ## tags
 git, terminal, documents, functionality, headquarter, application, ssh, tool
 ## symbols