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
This commit is contained in:
Developer
2026-06-12 20:36:31 +00:00
parent c6073fe9d2
commit 7ef8b0eb36
188 changed files with 348 additions and 361 deletions
+1 -1
View File
@@ -2,7 +2,7 @@
dir: docs/superpowers/specs
## role
Contains technical design specifications for planned system features, serving as architectural decision records and implementation blueprints for authentication and session management capabilities.
Contains design specification documents for planned system features, serving as architectural decision records for authentication and session management capabilities.
## parent
index: docs/superpowers/.pi-map.index.md
map: docs/superpowers/.pi-map.md
+2 -2
View File
@@ -4,12 +4,12 @@ dir: docs/superpowers/specs
index: docs/superpowers/specs/.pi-map.index.md
## role
Contains technical design specifications for planned system features, serving as architectural decision records and implementation blueprints for authentication and session management capabilities.
Contains design specification documents for planned system features, serving as architectural decision records for authentication and session management capabilities.
## files
- 2026-05-17-auth-oauth-design.md | Design document for implementing OAuth2/OIDC authentication with Authentik, internal JWT access tokens, and database-backed refresh token rotation. | dep: Authentik, JWKS, JWT, database/PostgreSQL, cookies, pytest, mypy, ruff
- 2026-05-24-session-branch-selection-design.md | Design document for replacing free-text branch input with a dropdown of available branches and adding the ability to create a new local branch at clone time in a session creation UI. | dep: React/TypeScript frontend, Python/FastAPI backend, Git, API client, ToolInstance database model
## arch
Markdown-based design documentation following a date-prefixed naming convention, with each spec detailing problem statements, proposed solutions, data models, API contracts, and security considerations for discrete feature increments.
Markdown-based technical design documentation following a chronological naming convention (YYYY-MM-DD-feature-name-design.md) with no executable code, using a lightweight specification format for capturing requirements, decisions, and implementation plans before development.
## tags
design, 2026, 05, branch, session, document, authentik, jwt
## symbols