chore: track all project map and index files

Add generated .pi-map.md and .pi-map.index.md files across the repository
so the project navigation maps are shared and versioned. These artifacts
are maintained by project_map_init/patch/validate and must be kept in
sync with source edits.

Note: .cache/ remains ignored (added in previous commit).

docs/superpowers/.pi-map.index.md

@@ -0,0 +1,23 @@
+# docs/superpowers (index)
+dir: docs/superpowers
+
+## role
+Documentation directory for special capabilities or advanced features of the project.
+## parent
+index: docs/.pi-map.index.md
+map: docs/.pi-map.md
+## children
+- docs/superpowers/plans
+  index: docs/superpowers/plans/.pi-map.index.md
+  map: docs/superpowers/plans/.pi-map.md
+- docs/superpowers/specs
+  index: docs/superpowers/specs/.pi-map.index.md
+  map: docs/superpowers/specs/.pi-map.md
+## files
+## links
+index: docs/superpowers/.pi-map.index.md
+map: docs/superpowers/.pi-map.md
+## workflows
+-
+## dirty
+-

docs/superpowers/.pi-map.md

@@ -0,0 +1,18 @@
+# docs/superpowers
+dir: docs/superpowers
+
+index: docs/superpowers/.pi-map.index.md
+
+## role
+Documentation directory for special capabilities or advanced features of the project.
+## files
+## arch
+N/A (empty directory - no files to analyze)
+## tags
+-
+## symbols
+-
+## workflows
+-
+## dirty
+-

docs/superpowers/plans/.pi-map.index.md

@@ -0,0 +1,22 @@
+# docs/superpowers/plans (index)
+dir: docs/superpowers/plans
+
+## role
+Contains dated implementation planning documents that specify step-by-step technical approaches for major system features and infrastructure setup.
+## parent
+index: docs/superpowers/.pi-map.index.md
+map: docs/superpowers/.pi-map.md
+## children
+-
+## files
+- 2024-05-16-docker-infrastructure.md
+- 2026-05-17-auth-oauth.md
+- 2026-05-17-database-models.md
+- 2026-05-24-session-branch-selection.md
+## links
+index: docs/superpowers/plans/.pi-map.index.md
+map: docs/superpowers/plans/.pi-map.md
+## workflows
+-
+## dirty
+-

docs/superpowers/plans/.pi-map.md

@@ -0,0 +1,22 @@
+# docs/superpowers/plans
+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.
+## 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.
+## tags
+05, fastapi, 2026, implementation, plan, docker, postgresql, authentik
+## symbols
+-
+## workflows
+-
+## dirty
+-

docs/superpowers/specs/.pi-map.index.md

@@ -0,0 +1,20 @@
+# docs/superpowers/specs (index)
+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.
+## parent
+index: docs/superpowers/.pi-map.index.md
+map: docs/superpowers/.pi-map.md
+## children
+-
+## files
+- 2026-05-17-auth-oauth-design.md
+- 2026-05-24-session-branch-selection-design.md
+## links
+index: docs/superpowers/specs/.pi-map.index.md
+map: docs/superpowers/specs/.pi-map.md
+## workflows
+-
+## dirty
+-

docs/superpowers/specs/.pi-map.md

@@ -0,0 +1,20 @@
+# docs/superpowers/specs
+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.
+## 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.
+## tags
+design, 2026, 05, branch, session, document, authentik, jwt
+## symbols
+-
+## workflows
+-
+## dirty
+-