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
@@ -2,7 +2,7 @@
|
||||
dir: docs/superpowers
|
||||
|
||||
## role
|
||||
Documentation directory for special capabilities or advanced features of the project.
|
||||
Documentation directory for specialized or advanced capabilities/features of the project.
|
||||
## parent
|
||||
index: docs/.pi-map.index.md
|
||||
map: docs/.pi-map.md
|
||||
|
||||
@@ -4,10 +4,10 @@ dir: docs/superpowers
|
||||
index: docs/superpowers/.pi-map.index.md
|
||||
|
||||
## role
|
||||
Documentation directory for special capabilities or advanced features of the project.
|
||||
Documentation directory for specialized or advanced capabilities/features of the project.
|
||||
## files
|
||||
## arch
|
||||
N/A (empty directory - no files to analyze)
|
||||
Static documentation storage with no executable code architecture; likely contains markdown or text files describing enhanced functionality.
|
||||
## tags
|
||||
-
|
||||
## symbols
|
||||
|
||||
@@ -2,7 +2,7 @@
|
||||
dir: docs/superpowers/plans
|
||||
|
||||
## role
|
||||
Contains dated implementation planning documents that specify step-by-step technical approaches for major system features and infrastructure setup.
|
||||
Contains implementation planning documents for core infrastructure, authentication, database modeling, and UI feature development.
|
||||
## parent
|
||||
index: docs/superpowers/.pi-map.index.md
|
||||
map: docs/superpowers/.pi-map.md
|
||||
|
||||
@@ -4,14 +4,14 @@ dir: docs/superpowers/plans
|
||||
index: docs/superpowers/plans/.pi-map.index.md
|
||||
|
||||
## role
|
||||
Contains dated implementation planning documents that specify step-by-step technical approaches for major system features and infrastructure setup.
|
||||
Contains implementation planning documents for core infrastructure, authentication, database modeling, and UI feature development.
|
||||
## files
|
||||
- 2024-05-16-docker-infrastructure.md | Defines a step-by-step implementation plan for setting up a complete Docker-based development infrastructure with multi-service orchestration including PostgreSQL, Redis, Traefik, Authentik, FastAPI backend, and React frontend. | dep: Docker, Docker Compose, Make, Python 3.11, Node.js 20, PostgreSQL, Redis, Traefik, Authentik, FastAPI, React, Vite, nginx, alembic, uvicorn, SQLAlchemy, pydantic, structlog
|
||||
- 2026-05-17-auth-oauth.md | Implementation plan for adding Authentik-backed OIDC authentication with JWT access tokens and DB-backed refresh tokens to a FastAPI application | dep: FastAPI, SQLAlchemy, Alembic, python-jose, httpx, pytest, Authentik, PostgreSQL
|
||||
- 2026-05-17-database-models.md | Define an implementation plan for building SQLAlchemy 2.0 async database models, Alembic migrations, and seed data for a FastAPI backend. | dep: SQLAlchemy 2.x, asyncpg, Alembic, pytest, pytest-asyncio, Pydantic Settings, PostgreSQL, FastAPI
|
||||
- 2026-05-24-session-branch-selection.md | Implementation plan for replacing free-text branch input with a dropdown of available branches and adding "Create new branch" functionality in a session creation form | dep: React, TypeScript, FastAPI, Python, Git subprocess, Pydantic, API client
|
||||
## arch
|
||||
Chronological planning document store using markdown files with ISO date prefixes; each plan follows a consistent structure of problem statement, proposed solution, implementation steps, and verification criteria, serving as architectural decision records and work specifications before code implementation.
|
||||
Markdown-based technical specification documents using date-prefixed naming convention, each detailing phased implementation steps for specific system capabilities with technology stack integration points.
|
||||
## tags
|
||||
05, fastapi, 2026, implementation, plan, docker, postgresql, authentik
|
||||
## symbols
|
||||
|
||||
@@ -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
|
||||
|
||||
@@ -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
|
||||
|
||||
Reference in New Issue
Block a user