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
|
||||
|
||||
## role
|
||||
Central documentation hub and knowledge base for the Headquarter platform, providing navigation and access to all project guides, API references, and technical resources.
|
||||
Provides user-facing documentation and knowledge base for the Headquarter platform.
|
||||
## parent
|
||||
index: ./.pi-map.index.md
|
||||
map: ./.pi-map.md
|
||||
|
||||
+2
-2
@@ -4,11 +4,11 @@ dir: docs
|
||||
index: docs/.pi-map.index.md
|
||||
|
||||
## role
|
||||
Central documentation hub and knowledge base for the Headquarter platform, providing navigation and access to all project guides, API references, and technical resources.
|
||||
Provides user-facing documentation and knowledge base for the Headquarter platform.
|
||||
## files
|
||||
- README.md | Serves as the main index and navigation hub for the Headquarter platform documentation, organizing links to feature guides, API docs, architecture, deployment, and development resources.
|
||||
## arch
|
||||
Static documentation structure using markdown-based content organization with hierarchical topic grouping (features, API, architecture, deployment, development) and a single-entry-point index pattern.
|
||||
Static documentation site using markdown files organized hierarchically with a central README index.
|
||||
## tags
|
||||
readme, serves, main, index, navigation, hub, headquarter, platform
|
||||
## symbols
|
||||
|
||||
@@ -2,7 +2,7 @@
|
||||
dir: docs/api
|
||||
|
||||
## role
|
||||
Provides comprehensive API documentation for a FastAPI-based Headquarter REST API covering authentication, project management, repositories, SSH keys, terminal access, tool types, and user profiles.
|
||||
Provides comprehensive API documentation for the Headquarter platform's REST and WebSocket endpoints, covering authentication, project management, infrastructure tooling, and interactive terminal access.
|
||||
## parent
|
||||
index: docs/.pi-map.index.md
|
||||
map: docs/.pi-map.md
|
||||
|
||||
+2
-2
@@ -4,7 +4,7 @@ dir: docs/api
|
||||
index: docs/api/.pi-map.index.md
|
||||
|
||||
## role
|
||||
Provides comprehensive API documentation for a FastAPI-based Headquarter REST API covering authentication, project management, repositories, SSH keys, terminal access, tool types, and user profiles.
|
||||
Provides comprehensive API documentation for the Headquarter platform's REST and WebSocket endpoints, covering authentication, project management, infrastructure tooling, and interactive terminal access.
|
||||
## files
|
||||
- README.md | API documentation for a FastAPI-based Headquarter REST API describing authentication, endpoints, and testing | dep: FastAPI, REST API, session cookie authentication, JSON
|
||||
- auth.md | Documents OAuth2 authentication API endpoints for Authentik-based login flow with session management | dep: Authentik, OAuth2, session cookies
|
||||
@@ -16,7 +16,7 @@ Provides comprehensive API documentation for a FastAPI-based Headquarter REST AP
|
||||
- tool-types.md | Documents REST API endpoints for managing Docker Compose-based tool types with template variable support
|
||||
- users.md | Documents a REST API for user profile management, avatar uploads, and user-configurable settings.
|
||||
## arch
|
||||
Standard REST API documentation structure organized by domain/resource with OAuth2/Authentik authentication, WebSocket for real-time terminal sessions, and git-backed configuration profile system with merge/override semantics.
|
||||
Documentation-as-code structure organized by domain entity with FastAPI-style endpoint documentation, following standard HTTP method conventions (GET/POST/PUT/DELETE) with WebSocket extensions for real-time features, and OAuth2/session-based authentication patterns.
|
||||
## tags
|
||||
api, documents, rest, tool, terminal, endpoints, management, profile
|
||||
## symbols
|
||||
|
||||
@@ -2,7 +2,7 @@
|
||||
dir: docs/architecture
|
||||
|
||||
## role
|
||||
Documents the technical architecture and system design for the "Headquarter" full-stack application across all layers.
|
||||
Provides technical documentation for the "Headquarter" application's system architecture across all layers.
|
||||
## parent
|
||||
index: docs/.pi-map.index.md
|
||||
map: docs/.pi-map.md
|
||||
|
||||
@@ -4,14 +4,14 @@ dir: docs/architecture
|
||||
index: docs/architecture/.pi-map.index.md
|
||||
|
||||
## role
|
||||
Documents the technical architecture and system design for the "Headquarter" full-stack application across all layers.
|
||||
Provides technical documentation for the "Headquarter" application's system architecture across all layers.
|
||||
## files
|
||||
- backend.md | Documents the layered backend architecture of a FastAPI application with authentication, real-time monitoring, and service management. | dep: FastAPI, SQLAlchemy, asyncpg, Pydantic, Alembic, httpx, pytest, Authentik, Docker
|
||||
- database.md | Documents the PostgreSQL database schema, relationships, and operational procedures for a "Headquarter" application managing users, projects, git repositories, SSH keys, user configs, and tool types. | dep: PostgreSQL, SQLAlchemy ORM, Alembic, Authentik, Docker Compose
|
||||
- deployment.md | Documents the containerized deployment architecture, infrastructure components, and operational strategies for a web application called "Headquarter" | dep: Docker, Traefik, React, Vite, nginx, FastAPI, Python 3.11, PostgreSQL 15, Redis 7, Authentik, PgBouncer, alembic
|
||||
- frontend.md | Documents the frontend architecture for a React-based SPA called "Headquarter" with modular design patterns, real-time SSE events, and OAuth authentication. | dep: React, React Router, Vite, TypeScript, Vitest, React Testing Library, Authentik OAuth
|
||||
## arch
|
||||
Markdown-based architectural decision records (ADRs) organized by domain (backend/frontend/database/deployment) using layered architecture patterns for a FastAPI+React+PostgreSQL stack with real-time capabilities and containerized deployment.
|
||||
Documentation-as-code approach with markdown files organized by architectural concern (backend, database, deployment, frontend) covering a full-stack FastAPI/React/PostgreSQL system with real-time features and containerized deployment.
|
||||
## tags
|
||||
documents, backend, architecture, fastapi, application, alembic, authentik, database
|
||||
## symbols
|
||||
|
||||
@@ -2,7 +2,7 @@
|
||||
dir: docs/architecture/decisions
|
||||
|
||||
## role
|
||||
Documents key architectural decisions for the project, providing rationale and context for technology choices around authentication and database access patterns.
|
||||
Documents key architectural decisions made during the project's development to provide historical context and rationale for technology choices.
|
||||
## parent
|
||||
index: docs/architecture/.pi-map.index.md
|
||||
map: docs/architecture/.pi-map.md
|
||||
|
||||
@@ -4,12 +4,12 @@ dir: docs/architecture/decisions
|
||||
index: docs/architecture/decisions/.pi-map.index.md
|
||||
|
||||
## role
|
||||
Documents key architectural decisions for the project, providing rationale and context for technology choices around authentication and database access patterns.
|
||||
Documents key architectural decisions made during the project's development to provide historical context and rationale for technology choices.
|
||||
## files
|
||||
- adr-001-session-auth.md | Documents the architectural decision to use session-based authentication with HMAC-signed httpOnly cookies for OAuth2 flow instead of JWT alternatives | dep: Authentik, Traefik, OAuth2, HMAC-SHA256
|
||||
- adr-002-async-sqlalchemy.md | Architecture decision record documenting the choice to use SQLAlchemy 2.0 with async PostgreSQL via asyncpg for an async-capable Python application | dep: SQLAlchemy 2.0, PostgreSQL, asyncpg, Alembic
|
||||
## arch
|
||||
Lightweight ADR (Architecture Decision Record) pattern using Markdown files with sequential numbering, each capturing context, decision, consequences, and alternatives considered for major technical choices.
|
||||
Lightweight ADR (Architecture Decision Record) pattern using numbered, markdown-formatted documents with consistent structure covering context, decision, consequences, and status.
|
||||
## tags
|
||||
adr, async, session, sqlalchemy, decision, hmac, oauth2, 001
|
||||
## symbols
|
||||
|
||||
@@ -2,7 +2,7 @@
|
||||
dir: docs/deployment
|
||||
|
||||
## role
|
||||
Provides deployment documentation and operational guides for installing, configuring, and running the Headquarter application in production environments.
|
||||
Provides operational documentation for deploying, configuring, and securing the Headquarter application in production environments.
|
||||
## parent
|
||||
index: docs/.pi-map.index.md
|
||||
map: docs/.pi-map.md
|
||||
|
||||
@@ -4,14 +4,14 @@ dir: docs/deployment
|
||||
index: docs/deployment/.pi-map.index.md
|
||||
|
||||
## role
|
||||
Provides deployment documentation and operational guides for installing, configuring, and running the Headquarter application in production environments.
|
||||
Provides operational documentation for deploying, configuring, and securing the Headquarter application in production environments.
|
||||
## files
|
||||
- authentik.md | Documents how to configure Authentik as an OAuth2 provider for the Headquarter application | dep: Authentik, Headquarter, OAuth2, Python
|
||||
- docker.md | Provides deployment instructions for a multi-container "Headquarter" application using Docker Compose in development and production environments | dep: Docker, Docker Compose, FastAPI, React, Vite, PostgreSQL, Redis, Traefik, Alembic, Authentik, Let's Encrypt
|
||||
- environment.md | Documents all environment variables used by the Headquarter application, including their defaults, construction rules, and security requirements.
|
||||
- traefik.md | Documents how to configure and deploy Traefik as a reverse proxy with automatic HTTPS for a "Headquarter" application using Docker Compose and Docker labels. | dep: Traefik, Docker, Docker Compose, Let's Encrypt, DNS
|
||||
## arch
|
||||
Documentation-as-code approach using Markdown files organized by infrastructure component (reverse proxy, identity provider, container orchestration, configuration management), following a modular microservices deployment pattern with Docker Compose.
|
||||
Documentation-as-code pattern covering containerized deployment (Docker Compose), reverse proxy routing (Traefik), identity federation (Authentik OAuth2), and environment-based configuration management.
|
||||
## tags
|
||||
docker, authentik, headquarter, traefik, application, documents, environment, configure
|
||||
## symbols
|
||||
|
||||
@@ -2,7 +2,7 @@
|
||||
dir: docs/development
|
||||
|
||||
## role
|
||||
Developer onboarding and contribution standards documentation for the Headquarter full-stack web application project.
|
||||
Developer documentation hub providing setup, contribution, quality, and testing guidelines for the Headquarter full-stack project.
|
||||
## parent
|
||||
index: docs/.pi-map.index.md
|
||||
map: docs/.pi-map.md
|
||||
|
||||
@@ -4,14 +4,14 @@ dir: docs/development
|
||||
index: docs/development/.pi-map.index.md
|
||||
|
||||
## role
|
||||
Developer onboarding and contribution standards documentation for the Headquarter full-stack web application project.
|
||||
Developer documentation hub providing setup, contribution, quality, and testing guidelines for the Headquarter full-stack project.
|
||||
## files
|
||||
- contributing.md | Provides guidelines and workflows for contributing to the Headquarter project | dep: git, ruff, mypy, pytest, npm, React, TypeScript, Python
|
||||
- quality-gates.md | Defines mandatory quality gates (linting, type checking, testing, security, build) for backend (Python) and frontend (TypeScript) code before merge, including CI/CD integration and IDE setup. | dep: ruff, mypy, pytest, bandit, safety, TypeScript, ESLint, Vitest, pre-commit, npm, make
|
||||
- setup.md | Provides step-by-step instructions for setting up a full-stack development environment for a FastAPI/React application with PostgreSQL, Redis, and optional Authentik authentication. | dep: Python 3.11+, Node.js 18+, PostgreSQL 15+, Redis 7+, Git, Docker, FastAPI, React, Alembic, uvicorn, npm, Authentik
|
||||
- testing.md | Documents testing practices, frameworks, and guidelines for both backend (Python/pytest) and frontend (React/Vitest) of a web application called "Headquarter" | dep: pytest, pytest-asyncio, httpx, factory-boy, vitest, react-testing-library, jsdom, playwright, asyncpg, postgresql, authentik, github-actions
|
||||
## arch
|
||||
Documentation-as-code approach with structured markdown files covering environment setup, quality assurance gates, testing standards, and contribution workflows for a FastAPI/React/PostgreSQL/Redis stack.
|
||||
Static markdown documentation organized by concern (setup, contributing, quality, testing) with explicit FastAPI/Python backend and React/TypeScript frontend toolchain boundaries.
|
||||
## tags
|
||||
pytest, react, testing, contributing, npm, typescript, python, quality
|
||||
## symbols
|
||||
|
||||
@@ -2,7 +2,7 @@
|
||||
dir: docs/features
|
||||
|
||||
## 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.
|
||||
## parent
|
||||
index: docs/.pi-map.index.md
|
||||
map: docs/.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
|
||||
|
||||
@@ -2,7 +2,7 @@
|
||||
dir: docs/guides
|
||||
|
||||
## role
|
||||
Provides user-facing documentation for advanced configuration features
|
||||
Provides user-facing documentation for advanced configuration features of the platform.
|
||||
## parent
|
||||
index: docs/.pi-map.index.md
|
||||
map: docs/.pi-map.md
|
||||
|
||||
@@ -4,11 +4,11 @@ dir: docs/guides
|
||||
index: docs/guides/.pi-map.index.md
|
||||
|
||||
## role
|
||||
Provides user-facing documentation for advanced configuration features
|
||||
Provides user-facing documentation for advanced configuration features of the platform.
|
||||
## files
|
||||
- config-profiles-git-mounts.md | Documents how to mount files and directories from git repositories into tool instances via config profiles | dep: Git, container runtime (bind mounts), glob pattern matching
|
||||
## arch
|
||||
Simple documentation-as-code with markdown files organized by feature topic
|
||||
Flat markdown documentation structure with topic-specific guides.
|
||||
## tags
|
||||
git, config, profiles, mounts, documents, mount, directories, repositories
|
||||
## symbols
|
||||
|
||||
@@ -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
|
||||
|
||||
Vendored
+1
-1
@@ -10,7 +10,7 @@ Provides standardized markdown templates for consistent documentation of APIs, a
|
||||
- architecture.md | Provides a markdown template for documenting system architecture with standardized sections for components, data flow, technology stack, and operational considerations.
|
||||
- feature-doc.md | Markdown template for documenting software features with standardized sections
|
||||
## arch
|
||||
Template library pattern using structured markdown files with predefined section conventions to enforce documentation uniformity and reduce authoring overhead.
|
||||
Template-based documentation system using structured markdown files with predefined sections to enforce uniformity and completeness in technical documentation.
|
||||
## tags
|
||||
standardized, markdown, template, documenting, api, sections, architecture, provides
|
||||
## symbols
|
||||
|
||||
Reference in New Issue
Block a user