fix: disable native touch panning on mobile terminal and archive specs

- Change mobile terminal CSS to use touch-action: none and overscroll-behavior: none so the custom touch handler owns swipes - Archive completed/partial OpenSpec specs to openspec/changes/archive/2026-06-14-completed-specs-archive/ - Regenerate project maps Quality gates: npm run typecheck, npm run lint (apps/web)
2026-06-14 18:07:01 +00:00
parent 896674195c
commit c8db6ce933
580 changed files with 4678 additions and 4333 deletions
@@ -16,7 +16,7 @@ dir: .
 Trust boundary: index routes, map orients, source decides.

 ## role
-A self-hosted web-based project management and Git repository platform with OAuth2 authentication, designed for deployment via Docker Compose with Traefik reverse proxy.
+Infrastructure and configuration package for a self-hosted project management platform with containerized deployment, SSO integration, and AI-assisted development workflows.
 ## parent
 -
 ## children
@@ -69,6 +69,7 @@ A self-hosted web-based project management and Git repository platform with OAut
 - CHANGELOG.md
 - Makefile
 - README.md
+- context.md
 - docker-compose.traefik.yml
 - docker-compose.yml
 - progress.md
@@ -18,7 +18,7 @@ index: ./.pi-map.index.md
 Trust boundary: index routes, map orients, source decides.

 ## role
-A self-hosted web-based project management and Git repository platform with OAuth2/SSO authentication, containerized for Docker deployment.
+Infrastructure and configuration package for a self-hosted project management platform with containerized deployment, SSO integration, and AI-assisted development workflows.
 ## files
 - .env.example | Provides a template of environment variables for configuring a Headquarter application with PostgreSQL, Redis, Authentik SSO, and Docker/Traefik deployment
 - .gitignore | Specifies files and directories for Git to ignore across a multi-language project with Python, Node, and custom tooling | dep: Git
@@ -26,14 +26,15 @@ A self-hosted web-based project management and Git repository platform with OAut
 - CHANGELOG.md | Documents version history and notable changes for a Git-based project management web application
 - Makefile | Provides standard development commands for containerized web application lifecycle management via Docker Compose | dep: docker compose, alembic, pytest, ruff, mypy, playwright, npm, postgres, redis
 - README.md | A self-hosted platform for managing projects, git repositories, and development tools with OAuth2 authentication. | dep: FastAPI, SQLAlchemy, Pydantic, Alembic, python-jose, React, TypeScript, Vite, React Router, Docker, PostgreSQL, Traefik, Authentik, Git
+- context.md | Documents a mobile web terminal scrolling bug where CSS touch-action rules conflict with a custom touch handler, preventing proper gesture interception in xterm.js on mobile devices. | dep: React, xterm.js, CSS modules, use-terminal-page hook, MobileTerminalView, DesktopTerminalView, TerminalComponent, AppShell
 - docker-compose.traefik.yml | Deploys a multi-service web application (frontend, API, PostgreSQL, Redis) behind an existing Traefik reverse proxy with TLS termination and environment-configurable domains. | dep: docker, traefik, postgres, redis, authentik, docker-compose
 - docker-compose.yml | Defines a multi-service Docker Compose stack with PostgreSQL, Redis, API backend, and web frontend services for a "headquarter" application | dep: Docker, PostgreSQL, Redis, Vite, asyncpg, nginx
 - progress.md | Tracks completed and remaining tasks for a backend-frontend code refactoring project organized in 7 phases
 - swap-pane | Empty file with no functionality
 ## arch
-Multi-service containerized architecture (PostgreSQL, Redis, API backend, web frontend) with reverse proxy integration (Traefik), environment-driven configuration, and AI-agent-guided development workflows via OpenSpec.
+Docker Compose-based microservices architecture with frontend/backend separation, PostgreSQL/Redis data layer, Traefik reverse proxy with TLS, OAuth2 SSO via Authentik, and OpenSpec-driven AI agent orchestration.
 ## tags
-docker, redis, git, application, postgresql, compose, traefik, project
+docker, redis, git, application, postgresql, web, compose, traefik
 ## symbols
 -
 ## workflows
@@ -2,7 +2,7 @@
 dir: apps

 ## role
-Contains the main application entry points and top-level configurations for different deployable targets.
+Container directory for all deployable application entry points in the project.
 ## parent
 index: ./.pi-map.index.md
 map: ./.pi-map.md
@@ -4,10 +4,10 @@ dir: apps
 index: apps/.pi-map.index.md

 ## role
-Contains the main deployable applications or entry points for the project.
+Container directory for all deployable application entry points in the project.
 ## files
 ## arch
-Typically follows a multi-app workspace pattern where each subdirectory is an independent executable or service sharing common libraries.
+Monorepo-style top-level organization following workspace/package boundary pattern with likely separate deployable units per subdirectory.
 ## tags
 -
 ## symbols
@@ -2,7 +2,7 @@
 dir: apps/web

 ## role
-Frontend web application providing a browser-based UI with code editing, terminal, and routing capabilities for the "headquarter" project.
+Frontend web application providing the browser-based user interface for the project, built with React/Vite and served via nginx.
 ## parent
 index: apps/.pi-map.index.md
 map: apps/.pi-map.md
@@ -4,7 +4,7 @@ dir: apps/web
 index: apps/web/.pi-map.index.md

 ## role
-Frontend web application providing a browser-based UI with code editing, terminal, and routing capabilities for the "headquarter" project.
+Frontend web application providing the browser-based user interface for the project, built with React/Vite and served via nginx.
 ## files
 - .env.example | Template file defining example environment variables for frontend API and application URL configuration
 - .eslintrc.cjs | Configures ESLint for a TypeScript browser project with modern ECMAScript module support | dep: @typescript-eslint/parser, @typescript-eslint/eslint-plugin, eslint
@@ -16,7 +16,7 @@ Frontend web application providing a browser-based UI with code editing, termina
 - tsconfig.json | TypeScript configuration file for a React project using Vite with modern ES2020 target and bundler module resolution | dep: typescript, react, vite
 - vite.config.ts | Configures Vite build tool for a React project with custom dev server port and Vitest test settings. | dep: vite, @vitejs/plugin-react
 ## arch
-Modern React SPA built with Vite and TypeScript, containerized via multi-stage Docker with nginx serving, featuring client-side routing, optimized static asset delivery, and development tooling (ESLint, Vitest).
+Modern SPA architecture using Vite for bundling, TypeScript for type safety, React for UI components, with containerized nginx deployment and environment-driven configuration.
 ## tags
 react, eslint, vite, typescript, dom, application, nginx, web
 ## symbols
@@ -10,7 +10,7 @@ Provides the core web application entry point, routing infrastructure, and share
 - router.tsx | Defines the React Router configuration for a web application with protected routes, nested layouts, and redirects. | exp: AppRouter | dep: react-router-dom, ./components/app-shell, ./components/protected-route, ./pages/DashboardPage, ./pages/PlaceholderPage, ./pages/ProfilePage, ./pages/ProjectsPage, ./pages/GitRepositoriesPage, ./pages/GitHistoryPage, ./pages/ProjectSettingsPage, ./pages/SettingsPage, ./pages/TerminalPage, ./pages/ToolWorkshopPage, ./pages/SshKeysPage, ./pages/ConfigProfilesPage, ./pages/SessionsPage, ./pages/WorkspacesPage, ./pages/WorkspaceDetailPage
 - types.ts | Defines TypeScript type definitions for user sessions, projects, repositories, and workspaces in an application. | exp: SessionUser, SessionPayload, Project, WorkspaceSummary, RepositorySummary, ProjectWithRepos
 ## arch
-Modular React SPA with provider-based dependency injection, declarative routing with nested layouts and route guards, and centralized TypeScript type definitions.
+Implements a modular React SPA architecture using React Router v6 with nested route layouts, protected route guards via authentication/session providers, and centralized TypeScript domain modeling for cross-cutting concerns.
 ## tags
 pages, styles, css, router, react, session, dom, project
 ## symbols
@@ -2,7 +2,7 @@
 dir: apps/web/src/styles

 ## role
-Provides the complete visual design system and styling foundation for the web application, including themes, tokens, utilities, and component-specific styles.
+Provides the complete visual design system and styling foundation for the web application, encompassing global styles, theme tokens, utility classes, and component-specific styles.
 ## parent
 index: apps/web/src/.pi-map.index.md
 map: apps/web/src/.pi-map.md
@@ -4,16 +4,16 @@ dir: apps/web/src/styles
 index: apps/web/src/styles/.pi-map.index.md

 ## role
-Provides the complete visual design system and styling foundation for the web application, including themes, tokens, utilities, and component-specific styles.
+Provides the complete visual design system and styling foundation for the web application, encompassing global styles, theme tokens, utility classes, and component-specific styles.
 ## files
 - global.css | Defines global CSS styles for a web application shell layout, navigation, cards, forms, dialogs, settings pages, and responsive design patterns. | dep: CSS custom properties (CSS variables: --border, --panel, --brand, --muted, --ink, --bg, --danger, --success, --warning, --font-size-xs, --font-size-sm, --space-2, --space-3, --space-4, --space-5)
 - syntax-highlight.css | Stylesheet for a syntax highlighting component with toolbar, line numbers, code display, and Prism.js theme integration | dep: Prism.js
 - tokens.css | Defines a comprehensive CSS design token system with light/dark themes, spacing scales, breakpoints, and fluid typography for a web application.
- utilities.css | Provides responsive CSS utility classes and component styles for a web application including layout, terminal, session navigation, and mobile-specific adaptations. | dep: CSS custom properties (--space-*, --border, --bg, --muted, --brand, --danger, --danger-light, --success, --text, --text-xs, --text-sm), xterm.js (terminal library)
+- utilities.css | Provides a comprehensive CSS utility system for responsive layouts, terminal interfaces, and UI components with mobile-first design patterns. | dep: CSS custom properties (--space-*, --border, --bg, --muted, --success, --text, --brand, --danger, --danger-light), xterm.js (terminal library)
 ## arch
-Token-driven CSS architecture using CSS custom properties for light/dark theming, utility-first responsive patterns, and modular separation of concerns across global base styles, design tokens, syntax highlighting, and adaptive utilities.
+Token-driven CSS architecture using CSS custom properties for themeable design system with mobile-first responsive utilities, separate component-specific stylesheets, and light/dark mode support.
 ## tags
-space, global, css, web, application, danger, syntax, text
+space, global, css, design, danger, syntax, defines, web
 ## symbols
 -
 ## workflows
@@ -564,6 +564,14 @@ a.nav-item,
 	width: 100% !important;
 }

+/* On mobile the custom touch handler scrolls the buffer; disable native
+   panning/overscroll so swipe gestures are not forwarded to a scrollbar. */
+.terminal-wrapper.mobile .terminal-container,
+.terminal-wrapper.mobile .terminal-container .xterm-viewport {
+	touch-action: none;
+	overscroll-behavior: none;
+}
+
 /* xterm.js manages its own positioning and sizing */

 .terminal-container canvas {
@@ -1771,7 +1779,7 @@ a.nav-item,
 /* Disable zoom on mobile terminal */
@media (max-width: 767px) {
 	.mobile-terminal-wrapper {
-		touch-action: pan-y;
+		touch-action: none;
 		-webkit-text-size-adjust: none;
 	}

@@ -1781,9 +1789,14 @@ a.nav-item,
 	}

 	.terminal-container {
-		touch-action: pan-y;
+		touch-action: none;
 		padding: 0;
 	}
+
+	.terminal-wrapper.mobile .terminal-container .xterm-viewport {
+		touch-action: none;
+		overscroll-behavior: none;
+	}
 }

 /* Animations */
@@ -2280,8 +2293,9 @@ a.nav-item,
 }

 .mobile-edit-code {
-	font-family: "IBM Plex Mono", ui-monospace, SFMono-Regular, Menlo, Monaco,
-		Consolas, monospace;
+	font-family:
+		"IBM Plex Mono", ui-monospace, SFMono-Regular, Menlo, Monaco, Consolas,
+		monospace;
 	font-size: 0.8125rem;
 }

@@ -2440,8 +2454,9 @@ a.nav-item,
 }

 .mobile-form-code {
-	font-family: "IBM Plex Mono", ui-monospace, SFMono-Regular, Menlo, Monaco,
-		Consolas, monospace;
+	font-family:
+		"IBM Plex Mono", ui-monospace, SFMono-Regular, Menlo, Monaco, Consolas,
+		monospace;
 	font-size: 0.8125rem;
 }

@@ -2694,8 +2709,9 @@ a.nav-item,
 	border-radius: 8px;
 	overflow-x: auto;
 	font-size: 0.8125rem;
-	font-family: "IBM Plex Mono", ui-monospace, SFMono-Regular, Menlo, Monaco,
-		Consolas, monospace;
+	font-family:
+		"IBM Plex Mono", ui-monospace, SFMono-Regular, Menlo, Monaco, Consolas,
+		monospace;
 	margin: var(--space-2) 0 0 0;
 }

@@ -2715,8 +2731,9 @@ a.nav-item,
 }

 .mobile-preview-mapping {
-	font-family: "IBM Plex Mono", ui-monospace, SFMono-Regular, Menlo, Monaco,
-		Consolas, monospace;
+	font-family:
+		"IBM Plex Mono", ui-monospace, SFMono-Regular, Menlo, Monaco, Consolas,
+		monospace;
 	font-size: 0.8125rem;
 	color: var(--muted);
 	margin-top: var(--space-1);
@@ -1,39 +1,52 @@
-# openspec (index)
-dir: openspec
+# . (index)
+dir: .
+
+## Project Map Protocol
+
+1. Read this protocol and the root `.pi-map.index.md` first.
+2. Use `index:` / `map:` references to open relevant directory indexes and maps.
+3. Load indexes before rich maps during task-start navigation.
+4. Read the local rich map and actual source before editing.
+5. Treat non-empty `## dirty` sections in either artifact as stale.
+6. If source and generated artifacts disagree, trust source.
+7. If map and index disagree, trust neither blindly; verify from source and regenerate the pair.
+8. After editing source, run `project_map_patch` for each changed file.
+9. Before broad architectural claims or final handoff, run `project_map_validate` when freshness matters.
+
+Trust boundary: index routes, map orients, source decides.

 ## role
-Defines the OpenSpec methodology and configuration for managing software requirements, specifications, and task tracking as living documentation within a Docker-based coding agent management platform.
+Defines a living documentation methodology and project configuration for managing software requirements, specifications, and development discipline rules within a Docker-based coding agent platform.
 ## parent
-index: ./.pi-map.index.md
-map: ./.pi-map.md
+-
 ## children
- openspec/changes
-  index: openspec/changes/.pi-map.index.md
-  map: openspec/changes/.pi-map.md
- openspec/designs
-  index: openspec/designs/.pi-map.index.md
-  map: openspec/designs/.pi-map.md
- openspec/docs
-  index: openspec/docs/.pi-map.index.md
-  map: openspec/docs/.pi-map.md
- openspec/explorations
-  index: openspec/explorations/.pi-map.index.md
-  map: openspec/explorations/.pi-map.md
- openspec/proposals
-  index: openspec/proposals/.pi-map.index.md
-  map: openspec/proposals/.pi-map.md
- openspec/specs
-  index: openspec/specs/.pi-map.index.md
-  map: openspec/specs/.pi-map.md
- openspec/tasks
-  index: openspec/tasks/.pi-map.index.md
-  map: openspec/tasks/.pi-map.md
+- changes
+  index: changes/.pi-map.index.md
+  map: changes/.pi-map.md
+- designs
+  index: designs/.pi-map.index.md
+  map: designs/.pi-map.md
+- docs
+  index: docs/.pi-map.index.md
+  map: docs/.pi-map.md
+- explorations
+  index: explorations/.pi-map.index.md
+  map: explorations/.pi-map.md
+- proposals
+  index: proposals/.pi-map.index.md
+  map: proposals/.pi-map.md
+- specs
+  index: specs/.pi-map.index.md
+  map: specs/.pi-map.md
+- tasks
+  index: tasks/.pi-map.index.md
+  map: tasks/.pi-map.md
 ## files
 - README.md
 - config.yaml
 ## links
-index: openspec/.pi-map.index.md
-map: openspec/.pi-map.md
+index: ./.pi-map.index.md
+map: ./.pi-map.md
 ## workflows
 -
 ## dirty
@@ -1,15 +1,29 @@
-# openspec
-dir: openspec
+# .
+dir: .

-index: openspec/.pi-map.index.md
+index: ./.pi-map.index.md
+
+## Project Map Protocol
+
+1. Read this protocol and the root `.pi-map.index.md` first.
+2. Use `index:` / `map:` references to open relevant directory indexes and maps.
+3. Load indexes before rich maps during task-start navigation.
+4. Read the local rich map and actual source before editing.
+5. Treat non-empty `## dirty` sections in either artifact as stale.
+6. If source and generated artifacts disagree, trust source.
+7. If map and index disagree, trust neither blindly; verify from source and regenerate the pair.
+8. After editing source, run `project_map_patch` for each changed file.
+9. Before broad architectural claims or final handoff, run `project_map_validate` when freshness matters.
+
+Trust boundary: index routes, map orients, source decides.

 ## role
-Defines the OpenSpec methodology and configuration for managing software requirements, specifications, and task tracking as living documentation within a Docker-based coding agent management platform.
+Defines a living documentation methodology and project configuration for managing software requirements, specifications, and development discipline rules within a Docker-based coding agent platform.
 ## files
 - README.md | Documents the OpenSpec methodology for managing software requirements, specifications, and task tracking as living documentation within a project repository. | dep: OpenSpec CLI (@fission-ai/openspec), Docker, SQLAlchemy, Alembic, Authentik, React, TypeScript, Tailwind, Traefik, Jinja2, xterm.js, pytest, mypy, ruff, npm
 - config.yaml | Configuration file defining project metadata, technology stack, and software development discipline rules for a Docker-based coding agent management platform | dep: FastAPI, React, Vite, PostgreSQL, SQLAlchemy, Redis, Alembic, pytest, Docker Compose, Traefik, Authentik
 ## arch
-Documentation-as-code pattern with YAML-based configuration management, structured metadata definitions, and rule-based discipline enforcement for AI-assisted software development workflows.
+Documentation-as-code pattern with YAML-based declarative configuration separating project metadata, technology stack definitions, and behavioral rules for automated agent orchestration.
 ## tags
 software, project, docker, sqlalchemy, alembic, authentik, react, traefik
 ## symbols
@@ -1,32 +1,37 @@
-# . (index)
-dir: .
-
-## Project Map Protocol
-
-1. Read this protocol and the root `.pi-map.index.md` first.
-2. Use `index:` / `map:` references to open relevant directory indexes and maps.
-3. Load indexes before rich maps during task-start navigation.
-4. Read the local rich map and actual source before editing.
-5. Treat non-empty `## dirty` sections in either artifact as stale.
-6. If source and generated artifacts disagree, trust source.
-7. If map and index disagree, trust neither blindly; verify from source and regenerate the pair.
-8. After editing source, run `project_map_patch` for each changed file.
-9. Before broad architectural claims or final handoff, run `project_map_validate` when freshness matters.
-
-Trust boundary: index routes, map orients, source decides.
+# changes (index)
+dir: changes

 ## role
-This is an empty directory with no files to analyze.
+Package for tracking, storing, and managing file changes or diffs in the project.
 ## parent
-
-## children
- archive
-  index: archive/.pi-map.index.md
-  map: archive/.pi-map.md
-## files
-## links
 index: ./.pi-map.index.md
 map: ./.pi-map.md
+## children
+- changes/archive
+  index: changes/archive/.pi-map.index.md
+  map: changes/archive/.pi-map.md
+- changes/fix-terminal-container-overflow
+  index: changes/fix-terminal-container-overflow/.pi-map.index.md
+  map: changes/fix-terminal-container-overflow/.pi-map.md
+- changes/fix-tmux-mouse-config
+  index: changes/fix-tmux-mouse-config/.pi-map.index.md
+  map: changes/fix-tmux-mouse-config/.pi-map.md
+- changes/mobile-config-profiles-ui
+  index: changes/mobile-config-profiles-ui/.pi-map.index.md
+  map: changes/mobile-config-profiles-ui/.pi-map.md
+- changes/mobile-edit-default-bottom-actions
+  index: changes/mobile-edit-default-bottom-actions/.pi-map.index.md
+  map: changes/mobile-edit-default-bottom-actions/.pi-map.md
+- changes/mobile-list-delete-button
+  index: changes/mobile-list-delete-button/.pi-map.index.md
+  map: changes/mobile-list-delete-button/.pi-map.md
+- changes/mobile-tool-profile-ui
+  index: changes/mobile-tool-profile-ui/.pi-map.index.md
+  map: changes/mobile-tool-profile-ui/.pi-map.md
+## files
+## links
+index: changes/.pi-map.index.md
+map: changes/.pi-map.md
 ## workflows
 -
 ## dirty
@@ -1,27 +1,13 @@
-# .
-dir: .
+# changes
+dir: changes

-index: ./.pi-map.index.md
-
-## Project Map Protocol
-
-1. Read this protocol and the root `.pi-map.index.md` first.
-2. Use `index:` / `map:` references to open relevant directory indexes and maps.
-3. Load indexes before rich maps during task-start navigation.
-4. Read the local rich map and actual source before editing.
-5. Treat non-empty `## dirty` sections in either artifact as stale.
-6. If source and generated artifacts disagree, trust source.
-7. If map and index disagree, trust neither blindly; verify from source and regenerate the pair.
-8. After editing source, run `project_map_patch` for each changed file.
-9. Before broad architectural claims or final handoff, run `project_map_validate` when freshness matters.
-
-Trust boundary: index routes, map orients, source decides.
+index: changes/.pi-map.index.md

 ## role
-This is an empty directory with no files to analyze.
+Package for tracking, storing, and managing file changes or diffs in the project.
 ## files
 ## arch
-N/A - no code or architecture present
+Likely implements a change-log or diff-storage pattern, possibly with immutable change records and versioning for audit trails or synchronization.
 ## tags
 -
 ## symbols
@@ -1,151 +1,167 @@
-# archive (index)
-dir: archive
+# . (index)
+dir: .
+
+## Project Map Protocol
+
+1. Read this protocol and the root `.pi-map.index.md` first.
+2. Use `index:` / `map:` references to open relevant directory indexes and maps.
+3. Load indexes before rich maps during task-start navigation.
+4. Read the local rich map and actual source before editing.
+5. Treat non-empty `## dirty` sections in either artifact as stale.
+6. If source and generated artifacts disagree, trust source.
+7. If map and index disagree, trust neither blindly; verify from source and regenerate the pair.
+8. After editing source, run `project_map_patch` for each changed file.
+9. Before broad architectural claims or final handoff, run `project_map_validate` when freshness matters.
+
+Trust boundary: index routes, map orients, source decides.

 ## role
-Contains historical or deprecated code and resources that are no longer active in the project but retained for reference or backup purposes.
+This is an empty package directory with no files to analyze.
 ## parent
-index: ./.pi-map.index.md
-map: ./.pi-map.md
+-
 ## children
- archive/2025-05-17-oauth-traefik-integration
-  index: archive/2025-05-17-oauth-traefik-integration/.pi-map.index.md
-  map: archive/2025-05-17-oauth-traefik-integration/.pi-map.md
- archive/2025-05-17-user-profile
-  index: archive/2025-05-17-user-profile/.pi-map.index.md
-  map: archive/2025-05-17-user-profile/.pi-map.md
- archive/2025-05-18-git-repo-management
-  index: archive/2025-05-18-git-repo-management/.pi-map.index.md
-  map: archive/2025-05-18-git-repo-management/.pi-map.md
- archive/2025-05-18-ssh-key-management
-  index: archive/2025-05-18-ssh-key-management/.pi-map.index.md
-  map: archive/2025-05-18-ssh-key-management/.pi-map.md
- archive/2025-05-18-test-infrastructure-improvements
-  index: archive/2025-05-18-test-infrastructure-improvements/.pi-map.index.md
-  map: archive/2025-05-18-test-infrastructure-improvements/.pi-map.md
- archive/2025-05-18-tool-types-definition
-  index: archive/2025-05-18-tool-types-definition/.pi-map.index.md
-  map: archive/2025-05-18-tool-types-definition/.pi-map.md
- archive/2025-05-18-user-config-management
-  index: archive/2025-05-18-user-config-management/.pi-map.index.md
-  map: archive/2025-05-18-user-config-management/.pi-map.md
- archive/2026-05-17-auth-oauth
-  index: archive/2026-05-17-auth-oauth/.pi-map.index.md
-  map: archive/2026-05-17-auth-oauth/.pi-map.md
- archive/2026-05-17-database-models
-  index: archive/2026-05-17-database-models/.pi-map.index.md
-  map: archive/2026-05-17-database-models/.pi-map.md
- archive/2026-05-17-frontend-foundation
-  index: archive/2026-05-17-frontend-foundation/.pi-map.index.md
-  map: archive/2026-05-17-frontend-foundation/.pi-map.md
- archive/2026-05-17-project-management
-  index: archive/2026-05-17-project-management/.pi-map.index.md
-  map: archive/2026-05-17-project-management/.pi-map.md
- archive/2026-05-18-database-setup-recovery
-  index: archive/2026-05-18-database-setup-recovery/.pi-map.index.md
-  map: archive/2026-05-18-database-setup-recovery/.pi-map.md
- archive/2026-05-18-simplify-authentik-auth
-  index: archive/2026-05-18-simplify-authentik-auth/.pi-map.index.md
-  map: archive/2026-05-18-simplify-authentik-auth/.pi-map.md
- archive/2026-05-19-api-documentation
-  index: archive/2026-05-19-api-documentation/.pi-map.index.md
-  map: archive/2026-05-19-api-documentation/.pi-map.md
- archive/2026-05-19-documentation-overhaul
-  index: archive/2026-05-19-documentation-overhaul/.pi-map.index.md
-  map: archive/2026-05-19-documentation-overhaul/.pi-map.md
- archive/2026-05-19-file-editor
-  index: archive/2026-05-19-file-editor/.pi-map.index.md
-  map: archive/2026-05-19-file-editor/.pi-map.md
- archive/2026-05-19-git-control
-  index: archive/2026-05-19-git-control/.pi-map.index.md
-  map: archive/2026-05-19-git-control/.pi-map.md
- archive/2026-05-19-git-history-visualization
-  index: archive/2026-05-19-git-history-visualization/.pi-map.index.md
-  map: archive/2026-05-19-git-history-visualization/.pi-map.md
- archive/2026-05-19-repo-workspace
-  index: archive/2026-05-19-repo-workspace/.pi-map.index.md
-  map: archive/2026-05-19-repo-workspace/.pi-map.md
- archive/2026-05-19-responsive-spacing-improvements
-  index: archive/2026-05-19-responsive-spacing-improvements/.pi-map.index.md
-  map: archive/2026-05-19-responsive-spacing-improvements/.pi-map.md
- archive/2026-05-19-smart-git-url-parsing
-  index: archive/2026-05-19-smart-git-url-parsing/.pi-map.index.md
-  map: archive/2026-05-19-smart-git-url-parsing/.pi-map.md
- archive/2026-05-19-tool-instances
-  index: archive/2026-05-19-tool-instances/.pi-map.index.md
-  map: archive/2026-05-19-tool-instances/.pi-map.md
- archive/2026-05-19-tool-terminal
-  index: archive/2026-05-19-tool-terminal/.pi-map.index.md
-  map: archive/2026-05-19-tool-terminal/.pi-map.md
- archive/2026-05-19-universal-icon-system
-  index: archive/2026-05-19-universal-icon-system/.pi-map.index.md
-  map: archive/2026-05-19-universal-icon-system/.pi-map.md
- archive/2026-05-19-workspace-visual-overhaul
-  index: archive/2026-05-19-workspace-visual-overhaul/.pi-map.index.md
-  map: archive/2026-05-19-workspace-visual-overhaul/.pi-map.md
- archive/2026-05-22-cloudflare-tunnel-instances-superseded
-  index: archive/2026-05-22-cloudflare-tunnel-instances-superseded/.pi-map.index.md
-  map: archive/2026-05-22-cloudflare-tunnel-instances-superseded/.pi-map.md
- archive/2026-05-22-enforce-single-tool-type-with-port-config
-  index: archive/2026-05-22-enforce-single-tool-type-with-port-config/.pi-map.index.md
-  map: archive/2026-05-22-enforce-single-tool-type-with-port-config/.pi-map.md
- archive/2026-05-22-git-repo-ssh-clone-check
-  index: archive/2026-05-22-git-repo-ssh-clone-check/.pi-map.index.md
-  map: archive/2026-05-22-git-repo-ssh-clone-check/.pi-map.md
- archive/2026-05-22-git-repo-working-clones
-  index: archive/2026-05-22-git-repo-working-clones/.pi-map.index.md
-  map: archive/2026-05-22-git-repo-working-clones/.pi-map.md
- archive/2026-05-22-instance-health-monitoring
-  index: archive/2026-05-22-instance-health-monitoring/.pi-map.index.md
-  map: archive/2026-05-22-instance-health-monitoring/.pi-map.md
- archive/2026-05-22-instance-proxy
-  index: archive/2026-05-22-instance-proxy/.pi-map.index.md
-  map: archive/2026-05-22-instance-proxy/.pi-map.md
- archive/2026-05-22-opencode-web-terminal
-  index: archive/2026-05-22-opencode-web-terminal/.pi-map.index.md
-  map: archive/2026-05-22-opencode-web-terminal/.pi-map.md
- archive/2026-05-22-repo-clone-mode-with-ssh
-  index: archive/2026-05-22-repo-clone-mode-with-ssh/.pi-map.index.md
-  map: archive/2026-05-22-repo-clone-mode-with-ssh/.pi-map.md
- archive/2026-05-22-session-management-fixes
-  index: archive/2026-05-22-session-management-fixes/.pi-map.index.md
-  map: archive/2026-05-22-session-management-fixes/.pi-map.md
- archive/2026-05-22-sessions-hub
-  index: archive/2026-05-22-sessions-hub/.pi-map.index.md
-  map: archive/2026-05-22-sessions-hub/.pi-map.md
- archive/2026-05-22-tool-config-management
-  index: archive/2026-05-22-tool-config-management/.pi-map.index.md
-  map: archive/2026-05-22-tool-config-management/.pi-map.md
- archive/2026-05-22-tool-config-ui-rework
-  index: archive/2026-05-22-tool-config-ui-rework/.pi-map.index.md
-  map: archive/2026-05-22-tool-config-ui-rework/.pi-map.md
- archive/2026-05-22-tool-workshop
-  index: archive/2026-05-22-tool-workshop/.pi-map.index.md
-  map: archive/2026-05-22-tool-workshop/.pi-map.md
- archive/2026-05-22-ui-redesign-home-settings
-  index: archive/2026-05-22-ui-redesign-home-settings/.pi-map.index.md
-  map: archive/2026-05-22-ui-redesign-home-settings/.pi-map.md
- archive/2026-05-23-remove-built-in-tools
-  index: archive/2026-05-23-remove-built-in-tools/.pi-map.index.md
-  map: archive/2026-05-23-remove-built-in-tools/.pi-map.md
- archive/2026-05-24-terminal-startup-and-container-tools
-  index: archive/2026-05-24-terminal-startup-and-container-tools/.pi-map.index.md
-  map: archive/2026-05-24-terminal-startup-and-container-tools/.pi-map.md
- archive/2026-05-25-add-config-profiles
-  index: archive/2026-05-25-add-config-profiles/.pi-map.index.md
-  map: archive/2026-05-25-add-config-profiles/.pi-map.md
- archive/2026-05-25-mobile-app-usability
-  index: archive/2026-05-25-mobile-app-usability/.pi-map.index.md
-  map: archive/2026-05-25-mobile-app-usability/.pi-map.md
- archive/2026-05-25-mobile-pages-overhaul
-  index: archive/2026-05-25-mobile-pages-overhaul/.pi-map.index.md
-  map: archive/2026-05-25-mobile-pages-overhaul/.pi-map.md
- archive/2026-06-12-completed-changes-archive
-  index: archive/2026-06-12-completed-changes-archive/.pi-map.index.md
-  map: archive/2026-06-12-completed-changes-archive/.pi-map.md
+- 2025-05-17-oauth-traefik-integration
+  index: 2025-05-17-oauth-traefik-integration/.pi-map.index.md
+  map: 2025-05-17-oauth-traefik-integration/.pi-map.md
+- 2025-05-17-user-profile
+  index: 2025-05-17-user-profile/.pi-map.index.md
+  map: 2025-05-17-user-profile/.pi-map.md
+- 2025-05-18-git-repo-management
+  index: 2025-05-18-git-repo-management/.pi-map.index.md
+  map: 2025-05-18-git-repo-management/.pi-map.md
+- 2025-05-18-ssh-key-management
+  index: 2025-05-18-ssh-key-management/.pi-map.index.md
+  map: 2025-05-18-ssh-key-management/.pi-map.md
+- 2025-05-18-test-infrastructure-improvements
+  index: 2025-05-18-test-infrastructure-improvements/.pi-map.index.md
+  map: 2025-05-18-test-infrastructure-improvements/.pi-map.md
+- 2025-05-18-tool-types-definition
+  index: 2025-05-18-tool-types-definition/.pi-map.index.md
+  map: 2025-05-18-tool-types-definition/.pi-map.md
+- 2025-05-18-user-config-management
+  index: 2025-05-18-user-config-management/.pi-map.index.md
+  map: 2025-05-18-user-config-management/.pi-map.md
+- 2026-05-17-auth-oauth
+  index: 2026-05-17-auth-oauth/.pi-map.index.md
+  map: 2026-05-17-auth-oauth/.pi-map.md
+- 2026-05-17-database-models
+  index: 2026-05-17-database-models/.pi-map.index.md
+  map: 2026-05-17-database-models/.pi-map.md
+- 2026-05-17-frontend-foundation
+  index: 2026-05-17-frontend-foundation/.pi-map.index.md
+  map: 2026-05-17-frontend-foundation/.pi-map.md
+- 2026-05-17-project-management
+  index: 2026-05-17-project-management/.pi-map.index.md
+  map: 2026-05-17-project-management/.pi-map.md
+- 2026-05-18-database-setup-recovery
+  index: 2026-05-18-database-setup-recovery/.pi-map.index.md
+  map: 2026-05-18-database-setup-recovery/.pi-map.md
+- 2026-05-18-simplify-authentik-auth
+  index: 2026-05-18-simplify-authentik-auth/.pi-map.index.md
+  map: 2026-05-18-simplify-authentik-auth/.pi-map.md
+- 2026-05-19-api-documentation
+  index: 2026-05-19-api-documentation/.pi-map.index.md
+  map: 2026-05-19-api-documentation/.pi-map.md
+- 2026-05-19-documentation-overhaul
+  index: 2026-05-19-documentation-overhaul/.pi-map.index.md
+  map: 2026-05-19-documentation-overhaul/.pi-map.md
+- 2026-05-19-file-editor
+  index: 2026-05-19-file-editor/.pi-map.index.md
+  map: 2026-05-19-file-editor/.pi-map.md
+- 2026-05-19-git-control
+  index: 2026-05-19-git-control/.pi-map.index.md
+  map: 2026-05-19-git-control/.pi-map.md
+- 2026-05-19-git-history-visualization
+  index: 2026-05-19-git-history-visualization/.pi-map.index.md
+  map: 2026-05-19-git-history-visualization/.pi-map.md
+- 2026-05-19-repo-workspace
+  index: 2026-05-19-repo-workspace/.pi-map.index.md
+  map: 2026-05-19-repo-workspace/.pi-map.md
+- 2026-05-19-responsive-spacing-improvements
+  index: 2026-05-19-responsive-spacing-improvements/.pi-map.index.md
+  map: 2026-05-19-responsive-spacing-improvements/.pi-map.md
+- 2026-05-19-smart-git-url-parsing
+  index: 2026-05-19-smart-git-url-parsing/.pi-map.index.md
+  map: 2026-05-19-smart-git-url-parsing/.pi-map.md
+- 2026-05-19-tool-instances
+  index: 2026-05-19-tool-instances/.pi-map.index.md
+  map: 2026-05-19-tool-instances/.pi-map.md
+- 2026-05-19-tool-terminal
+  index: 2026-05-19-tool-terminal/.pi-map.index.md
+  map: 2026-05-19-tool-terminal/.pi-map.md
+- 2026-05-19-universal-icon-system
+  index: 2026-05-19-universal-icon-system/.pi-map.index.md
+  map: 2026-05-19-universal-icon-system/.pi-map.md
+- 2026-05-19-workspace-visual-overhaul
+  index: 2026-05-19-workspace-visual-overhaul/.pi-map.index.md
+  map: 2026-05-19-workspace-visual-overhaul/.pi-map.md
+- 2026-05-22-cloudflare-tunnel-instances-superseded
+  index: 2026-05-22-cloudflare-tunnel-instances-superseded/.pi-map.index.md
+  map: 2026-05-22-cloudflare-tunnel-instances-superseded/.pi-map.md
+- 2026-05-22-enforce-single-tool-type-with-port-config
+  index: 2026-05-22-enforce-single-tool-type-with-port-config/.pi-map.index.md
+  map: 2026-05-22-enforce-single-tool-type-with-port-config/.pi-map.md
+- 2026-05-22-git-repo-ssh-clone-check
+  index: 2026-05-22-git-repo-ssh-clone-check/.pi-map.index.md
+  map: 2026-05-22-git-repo-ssh-clone-check/.pi-map.md
+- 2026-05-22-git-repo-working-clones
+  index: 2026-05-22-git-repo-working-clones/.pi-map.index.md
+  map: 2026-05-22-git-repo-working-clones/.pi-map.md
+- 2026-05-22-instance-health-monitoring
+  index: 2026-05-22-instance-health-monitoring/.pi-map.index.md
+  map: 2026-05-22-instance-health-monitoring/.pi-map.md
+- 2026-05-22-instance-proxy
+  index: 2026-05-22-instance-proxy/.pi-map.index.md
+  map: 2026-05-22-instance-proxy/.pi-map.md
+- 2026-05-22-opencode-web-terminal
+  index: 2026-05-22-opencode-web-terminal/.pi-map.index.md
+  map: 2026-05-22-opencode-web-terminal/.pi-map.md
+- 2026-05-22-repo-clone-mode-with-ssh
+  index: 2026-05-22-repo-clone-mode-with-ssh/.pi-map.index.md
+  map: 2026-05-22-repo-clone-mode-with-ssh/.pi-map.md
+- 2026-05-22-session-management-fixes
+  index: 2026-05-22-session-management-fixes/.pi-map.index.md
+  map: 2026-05-22-session-management-fixes/.pi-map.md
+- 2026-05-22-sessions-hub
+  index: 2026-05-22-sessions-hub/.pi-map.index.md
+  map: 2026-05-22-sessions-hub/.pi-map.md
+- 2026-05-22-tool-config-management
+  index: 2026-05-22-tool-config-management/.pi-map.index.md
+  map: 2026-05-22-tool-config-management/.pi-map.md
+- 2026-05-22-tool-config-ui-rework
+  index: 2026-05-22-tool-config-ui-rework/.pi-map.index.md
+  map: 2026-05-22-tool-config-ui-rework/.pi-map.md
+- 2026-05-22-tool-workshop
+  index: 2026-05-22-tool-workshop/.pi-map.index.md
+  map: 2026-05-22-tool-workshop/.pi-map.md
+- 2026-05-22-ui-redesign-home-settings
+  index: 2026-05-22-ui-redesign-home-settings/.pi-map.index.md
+  map: 2026-05-22-ui-redesign-home-settings/.pi-map.md
+- 2026-05-23-remove-built-in-tools
+  index: 2026-05-23-remove-built-in-tools/.pi-map.index.md
+  map: 2026-05-23-remove-built-in-tools/.pi-map.md
+- 2026-05-24-terminal-startup-and-container-tools
+  index: 2026-05-24-terminal-startup-and-container-tools/.pi-map.index.md
+  map: 2026-05-24-terminal-startup-and-container-tools/.pi-map.md
+- 2026-05-25-add-config-profiles
+  index: 2026-05-25-add-config-profiles/.pi-map.index.md
+  map: 2026-05-25-add-config-profiles/.pi-map.md
+- 2026-05-25-mobile-app-usability
+  index: 2026-05-25-mobile-app-usability/.pi-map.index.md
+  map: 2026-05-25-mobile-app-usability/.pi-map.md
+- 2026-05-25-mobile-pages-overhaul
+  index: 2026-05-25-mobile-pages-overhaul/.pi-map.index.md
+  map: 2026-05-25-mobile-pages-overhaul/.pi-map.md
+- 2026-06-12-completed-changes-archive
+  index: 2026-06-12-completed-changes-archive/.pi-map.index.md
+  map: 2026-06-12-completed-changes-archive/.pi-map.md
+- 2026-06-14-completed-specs-archive
+  index: 2026-06-14-completed-specs-archive/.pi-map.index.md
+  map: 2026-06-14-completed-specs-archive/.pi-map.md
 ## files
 ## links
-index: archive/.pi-map.index.md
-map: archive/.pi-map.md
+index: ./.pi-map.index.md
+map: ./.pi-map.md
 ## workflows
 -
 ## dirty
@@ -1,13 +1,27 @@
-# archive
-dir: archive
+# .
+dir: .

-index: archive/.pi-map.index.md
+index: ./.pi-map.index.md
+
+## Project Map Protocol
+
+1. Read this protocol and the root `.pi-map.index.md` first.
+2. Use `index:` / `map:` references to open relevant directory indexes and maps.
+3. Load indexes before rich maps during task-start navigation.
+4. Read the local rich map and actual source before editing.
+5. Treat non-empty `## dirty` sections in either artifact as stale.
+6. If source and generated artifacts disagree, trust source.
+7. If map and index disagree, trust neither blindly; verify from source and regenerate the pair.
+8. After editing source, run `project_map_patch` for each changed file.
+9. Before broad architectural claims or final handoff, run `project_map_validate` when freshness matters.
+
+Trust boundary: index routes, map orients, source decides.

 ## role
-Contains historical or deprecated code and resources that are no longer active in the project but retained for reference or backup purposes.
+This is an empty package directory with no files to analyze.
 ## files
 ## arch
-No active architecture; typically flat storage of obsolete files with no dependencies or patterns, isolated from the main codebase.
+N/A - no code or architecture patterns present
 ## tags
 -
 ## symbols
@@ -1,23 +1,23 @@
-# archive/2025-05-17-oauth-traefik-integration (index)
-dir: archive/2025-05-17-oauth-traefik-integration
+# 2025-05-17-oauth-traefik-integration (index)
+dir: 2025-05-17-oauth-traefik-integration

 ## role
-Designs and tracks the integration of a Docker-based application with Traefik reverse proxy and Authentik OAuth through environment-based configuration externalization.
+Infrastructure integration package for deploying a Docker-based application behind an existing Traefik reverse proxy with OAuth authentication via Authentik.
 ## parent
-index: archive/.pi-map.index.md
-map: archive/.pi-map.md
+index: ./.pi-map.index.md
+map: ./.pi-map.md
 ## children
- archive/2025-05-17-oauth-traefik-integration/specs
-  index: archive/2025-05-17-oauth-traefik-integration/specs/.pi-map.index.md
-  map: archive/2025-05-17-oauth-traefik-integration/specs/.pi-map.md
+- 2025-05-17-oauth-traefik-integration/specs
+  index: 2025-05-17-oauth-traefik-integration/specs/.pi-map.index.md
+  map: 2025-05-17-oauth-traefik-integration/specs/.pi-map.md
 ## files
 - .openspec.yaml
 - design.md
 - proposal.md
 - tasks.md
 ## links
-index: archive/2025-05-17-oauth-traefik-integration/.pi-map.index.md
-map: archive/2025-05-17-oauth-traefik-integration/.pi-map.md
+index: 2025-05-17-oauth-traefik-integration/.pi-map.index.md
+map: 2025-05-17-oauth-traefik-integration/.pi-map.md
 ## workflows
 -
 ## dirty
@@ -1,17 +1,17 @@
-# archive/2025-05-17-oauth-traefik-integration
-dir: archive/2025-05-17-oauth-traefik-integration
+# 2025-05-17-oauth-traefik-integration
+dir: 2025-05-17-oauth-traefik-integration

-index: archive/2025-05-17-oauth-traefik-integration/.pi-map.index.md
+index: 2025-05-17-oauth-traefik-integration/.pi-map.index.md

 ## role
-Designs and tracks the integration of a Docker-based application with Traefik reverse proxy and Authentik OAuth through environment-based configuration externalization.
+Infrastructure integration package for deploying a Docker-based application behind an existing Traefik reverse proxy with OAuth authentication via Authentik.
 ## files
 - .openspec.yaml | Defines an OpenAPI specification file metadata with schema type and creation date
 - design.md | Design document for making a Docker-based application deployable behind an existing Traefik reverse proxy by removing hardcoded URLs and adding environment-based configuration | dep: Docker, Docker Compose, Traefik, Authentik, Python (config.py, auth.py), Vite (frontend)
 - proposal.md | Proposes architectural changes to externalize Authentik/domain configuration to environment variables and add Traefik reverse proxy deployment support.
 - tasks.md | A task tracking document for externalizing authentication/domain configuration, creating Traefik deployment, updating frontend config, and running verification tests.
 ## arch
-Documentation-driven design process using markdown specifications with phased task tracking, focusing on 12-factor app configuration principles (env vars over hardcoded values) and reverse proxy deployment patterns.
+Environment-driven configuration pattern replacing hardcoded URLs with externalized variables, plus reverse proxy integration using Traefik labels and Docker Compose deployment orchestration.
 ## tags
 traefik, design, configuration, .openspec, document, docker, reverse, proxy
 ## symbols
@@ -1,25 +1,25 @@
-# archive/2025-05-17-oauth-traefik-integration/specs (index)
-dir: archive/2025-05-17-oauth-traefik-integration/specs
+# 2025-05-17-oauth-traefik-integration/specs (index)
+dir: 2025-05-17-oauth-traefik-integration/specs

 ## role
-Contains specification documents for OAuth-Traefik integration design.
+Contains specification documents and design requirements for the OAuth-Traefik integration feature
 ## parent
-index: archive/2025-05-17-oauth-traefik-integration/.pi-map.index.md
-map: archive/2025-05-17-oauth-traefik-integration/.pi-map.md
+index: 2025-05-17-oauth-traefik-integration/.pi-map.index.md
+map: 2025-05-17-oauth-traefik-integration/.pi-map.md
 ## children
- archive/2025-05-17-oauth-traefik-integration/specs/auth-oauth
-  index: archive/2025-05-17-oauth-traefik-integration/specs/auth-oauth/.pi-map.index.md
-  map: archive/2025-05-17-oauth-traefik-integration/specs/auth-oauth/.pi-map.md
- archive/2025-05-17-oauth-traefik-integration/specs/docker-infrastructure
-  index: archive/2025-05-17-oauth-traefik-integration/specs/docker-infrastructure/.pi-map.index.md
-  map: archive/2025-05-17-oauth-traefik-integration/specs/docker-infrastructure/.pi-map.md
- archive/2025-05-17-oauth-traefik-integration/specs/traefik-deployment
-  index: archive/2025-05-17-oauth-traefik-integration/specs/traefik-deployment/.pi-map.index.md
-  map: archive/2025-05-17-oauth-traefik-integration/specs/traefik-deployment/.pi-map.md
+- 2025-05-17-oauth-traefik-integration/specs/auth-oauth
+  index: 2025-05-17-oauth-traefik-integration/specs/auth-oauth/.pi-map.index.md
+  map: 2025-05-17-oauth-traefik-integration/specs/auth-oauth/.pi-map.md
+- 2025-05-17-oauth-traefik-integration/specs/docker-infrastructure
+  index: 2025-05-17-oauth-traefik-integration/specs/docker-infrastructure/.pi-map.index.md
+  map: 2025-05-17-oauth-traefik-integration/specs/docker-infrastructure/.pi-map.md
+- 2025-05-17-oauth-traefik-integration/specs/traefik-deployment
+  index: 2025-05-17-oauth-traefik-integration/specs/traefik-deployment/.pi-map.index.md
+  map: 2025-05-17-oauth-traefik-integration/specs/traefik-deployment/.pi-map.md
 ## files
 ## links
-index: archive/2025-05-17-oauth-traefik-integration/specs/.pi-map.index.md
-map: archive/2025-05-17-oauth-traefik-integration/specs/.pi-map.md
+index: 2025-05-17-oauth-traefik-integration/specs/.pi-map.index.md
+map: 2025-05-17-oauth-traefik-integration/specs/.pi-map.md
 ## workflows
 -
 ## dirty
@@ -1,13 +1,13 @@
-# archive/2025-05-17-oauth-traefik-integration/specs
-dir: archive/2025-05-17-oauth-traefik-integration/specs
+# 2025-05-17-oauth-traefik-integration/specs
+dir: 2025-05-17-oauth-traefik-integration/specs

-index: archive/2025-05-17-oauth-traefik-integration/specs/.pi-map.index.md
+index: 2025-05-17-oauth-traefik-integration/specs/.pi-map.index.md

 ## role
-Contains specification documents for OAuth-Traefik integration design.
+Contains specification documents and design requirements for the OAuth-Traefik integration feature
 ## files
 ## arch
-Documentation-only package with no code architecture; stores technical specifications and design documents.
+Documentation-driven development with structured specification files (likely markdown/asciidoc) defining system requirements, API contracts, and integration patterns before implementation
 ## tags
 -
 ## symbols
@@ -1,18 +1,18 @@
-# archive/2025-05-17-oauth-traefik-integration/specs/auth-oauth (index)
-dir: archive/2025-05-17-oauth-traefik-integration/specs/auth-oauth
+# 2025-05-17-oauth-traefik-integration/specs/auth-oauth (index)
+dir: 2025-05-17-oauth-traefik-integration/specs/auth-oauth

 ## role
-Defines OAuth2/OIDC authentication requirements using Authentik with session security via httpOnly cookies for the Traefik integration project.
+Defines authentication requirements for OAuth2/OIDC integration with Authentik and secure session management using httpOnly cookies.
 ## parent
-index: archive/2025-05-17-oauth-traefik-integration/specs/.pi-map.index.md
-map: archive/2025-05-17-oauth-traefik-integration/specs/.pi-map.md
+index: 2025-05-17-oauth-traefik-integration/specs/.pi-map.index.md
+map: 2025-05-17-oauth-traefik-integration/specs/.pi-map.md
 ## children
 -
 ## files
 - spec.md
 ## links
-index: archive/2025-05-17-oauth-traefik-integration/specs/auth-oauth/.pi-map.index.md
-map: archive/2025-05-17-oauth-traefik-integration/specs/auth-oauth/.pi-map.md
+index: 2025-05-17-oauth-traefik-integration/specs/auth-oauth/.pi-map.index.md
+map: 2025-05-17-oauth-traefik-integration/specs/auth-oauth/.pi-map.md
 ## workflows
 -
 ## dirty
@@ -1,14 +1,14 @@
-# archive/2025-05-17-oauth-traefik-integration/specs/auth-oauth
-dir: archive/2025-05-17-oauth-traefik-integration/specs/auth-oauth
+# 2025-05-17-oauth-traefik-integration/specs/auth-oauth
+dir: 2025-05-17-oauth-traefik-integration/specs/auth-oauth

-index: archive/2025-05-17-oauth-traefik-integration/specs/auth-oauth/.pi-map.index.md
+index: 2025-05-17-oauth-traefik-integration/specs/auth-oauth/.pi-map.index.md

 ## role
-Defines OAuth2/OIDC authentication requirements using Authentik with session security via httpOnly cookies for the Traefik integration project.
+Defines authentication requirements for OAuth2/OIDC integration with Authentik and secure session management using httpOnly cookies.
 ## files
 - spec.md | Specifies modified requirements for OAuth2/OIDC authentication via Authentik and session security with httpOnly cookies | dep: Authentik, Traefik, OAuth2, OIDC
 ## arch
-Specification-driven requirements document using markdown-based technical specification pattern with security-focused authentication flow definitions.
+Specification-driven architecture with external identity provider delegation, token-based authentication flows, and cookie-based session security patterns.
 ## tags
 oauth2, oidc, authentik, spec, specifies, modified, requirements, authentication
 ## symbols
@@ -1,18 +1,18 @@
-# archive/2025-05-17-oauth-traefik-integration/specs/docker-infrastructure (index)
-dir: archive/2025-05-17-oauth-traefik-integration/specs/docker-infrastructure
+# 2025-05-17-oauth-traefik-integration/specs/docker-infrastructure (index)
+dir: 2025-05-17-oauth-traefik-integration/specs/docker-infrastructure

 ## role
-Defines Docker infrastructure requirements and environment configuration specifications for the OAuth-Traefik integration project using behavior-driven examples.
+Defines Docker infrastructure specifications using behavior-driven development examples to validate environment configuration and service orchestration requirements.
 ## parent
-index: archive/2025-05-17-oauth-traefik-integration/specs/.pi-map.index.md
-map: archive/2025-05-17-oauth-traefik-integration/specs/.pi-map.md
+index: 2025-05-17-oauth-traefik-integration/specs/.pi-map.index.md
+map: 2025-05-17-oauth-traefik-integration/specs/.pi-map.md
 ## children
 -
 ## files
 - spec.md
 ## links
-index: archive/2025-05-17-oauth-traefik-integration/specs/docker-infrastructure/.pi-map.index.md
-map: archive/2025-05-17-oauth-traefik-integration/specs/docker-infrastructure/.pi-map.md
+index: 2025-05-17-oauth-traefik-integration/specs/docker-infrastructure/.pi-map.index.md
+map: 2025-05-17-oauth-traefik-integration/specs/docker-infrastructure/.pi-map.md
 ## workflows
 -
 ## dirty
@@ -1,14 +1,14 @@
-# archive/2025-05-17-oauth-traefik-integration/specs/docker-infrastructure
-dir: archive/2025-05-17-oauth-traefik-integration/specs/docker-infrastructure
+# 2025-05-17-oauth-traefik-integration/specs/docker-infrastructure
+dir: 2025-05-17-oauth-traefik-integration/specs/docker-infrastructure

-index: archive/2025-05-17-oauth-traefik-integration/specs/docker-infrastructure/.pi-map.index.md
+index: 2025-05-17-oauth-traefik-integration/specs/docker-infrastructure/.pi-map.index.md

 ## role
-Defines Docker infrastructure requirements and environment configuration specifications for the OAuth-Traefik integration project using behavior-driven examples.
+Defines Docker infrastructure specifications using behavior-driven development examples to validate environment configuration and service orchestration requirements.
 ## files
 - spec.md | Defines modified requirements for Docker Compose setup and environment configuration using specification by example (Gherkin-style scenarios) | dep: Docker Compose, Traefik
 ## arch
-Specification-by-example pattern with Gherkin-style scenarios documenting Docker Compose setup requirements as executable documentation.
+Specification-by-example pattern with Gherkin-style scenarios for executable requirements, targeting Docker Compose-based infrastructure validation.
 ## tags
 spec, defines, modified, requirements, docker, compose, setup, environment
 ## symbols
@@ -1,18 +1,18 @@
-# archive/2025-05-17-oauth-traefik-integration/specs/traefik-deployment (index)
-dir: archive/2025-05-17-oauth-traefik-integration/specs/traefik-deployment
+# 2025-05-17-oauth-traefik-integration/specs/traefik-deployment (index)
+dir: 2025-05-17-oauth-traefik-integration/specs/traefik-deployment

 ## role
-Defines deployment specifications for Traefik reverse proxy integration with OAuth authentication services
+Defines deployment specifications for Traefik reverse proxy infrastructure in a Docker Compose environment.
 ## parent
-index: archive/2025-05-17-oauth-traefik-integration/specs/.pi-map.index.md
-map: archive/2025-05-17-oauth-traefik-integration/specs/.pi-map.md
+index: 2025-05-17-oauth-traefik-integration/specs/.pi-map.index.md
+map: 2025-05-17-oauth-traefik-integration/specs/.pi-map.md
 ## children
 -
 ## files
 - spec.md
 ## links
-index: archive/2025-05-17-oauth-traefik-integration/specs/traefik-deployment/.pi-map.index.md
-map: archive/2025-05-17-oauth-traefik-integration/specs/traefik-deployment/.pi-map.md
+index: 2025-05-17-oauth-traefik-integration/specs/traefik-deployment/.pi-map.index.md
+map: 2025-05-17-oauth-traefik-integration/specs/traefik-deployment/.pi-map.md
 ## workflows
 -
 ## dirty
@@ -1,14 +1,14 @@
-# archive/2025-05-17-oauth-traefik-integration/specs/traefik-deployment
-dir: archive/2025-05-17-oauth-traefik-integration/specs/traefik-deployment
+# 2025-05-17-oauth-traefik-integration/specs/traefik-deployment
+dir: 2025-05-17-oauth-traefik-integration/specs/traefik-deployment

-index: archive/2025-05-17-oauth-traefik-integration/specs/traefik-deployment/.pi-map.index.md
+index: 2025-05-17-oauth-traefik-integration/specs/traefik-deployment/.pi-map.index.md

 ## role
-Defines deployment specifications for Traefik reverse proxy integration with OAuth authentication services
+Defines deployment specifications for Traefik reverse proxy infrastructure in a Docker Compose environment.
 ## files
 - spec.md | Specifies requirements for Traefik Docker Compose deployment configuration and environment variable documentation | dep: Traefik, Docker Compose, Authentik, OIDC
 ## arch
-Infrastructure-as-documentation pattern using Markdown specification files for declarative container orchestration configuration
+Infrastructure-as-specification pattern using markdown-based requirements documentation for containerized reverse proxy deployment.
 ## tags
 traefik, spec, specifies, requirements, docker, compose, deployment, configuration
 ## symbols
@@ -1,15 +1,15 @@
-# archive/2025-05-17-user-profile (index)
-dir: archive/2025-05-17-user-profile
+# 2025-05-17-user-profile (index)
+dir: 2025-05-17-user-profile

 ## role
-Archive of planning and design documents for an authenticated user profile management feature implementation.
+Design and planning package for an authenticated user profile management feature with read/update endpoints, frontend page, and avatar upload.
 ## parent
-index: archive/.pi-map.index.md
-map: archive/.pi-map.md
+index: ./.pi-map.index.md
+map: ./.pi-map.md
 ## children
- archive/2025-05-17-user-profile/specs
-  index: archive/2025-05-17-user-profile/specs/.pi-map.index.md
-  map: archive/2025-05-17-user-profile/specs/.pi-map.md
+- 2025-05-17-user-profile/specs
+  index: 2025-05-17-user-profile/specs/.pi-map.index.md
+  map: 2025-05-17-user-profile/specs/.pi-map.md
 ## files
 - .openspec.yaml
 - README.md
@@ -17,8 +17,8 @@ map: archive/.pi-map.md
 - proposal.md
 - tasks.md
 ## links
-index: archive/2025-05-17-user-profile/.pi-map.index.md
-map: archive/2025-05-17-user-profile/.pi-map.md
+index: 2025-05-17-user-profile/.pi-map.index.md
+map: 2025-05-17-user-profile/.pi-map.md
 ## workflows
 -
 ## dirty
@@ -1,10 +1,10 @@
-# archive/2025-05-17-user-profile
-dir: archive/2025-05-17-user-profile
+# 2025-05-17-user-profile
+dir: 2025-05-17-user-profile

-index: archive/2025-05-17-user-profile/.pi-map.index.md
+index: 2025-05-17-user-profile/.pi-map.index.md

 ## role
-Archive of planning and design documents for an authenticated user profile management feature implementation.
+Design and planning package for an authenticated user profile management feature with read/update endpoints, frontend page, and avatar upload.
 ## files
 - .openspec.yaml | Defines an OpenAPI specification file metadata with schema type and creation date
 - README.md | Documents the implementation of an authenticated user profile read/update flow across API and frontend
@@ -12,7 +12,7 @@ Archive of planning and design documents for an authenticated user profile manag
 - proposal.md | Proposes implementing authenticated user profile management with read/update endpoints, frontend page, and avatar upload functionality. | dep: apps/api/src/api/, apps/web/src/, auth-oauth, User model
 - tasks.md | Tracks implementation tasks for a user profile feature across backend API and frontend, with completion status and follow-up notes.
 ## arch
-Specification-driven development using OpenAPI standards, with phased task tracking across backend API and frontend layers.
+Specification-driven development using OpenAPI schema definitions, with phased task tracking across backend API and frontend implementation, documented through proposal, design, and task artifacts.
 ## tags
 api, user, profile, frontend, design, tasks, .openspec, implementation
 ## symbols
@@ -1,19 +1,19 @@
-# archive/2025-05-17-user-profile/specs (index)
-dir: archive/2025-05-17-user-profile/specs
+# 2025-05-17-user-profile/specs (index)
+dir: 2025-05-17-user-profile/specs

 ## role
-Contains specification documents for the user profile feature that was archived on May 17, 2025.
+Contains specification documents defining requirements and behavior for the user profile feature.
 ## parent
-index: archive/2025-05-17-user-profile/.pi-map.index.md
-map: archive/2025-05-17-user-profile/.pi-map.md
+index: 2025-05-17-user-profile/.pi-map.index.md
+map: 2025-05-17-user-profile/.pi-map.md
 ## children
- archive/2025-05-17-user-profile/specs/user-profile
-  index: archive/2025-05-17-user-profile/specs/user-profile/.pi-map.index.md
-  map: archive/2025-05-17-user-profile/specs/user-profile/.pi-map.md
+- 2025-05-17-user-profile/specs/user-profile
+  index: 2025-05-17-user-profile/specs/user-profile/.pi-map.index.md
+  map: 2025-05-17-user-profile/specs/user-profile/.pi-map.md
 ## files
 ## links
-index: archive/2025-05-17-user-profile/specs/.pi-map.index.md
-map: archive/2025-05-17-user-profile/specs/.pi-map.md
+index: 2025-05-17-user-profile/specs/.pi-map.index.md
+map: 2025-05-17-user-profile/specs/.pi-map.md
 ## workflows
 -
 ## dirty
@@ -1,13 +1,13 @@
-# archive/2025-05-17-user-profile/specs
-dir: archive/2025-05-17-user-profile/specs
+# 2025-05-17-user-profile/specs
+dir: 2025-05-17-user-profile/specs

-index: archive/2025-05-17-user-profile/specs/.pi-map.index.md
+index: 2025-05-17-user-profile/specs/.pi-map.index.md

 ## role
-Contains specification documents for the user profile feature that was archived on May 17, 2025.
+Contains specification documents defining requirements and behavior for the user profile feature.
 ## files
 ## arch
-N/A (no code files present; directory contains only archived specification documents)
+Documentation-driven specification pattern with date-based versioning for feature scoping.
 ## tags
 -
 ## symbols
@@ -1,18 +1,18 @@
-# archive/2025-05-17-user-profile/specs/user-profile (index)
-dir: archive/2025-05-17-user-profile/specs/user-profile
+# 2025-05-17-user-profile/specs/user-profile (index)
+dir: 2025-05-17-user-profile/specs/user-profile

 ## role
-Defines functional specifications for user profile management capabilities including profile data operations and avatar handling
+Defines functional specifications for a user profile management system including profile retrieval, updates, and local avatar storage
 ## parent
-index: archive/2025-05-17-user-profile/specs/.pi-map.index.md
-map: archive/2025-05-17-user-profile/specs/.pi-map.md
+index: 2025-05-17-user-profile/specs/.pi-map.index.md
+map: 2025-05-17-user-profile/specs/.pi-map.md
 ## children
 -
 ## files
 - spec.md
 ## links
-index: archive/2025-05-17-user-profile/specs/user-profile/.pi-map.index.md
-map: archive/2025-05-17-user-profile/specs/user-profile/.pi-map.md
+index: 2025-05-17-user-profile/specs/user-profile/.pi-map.index.md
+map: 2025-05-17-user-profile/specs/user-profile/.pi-map.md
 ## workflows
 -
 ## dirty
@@ -1,14 +1,14 @@
-# archive/2025-05-17-user-profile/specs/user-profile
-dir: archive/2025-05-17-user-profile/specs/user-profile
+# 2025-05-17-user-profile/specs/user-profile
+dir: 2025-05-17-user-profile/specs/user-profile

-index: archive/2025-05-17-user-profile/specs/user-profile/.pi-map.index.md
+index: 2025-05-17-user-profile/specs/user-profile/.pi-map.index.md

 ## role
-Defines functional specifications for user profile management capabilities including profile data operations and avatar handling
+Defines functional specifications for a user profile management system including profile retrieval, updates, and local avatar storage
 ## files
 - spec.md | Defines functional specifications for a user profile management system including profile retrieval, updates, and local avatar storage | dep: auth-oauth, User database model, pytest, mypy, ruff, npm/typecheck, npm/lint
 ## arch
-Specification-driven design using markdown-based requirements documentation with modular feature decomposition (retrieval, updates, local storage)
+Specification-driven design with markdown-based requirements documentation
 ## tags
 profile, npm, spec, defines, functional, specifications, user, management
 ## symbols
@@ -1,23 +1,23 @@
-# archive/2025-05-18-git-repo-management (index)
-dir: archive/2025-05-18-git-repo-management
+# 2025-05-18-git-repo-management (index)
+dir: 2025-05-18-git-repo-management

 ## role
-Proposes and designs a git repository management feature for projects, including bare repo creation, listing, cloning, and deletion across backend and frontend.
+This package contains design and planning documents for implementing a git repository management feature that enables creating, listing, cloning, and deleting bare git repositories within projects.
 ## parent
-index: archive/.pi-map.index.md
-map: archive/.pi-map.md
+index: ./.pi-map.index.md
+map: ./.pi-map.md
 ## children
- archive/2025-05-18-git-repo-management/specs
-  index: archive/2025-05-18-git-repo-management/specs/.pi-map.index.md
-  map: archive/2025-05-18-git-repo-management/specs/.pi-map.md
+- 2025-05-18-git-repo-management/specs
+  index: 2025-05-18-git-repo-management/specs/.pi-map.index.md
+  map: 2025-05-18-git-repo-management/specs/.pi-map.md
 ## files
 - .openspec.yaml
 - design.md
 - proposal.md
 - tasks.md
 ## links
-index: archive/2025-05-18-git-repo-management/.pi-map.index.md
-map: archive/2025-05-18-git-repo-management/.pi-map.md
+index: 2025-05-18-git-repo-management/.pi-map.index.md
+map: 2025-05-18-git-repo-management/.pi-map.md
 ## workflows
 -
 ## dirty
@@ -1,17 +1,17 @@
-# archive/2025-05-18-git-repo-management
-dir: archive/2025-05-18-git-repo-management
+# 2025-05-18-git-repo-management
+dir: 2025-05-18-git-repo-management

-index: archive/2025-05-18-git-repo-management/.pi-map.index.md
+index: 2025-05-18-git-repo-management/.pi-map.index.md

 ## role
-Proposes and designs a git repository management feature for projects, including bare repo creation, listing, cloning, and deletion across backend and frontend.
+This package contains design and planning documents for implementing a git repository management feature that enables creating, listing, cloning, and deleting bare git repositories within projects.
 ## files
 - .openspec.yaml | Defines an OpenSpec configuration file with schema type and creation date metadata
 - design.md | Design document specifying a bare git repository management system for projects with create/list/clone/delete operations | dep: git, filesystem, database, API, Dockerfile
 - proposal.md | Proposes a feature to add git repository creation, cloning, and management capabilities within existing projects | dep: project-management, git, backend API, frontend UI, disk storage
 - tasks.md | Project task checklist tracking implementation of a Git repository management feature across backend API, frontend UI, and project integration with verification steps.
 ## arch
-Specification-driven development using OpenSpec schema configuration, phased task tracking with verification gates, and layered documentation (proposal → design → implementation tasks).
+Documentation-driven specification pattern using layered design docs (proposal → design → tasks → API spec) to formally define requirements before implementation, with clear separation between backend API, frontend UI, and project integration concerns.
 ## tags
 git, management, design, repository, project, creation, .openspec, projects
 ## symbols
@@ -1,19 +1,19 @@
-# archive/2025-05-18-git-repo-management/specs (index)
-dir: archive/2025-05-18-git-repo-management/specs
+# 2025-05-18-git-repo-management/specs (index)
+dir: 2025-05-18-git-repo-management/specs

 ## role
-Defines specifications and requirements for git repository management functionality.
+Contains specification documents that define requirements, standards, or design contracts for the git repository management project.
 ## parent
-index: archive/2025-05-18-git-repo-management/.pi-map.index.md
-map: archive/2025-05-18-git-repo-management/.pi-map.md
+index: 2025-05-18-git-repo-management/.pi-map.index.md
+map: 2025-05-18-git-repo-management/.pi-map.md
 ## children
- archive/2025-05-18-git-repo-management/specs/git-repo-management
-  index: archive/2025-05-18-git-repo-management/specs/git-repo-management/.pi-map.index.md
-  map: archive/2025-05-18-git-repo-management/specs/git-repo-management/.pi-map.md
+- 2025-05-18-git-repo-management/specs/git-repo-management
+  index: 2025-05-18-git-repo-management/specs/git-repo-management/.pi-map.index.md
+  map: 2025-05-18-git-repo-management/specs/git-repo-management/.pi-map.md
 ## files
 ## links
-index: archive/2025-05-18-git-repo-management/specs/.pi-map.index.md
-map: archive/2025-05-18-git-repo-management/specs/.pi-map.md
+index: 2025-05-18-git-repo-management/specs/.pi-map.index.md
+map: 2025-05-18-git-repo-management/specs/.pi-map.md
 ## workflows
 -
 ## dirty
@@ -1,13 +1,13 @@
-# archive/2025-05-18-git-repo-management/specs
-dir: archive/2025-05-18-git-repo-management/specs
+# 2025-05-18-git-repo-management/specs
+dir: 2025-05-18-git-repo-management/specs

-index: archive/2025-05-18-git-repo-management/specs/.pi-map.index.md
+index: 2025-05-18-git-repo-management/specs/.pi-map.index.md

 ## role
-Defines specifications and requirements for git repository management functionality.
+Contains specification documents that define requirements, standards, or design contracts for the git repository management project.
 ## files
 ## arch
-Specification-driven development with structured documentation files (likely markdown or similar) capturing functional requirements, API contracts, and behavioral expectations for the git repo management system.
+Documentation-driven architecture using specification files (likely markdown or structured text) to establish formal contracts before implementation, supporting design-first or contract-first development patterns.
 ## tags
 -
 ## symbols
@@ -1,18 +1,18 @@
-# archive/2025-05-18-git-repo-management/specs/git-repo-management (index)
-dir: archive/2025-05-18-git-repo-management/specs/git-repo-management
+# 2025-05-18-git-repo-management/specs/git-repo-management (index)
+dir: 2025-05-18-git-repo-management/specs/git-repo-management

 ## role
-Defines functional requirements for a Git repository management system supporting CRUD operations with cascade deletion capabilities.
+Defines functional requirements for a Git repository management system supporting lifecycle operations.
 ## parent
-index: archive/2025-05-18-git-repo-management/specs/.pi-map.index.md
-map: archive/2025-05-18-git-repo-management/specs/.pi-map.md
+index: 2025-05-18-git-repo-management/specs/.pi-map.index.md
+map: 2025-05-18-git-repo-management/specs/.pi-map.md
 ## children
 -
 ## files
 - spec.md
 ## links
-index: archive/2025-05-18-git-repo-management/specs/git-repo-management/.pi-map.index.md
-map: archive/2025-05-18-git-repo-management/specs/git-repo-management/.pi-map.md
+index: 2025-05-18-git-repo-management/specs/git-repo-management/.pi-map.index.md
+map: 2025-05-18-git-repo-management/specs/git-repo-management/.pi-map.md
 ## workflows
 -
 ## dirty
@@ -1,14 +1,14 @@
-# archive/2025-05-18-git-repo-management/specs/git-repo-management
-dir: archive/2025-05-18-git-repo-management/specs/git-repo-management
+# 2025-05-18-git-repo-management/specs/git-repo-management
+dir: 2025-05-18-git-repo-management/specs/git-repo-management

-index: archive/2025-05-18-git-repo-management/specs/git-repo-management/.pi-map.index.md
+index: 2025-05-18-git-repo-management/specs/git-repo-management/.pi-map.index.md

 ## role
-Defines functional requirements for a Git repository management system supporting CRUD operations with cascade deletion capabilities.
+Defines functional requirements for a Git repository management system supporting lifecycle operations.
 ## files
 - spec.md | This file specifies software requirements for a Git repository management system, including creation, cloning, listing, deletion, and cascade deletion features. | dep: git, database, filesystem, HTTP API
 ## arch
-Specification-driven design using a single markdown-based requirements document without explicit architectural patterns.
+Specification-driven design using a single requirements document with feature-based organization (CRUD + cascade operations).
 ## tags
 git, deletion, spec, specifies, software, requirements, repository, management
 ## symbols
@@ -1,23 +1,23 @@
-# archive/2025-05-18-ssh-key-management (index)
-dir: archive/2025-05-18-ssh-key-management
+# 2025-05-18-ssh-key-management (index)
+dir: 2025-05-18-ssh-key-management

 ## role
-Implements a full-stack SSH key management feature for secure Ed25519 key generation, encrypted storage, and git operations with external providers.
+Implements a full-stack SSH key management system for secure Ed25519 key generation, encrypted storage, and git operations with external providers.
 ## parent
-index: archive/.pi-map.index.md
-map: archive/.pi-map.md
+index: ./.pi-map.index.md
+map: ./.pi-map.md
 ## children
- archive/2025-05-18-ssh-key-management/specs
-  index: archive/2025-05-18-ssh-key-management/specs/.pi-map.index.md
-  map: archive/2025-05-18-ssh-key-management/specs/.pi-map.md
+- 2025-05-18-ssh-key-management/specs
+  index: 2025-05-18-ssh-key-management/specs/.pi-map.index.md
+  map: 2025-05-18-ssh-key-management/specs/.pi-map.md
 ## files
 - .openspec.yaml
 - design.md
 - proposal.md
 - tasks.md
 ## links
-index: archive/2025-05-18-ssh-key-management/.pi-map.index.md
-map: archive/2025-05-18-ssh-key-management/.pi-map.md
+index: 2025-05-18-ssh-key-management/.pi-map.index.md
+map: 2025-05-18-ssh-key-management/.pi-map.md
 ## workflows
 -
 ## dirty
@@ -1,17 +1,17 @@
-# archive/2025-05-18-ssh-key-management
-dir: archive/2025-05-18-ssh-key-management
+# 2025-05-18-ssh-key-management
+dir: 2025-05-18-ssh-key-management

-index: archive/2025-05-18-ssh-key-management/.pi-map.index.md
+index: 2025-05-18-ssh-key-management/.pi-map.index.md

 ## role
-Implements a full-stack SSH key management feature for secure Ed25519 key generation, encrypted storage, and git operations with external providers.
+Implements a full-stack SSH key management system for secure Ed25519 key generation, encrypted storage, and git operations with external providers.
 ## files
 - .openspec.yaml | Defines an OpenSpec configuration file with schema type and creation date metadata
 - design.md | Design document for implementing an API and UI to manage Ed25519 SSH keys with encrypted private key storage | dep: cryptography (Fernet, Ed25519), database/SSHKey model, frontend UI components, JWT_SECRET (for Fernet key derivation)
 - proposal.md | Proposes adding SSH key management functionality (backend API, frontend UI, and Ed25519 key generation with encryption) to enable git operations with external providers. | dep: FastAPI (implied by router pattern), Fernet encryption, Ed25519 cryptography, React/Vue frontend (implied by web app), existing SSHKey model
 - tasks.md | A completed task checklist documenting the implementation of a full-stack SSH key management feature with backend API, frontend UI, and verification steps. | dep: FastAPI, cryptography, Pydantic, React, React Router, npm, pytest, ruff, mypy
 ## arch
-Clean documentation-driven architecture using OpenSpec schema configuration, phased implementation (proposal → design → tasks), with separated backend API and frontend UI concerns and encrypted private key security pattern.
+Full-stack feature module with backend REST API, frontend UI, encrypted private key storage, and task-driven implementation documentation following design-proposal-tasks workflow.
 ## tags
 key, design, api, ssh, .openspec, ed25519, management, backend
 ## symbols
@@ -1,19 +1,19 @@
-# archive/2025-05-18-ssh-key-management/specs (index)
-dir: archive/2025-05-18-ssh-key-management/specs
+# 2025-05-18-ssh-key-management/specs (index)
+dir: 2025-05-18-ssh-key-management/specs

 ## role
-Contains archived specifications for SSH key management features from May 18, 2025.
+Contains specification documents defining requirements and design for SSH key management functionality.
 ## parent
-index: archive/2025-05-18-ssh-key-management/.pi-map.index.md
-map: archive/2025-05-18-ssh-key-management/.pi-map.md
+index: 2025-05-18-ssh-key-management/.pi-map.index.md
+map: 2025-05-18-ssh-key-management/.pi-map.md
 ## children
- archive/2025-05-18-ssh-key-management/specs/ssh-key-management
-  index: archive/2025-05-18-ssh-key-management/specs/ssh-key-management/.pi-map.index.md
-  map: archive/2025-05-18-ssh-key-management/specs/ssh-key-management/.pi-map.md
+- 2025-05-18-ssh-key-management/specs/ssh-key-management
+  index: 2025-05-18-ssh-key-management/specs/ssh-key-management/.pi-map.index.md
+  map: 2025-05-18-ssh-key-management/specs/ssh-key-management/.pi-map.md
 ## files
 ## links
-index: archive/2025-05-18-ssh-key-management/specs/.pi-map.index.md
-map: archive/2025-05-18-ssh-key-management/specs/.pi-map.md
+index: 2025-05-18-ssh-key-management/specs/.pi-map.index.md
+map: 2025-05-18-ssh-key-management/specs/.pi-map.md
 ## workflows
 -
 ## dirty
@@ -1,13 +1,13 @@
-# archive/2025-05-18-ssh-key-management/specs
-dir: archive/2025-05-18-ssh-key-management/specs
+# 2025-05-18-ssh-key-management/specs
+dir: 2025-05-18-ssh-key-management/specs

-index: archive/2025-05-18-ssh-key-management/specs/.pi-map.index.md
+index: 2025-05-18-ssh-key-management/specs/.pi-map.index.md

 ## role
-Contains archived specifications for SSH key management features from May 18, 2025.
+Contains specification documents defining requirements and design for SSH key management functionality.
 ## files
 ## arch
-Document-based specification storage with date-versioned archiving pattern for historical feature planning documents.
+Documentation-driven specification pattern using dated directory organization for version tracking of feature requirements.
 ## tags
 -
 ## symbols
@@ -1,18 +1,18 @@
-# archive/2025-05-18-ssh-key-management/specs/ssh-key-management (index)
-dir: archive/2025-05-18-ssh-key-management/specs/ssh-key-management
+# 2025-05-18-ssh-key-management/specs/ssh-key-management (index)
+dir: 2025-05-18-ssh-key-management/specs/ssh-key-management

 ## role
-Defines functional requirements and acceptance criteria for SSH key lifecycle management operations.
+Defines functional requirements and specifications for SSH key lifecycle management operations.
 ## parent
-index: archive/2025-05-18-ssh-key-management/specs/.pi-map.index.md
-map: archive/2025-05-18-ssh-key-management/specs/.pi-map.md
+index: 2025-05-18-ssh-key-management/specs/.pi-map.index.md
+map: 2025-05-18-ssh-key-management/specs/.pi-map.md
 ## children
 -
 ## files
 - spec.md
 ## links
-index: archive/2025-05-18-ssh-key-management/specs/ssh-key-management/.pi-map.index.md
-map: archive/2025-05-18-ssh-key-management/specs/ssh-key-management/.pi-map.md
+index: 2025-05-18-ssh-key-management/specs/ssh-key-management/.pi-map.index.md
+map: 2025-05-18-ssh-key-management/specs/ssh-key-management/.pi-map.md
 ## workflows
 -
 ## dirty
@@ -1,14 +1,14 @@
-# archive/2025-05-18-ssh-key-management/specs/ssh-key-management
-dir: archive/2025-05-18-ssh-key-management/specs/ssh-key-management
+# 2025-05-18-ssh-key-management/specs/ssh-key-management
+dir: 2025-05-18-ssh-key-management/specs/ssh-key-management

-index: archive/2025-05-18-ssh-key-management/specs/ssh-key-management/.pi-map.index.md
+index: 2025-05-18-ssh-key-management/specs/ssh-key-management/.pi-map.index.md

 ## role
-Defines functional requirements and acceptance criteria for SSH key lifecycle management operations.
+Defines functional requirements and specifications for SSH key lifecycle management operations.
 ## files
 - spec.md | Defines requirements for SSH key management functionality including generation, listing, display, and deletion
 ## arch
-Specification-driven design using structured requirements documentation with use-case based organization (generate, list, show, delete) and explicit acceptance criteria.
+Specification-driven design using requirement documents to define system behavior before implementation.
 ## tags
 spec, defines, requirements, ssh, key, management, functionality, including
 ## symbols
@@ -1,23 +1,23 @@
-# archive/2025-05-18-test-infrastructure-improvements (index)
-dir: archive/2025-05-18-test-infrastructure-improvements
+# 2025-05-18-test-infrastructure-improvements (index)
+dir: 2025-05-18-test-infrastructure-improvements

 ## role
-Contains design documents, proposals, and task tracking for a test infrastructure restructuring initiative that was archived after completion.
+Documents the planning, design, and tracking of test infrastructure improvements for a backend API project.
 ## parent
-index: archive/.pi-map.index.md
-map: archive/.pi-map.md
+index: ./.pi-map.index.md
+map: ./.pi-map.md
 ## children
- archive/2025-05-18-test-infrastructure-improvements/specs
-  index: archive/2025-05-18-test-infrastructure-improvements/specs/.pi-map.index.md
-  map: archive/2025-05-18-test-infrastructure-improvements/specs/.pi-map.md
+- 2025-05-18-test-infrastructure-improvements/specs
+  index: 2025-05-18-test-infrastructure-improvements/specs/.pi-map.index.md
+  map: 2025-05-18-test-infrastructure-improvements/specs/.pi-map.md
 ## files
 - .openspec.yaml
 - design.md
 - proposal.md
 - tasks.md
 ## links
-index: archive/2025-05-18-test-infrastructure-improvements/.pi-map.index.md
-map: archive/2025-05-18-test-infrastructure-improvements/.pi-map.md
+index: 2025-05-18-test-infrastructure-improvements/.pi-map.index.md
+map: 2025-05-18-test-infrastructure-improvements/.pi-map.md
 ## workflows
 -
 ## dirty
@@ -1,17 +1,17 @@
-# archive/2025-05-18-test-infrastructure-improvements
-dir: archive/2025-05-18-test-infrastructure-improvements
+# 2025-05-18-test-infrastructure-improvements
+dir: 2025-05-18-test-infrastructure-improvements

-index: archive/2025-05-18-test-infrastructure-improvements/.pi-map.index.md
+index: 2025-05-18-test-infrastructure-improvements/.pi-map.index.md

 ## role
-Contains design documents, proposals, and task tracking for a test infrastructure restructuring initiative that was archived after completion.
+Documents the planning, design, and tracking of test infrastructure improvements for a backend API project.
 ## files
 - .openspec.yaml | Defines an OpenSpec configuration file with schema type and creation date metadata
 - design.md | This file documents the design and migration plan for restructuring a test suite into unit, integration, and system categories with shared fixtures, SQLite/PostgreSQL separation, and E2E coverage. | dep: pytest, pytest-asyncio, SQLite, PostgreSQL, Playwright, Docker, React/Vite, asyncpg, pytest-xdist
 - proposal.md | Proposes a comprehensive restructuring of test infrastructure to separate unit/integration/system tests, add shared fixtures, enable SQLite for unit tests, implement transaction rollback isolation, and introduce Playwright E2E testing. | dep: pytest, PostgreSQL, SQLite, Playwright, python-jose, docker, Makefile
 - tasks.md | Project task list tracking completed testing infrastructure improvements for a backend API project including test restructuring, shared fixtures, multi-database support, E2E setup, and documentation. | dep: pytest, pytest-asyncio, SQLAlchemy, aiosqlite, PostgreSQL, Playwright, python-jose, TestClient, Makefile
 ## arch
-Documentation-driven planning pattern with structured design docs (design.md, proposal.md) preceding implementation, tracked via task lists, using OpenSpec for schema metadata and following a test pyramid architecture (unit/integration/system/E2E tiers with shared fixtures and database isolation).
+Documentation-driven project management using structured markdown files (proposal → design → tasks) with OpenSpec metadata, following a waterfall-like planning pattern for test suite restructuring across unit/integration/system/E2E layers.
 ## tags
 pytest, sqlite, postgresql, playwright, design, restructuring, test, unit
 ## symbols
@@ -1,25 +1,25 @@
-# archive/2025-05-18-test-infrastructure-improvements/specs (index)
-dir: archive/2025-05-18-test-infrastructure-improvements/specs
+# 2025-05-18-test-infrastructure-improvements/specs (index)
+dir: 2025-05-18-test-infrastructure-improvements/specs

 ## role
-Contains specification documents for test infrastructure improvements planned or implemented on 2025-05-18.
+Contains specification documents defining requirements and design for test infrastructure improvements
 ## parent
-index: archive/2025-05-18-test-infrastructure-improvements/.pi-map.index.md
-map: archive/2025-05-18-test-infrastructure-improvements/.pi-map.md
+index: 2025-05-18-test-infrastructure-improvements/.pi-map.index.md
+map: 2025-05-18-test-infrastructure-improvements/.pi-map.md
 ## children
- archive/2025-05-18-test-infrastructure-improvements/specs/e2e-testing
-  index: archive/2025-05-18-test-infrastructure-improvements/specs/e2e-testing/.pi-map.index.md
-  map: archive/2025-05-18-test-infrastructure-improvements/specs/e2e-testing/.pi-map.md
- archive/2025-05-18-test-infrastructure-improvements/specs/test-isolation
-  index: archive/2025-05-18-test-infrastructure-improvements/specs/test-isolation/.pi-map.index.md
-  map: archive/2025-05-18-test-infrastructure-improvements/specs/test-isolation/.pi-map.md
- archive/2025-05-18-test-infrastructure-improvements/specs/test-organization
-  index: archive/2025-05-18-test-infrastructure-improvements/specs/test-organization/.pi-map.index.md
-  map: archive/2025-05-18-test-infrastructure-improvements/specs/test-organization/.pi-map.md
+- 2025-05-18-test-infrastructure-improvements/specs/e2e-testing
+  index: 2025-05-18-test-infrastructure-improvements/specs/e2e-testing/.pi-map.index.md
+  map: 2025-05-18-test-infrastructure-improvements/specs/e2e-testing/.pi-map.md
+- 2025-05-18-test-infrastructure-improvements/specs/test-isolation
+  index: 2025-05-18-test-infrastructure-improvements/specs/test-isolation/.pi-map.index.md
+  map: 2025-05-18-test-infrastructure-improvements/specs/test-isolation/.pi-map.md
+- 2025-05-18-test-infrastructure-improvements/specs/test-organization
+  index: 2025-05-18-test-infrastructure-improvements/specs/test-organization/.pi-map.index.md
+  map: 2025-05-18-test-infrastructure-improvements/specs/test-organization/.pi-map.md
 ## files
 ## links
-index: archive/2025-05-18-test-infrastructure-improvements/specs/.pi-map.index.md
-map: archive/2025-05-18-test-infrastructure-improvements/specs/.pi-map.md
+index: 2025-05-18-test-infrastructure-improvements/specs/.pi-map.index.md
+map: 2025-05-18-test-infrastructure-improvements/specs/.pi-map.md
 ## workflows
 -
 ## dirty
@@ -1,13 +1,13 @@
-# archive/2025-05-18-test-infrastructure-improvements/specs
-dir: archive/2025-05-18-test-infrastructure-improvements/specs
+# 2025-05-18-test-infrastructure-improvements/specs
+dir: 2025-05-18-test-infrastructure-improvements/specs

-index: archive/2025-05-18-test-infrastructure-improvements/specs/.pi-map.index.md
+index: 2025-05-18-test-infrastructure-improvements/specs/.pi-map.index.md

 ## role
-Contains specification documents for test infrastructure improvements planned or implemented on 2025-05-18.
+Contains specification documents defining requirements and design for test infrastructure improvements
 ## files
 ## arch
-Documentation-driven specification pattern with dated archival organization for tracking infrastructure changes over time.
+Documentation-as-code pattern using dated directories for versioned specification tracking
 ## tags
 -
 ## symbols
@@ -1,18 +1,18 @@
-# archive/2025-05-18-test-infrastructure-improvements/specs/e2e-testing (index)
-dir: archive/2025-05-18-test-infrastructure-improvements/specs/e2e-testing
+# 2025-05-18-test-infrastructure-improvements/specs/e2e-testing (index)
+dir: 2025-05-18-test-infrastructure-improvements/specs/e2e-testing

 ## role
-Defines specifications for end-to-end testing infrastructure using Playwright and Makefile integration.
+Defines end-to-end testing requirements using Playwright and Makefile integration for automated browser-based system validation.
 ## parent
-index: archive/2025-05-18-test-infrastructure-improvements/specs/.pi-map.index.md
-map: archive/2025-05-18-test-infrastructure-improvements/specs/.pi-map.md
+index: 2025-05-18-test-infrastructure-improvements/specs/.pi-map.index.md
+map: 2025-05-18-test-infrastructure-improvements/specs/.pi-map.md
 ## children
 -
 ## files
 - spec.md
 ## links
-index: archive/2025-05-18-test-infrastructure-improvements/specs/e2e-testing/.pi-map.index.md
-map: archive/2025-05-18-test-infrastructure-improvements/specs/e2e-testing/.pi-map.md
+index: 2025-05-18-test-infrastructure-improvements/specs/e2e-testing/.pi-map.index.md
+map: 2025-05-18-test-infrastructure-improvements/specs/e2e-testing/.pi-map.md
 ## workflows
 -
 ## dirty
@@ -1,14 +1,14 @@
-# archive/2025-05-18-test-infrastructure-improvements/specs/e2e-testing
-dir: archive/2025-05-18-test-infrastructure-improvements/specs/e2e-testing
+# 2025-05-18-test-infrastructure-improvements/specs/e2e-testing
+dir: 2025-05-18-test-infrastructure-improvements/specs/e2e-testing

-index: archive/2025-05-18-test-infrastructure-improvements/specs/e2e-testing/.pi-map.index.md
+index: 2025-05-18-test-infrastructure-improvements/specs/e2e-testing/.pi-map.index.md

 ## role
-Defines specifications for end-to-end testing infrastructure using Playwright and Makefile integration.
+Defines end-to-end testing requirements using Playwright and Makefile integration for automated browser-based system validation.
 ## files
 - spec.md | Defines requirements for end-to-end testing with Playwright and Makefile test targets for a software system. | dep: Playwright, Makefile, test database
 ## arch
-Specification-driven testing architecture with browser automation (Playwright) and build system (Makefile) orchestration for test execution.
+Specification-driven testing architecture with Makefile target orchestration and Playwright-based browser automation framework.
 ## tags
 end, playwright, makefile, spec, defines, requirements, testing, test
 ## symbols
@@ -1,18 +1,18 @@
-# archive/2025-05-18-test-infrastructure-improvements/specs/test-isolation (index)
-dir: archive/2025-05-18-test-infrastructure-improvements/specs/test-isolation
+# 2025-05-18-test-infrastructure-improvements/specs/test-isolation (index)
+dir: 2025-05-18-test-infrastructure-improvements/specs/test-isolation

 ## role
-Defines specifications for test isolation mechanisms ensuring clean, independent test execution through shared fixtures and transaction management.
+Defines requirements for ensuring test isolation through shared fixtures and database transaction management in a testing infrastructure.
 ## parent
-index: archive/2025-05-18-test-infrastructure-improvements/specs/.pi-map.index.md
-map: archive/2025-05-18-test-infrastructure-improvements/specs/.pi-map.md
+index: 2025-05-18-test-infrastructure-improvements/specs/.pi-map.index.md
+map: 2025-05-18-test-infrastructure-improvements/specs/.pi-map.md
 ## children
 -
 ## files
 - spec.md
 ## links
-index: archive/2025-05-18-test-infrastructure-improvements/specs/test-isolation/.pi-map.index.md
-map: archive/2025-05-18-test-infrastructure-improvements/specs/test-isolation/.pi-map.md
+index: 2025-05-18-test-infrastructure-improvements/specs/test-isolation/.pi-map.index.md
+map: 2025-05-18-test-infrastructure-improvements/specs/test-isolation/.pi-map.md
 ## workflows
 -
 ## dirty
@@ -1,14 +1,14 @@
-# archive/2025-05-18-test-infrastructure-improvements/specs/test-isolation
-dir: archive/2025-05-18-test-infrastructure-improvements/specs/test-isolation
+# 2025-05-18-test-infrastructure-improvements/specs/test-isolation
+dir: 2025-05-18-test-infrastructure-improvements/specs/test-isolation

-index: archive/2025-05-18-test-infrastructure-improvements/specs/test-isolation/.pi-map.index.md
+index: 2025-05-18-test-infrastructure-improvements/specs/test-isolation/.pi-map.index.md

 ## role
-Defines specifications for test isolation mechanisms ensuring clean, independent test execution through shared fixtures and transaction management.
+Defines requirements for ensuring test isolation through shared fixtures and database transaction management in a testing infrastructure.
 ## files
 - spec.md | Defines requirements for shared test fixtures and transaction isolation in a testing infrastructure | dep: pytest, SQLAlchemy, TestClient, SQLite, PostgreSQL
 ## arch
-Specification-driven design using requirement documents to define behavioral contracts for test infrastructure components.
+Specification-driven architecture using markdown-based requirements documents to define behavioral contracts for test infrastructure components.
 ## tags
 spec, defines, requirements, shared, test, fixtures, transaction, isolation
 ## symbols
@@ -1,18 +1,18 @@
-# archive/2025-05-18-test-infrastructure-improvements/specs/test-organization (index)
-dir: archive/2025-05-18-test-infrastructure-improvements/specs/test-organization
+# 2025-05-18-test-infrastructure-improvements/specs/test-organization (index)
+dir: 2025-05-18-test-infrastructure-improvements/specs/test-organization

 ## role
-Defines testing standards for categorizing backend tests by scope using pytest markers
+Defines testing standards and categorization requirements for the backend test suite using pytest markers.
 ## parent
-index: archive/2025-05-18-test-infrastructure-improvements/specs/.pi-map.index.md
-map: archive/2025-05-18-test-infrastructure-improvements/specs/.pi-map.md
+index: 2025-05-18-test-infrastructure-improvements/specs/.pi-map.index.md
+map: 2025-05-18-test-infrastructure-improvements/specs/.pi-map.md
 ## children
 -
 ## files
 - spec.md
 ## links
-index: archive/2025-05-18-test-infrastructure-improvements/specs/test-organization/.pi-map.index.md
-map: archive/2025-05-18-test-infrastructure-improvements/specs/test-organization/.pi-map.md
+index: 2025-05-18-test-infrastructure-improvements/specs/test-organization/.pi-map.index.md
+map: 2025-05-18-test-infrastructure-improvements/specs/test-organization/.pi-map.md
 ## workflows
 -
 ## dirty
@@ -1,14 +1,14 @@
-# archive/2025-05-18-test-infrastructure-improvements/specs/test-organization
-dir: archive/2025-05-18-test-infrastructure-improvements/specs/test-organization
+# 2025-05-18-test-infrastructure-improvements/specs/test-organization
+dir: 2025-05-18-test-infrastructure-improvements/specs/test-organization

-index: archive/2025-05-18-test-infrastructure-improvements/specs/test-organization/.pi-map.index.md
+index: 2025-05-18-test-infrastructure-improvements/specs/test-organization/.pi-map.index.md

 ## role
-Defines testing standards for categorizing backend tests by scope using pytest markers
+Defines testing standards and categorization requirements for the backend test suite using pytest markers.
 ## files
 - spec.md | Defines requirements for organizing backend tests into unit, integration, and system categories with pytest markers | dep: pytest, pyproject.toml, apps/api/tests/
 ## arch
-Specification-driven testing strategy with hierarchical test classification (unit/integration/system) and marker-based test selection
+Specification-driven documentation pattern establishing a three-tier test hierarchy (unit/integration/system) with marker-based test organization.
 ## tags
 tests, pytest, spec, defines, requirements, organizing, backend, unit
 ## symbols
@@ -1,23 +1,23 @@
-# archive/2025-05-18-tool-types-definition (index)
-dir: archive/2025-05-18-tool-types-definition
+# 2025-05-18-tool-types-definition (index)
+dir: 2025-05-18-tool-types-definition

 ## role
 Design and planning package for a ToolType system that enables defining and launching development tools via Docker Compose templates.
 ## parent
-index: archive/.pi-map.index.md
-map: archive/.pi-map.md
+index: ./.pi-map.index.md
+map: ./.pi-map.md
 ## children
- archive/2025-05-18-tool-types-definition/specs
-  index: archive/2025-05-18-tool-types-definition/specs/.pi-map.index.md
-  map: archive/2025-05-18-tool-types-definition/specs/.pi-map.md
+- 2025-05-18-tool-types-definition/specs
+  index: 2025-05-18-tool-types-definition/specs/.pi-map.index.md
+  map: 2025-05-18-tool-types-definition/specs/.pi-map.md
 ## files
 - .openspec.yaml
 - design.md
 - proposal.md
 - tasks.md
 ## links
-index: archive/2025-05-18-tool-types-definition/.pi-map.index.md
-map: archive/2025-05-18-tool-types-definition/.pi-map.md
+index: 2025-05-18-tool-types-definition/.pi-map.index.md
+map: 2025-05-18-tool-types-definition/.pi-map.md
 ## workflows
 -
 ## dirty
@@ -1,7 +1,7 @@
-# archive/2025-05-18-tool-types-definition
-dir: archive/2025-05-18-tool-types-definition
+# 2025-05-18-tool-types-definition
+dir: 2025-05-18-tool-types-definition

-index: archive/2025-05-18-tool-types-definition/.pi-map.index.md
+index: 2025-05-18-tool-types-definition/.pi-map.index.md

 ## role
 Design and planning package for a ToolType system that enables defining and launching development tools via Docker Compose templates.
@@ -11,7 +11,7 @@ Design and planning package for a ToolType system that enables defining and laun
 - proposal.md | Defines a feature proposal for implementing a tool type system with Docker Compose template support to enable launching development tool instances | dep: SQLAlchemy, Docker Compose, apps/api/src/api/tool_types.py, apps/web/src/pages/tool-types.tsx
 - tasks.md | Tracks completed development tasks for implementing a ToolType CRUD feature across backend API, frontend UI, and database migration | dep: SQLAlchemy, Alembic, FastAPI, Pydantic, React/TypeScript, pytest, ruff, mypy, npm
 ## arch
-Documentation-driven design pattern with structured specification files (OpenSpec config, design doc, proposal, task tracking) preceding implementation.
+Documentation-driven specification pattern using OpenSpec schema configuration, layered design docs (proposal → design → tasks), and CRUD-focused implementation planning across full stack (API/UI/database).
 ## tags
 defines, design, implementing, development, proposal, tool, api, tasks
 ## symbols
@@ -1,19 +1,19 @@
-# archive/2025-05-18-tool-types-definition/specs (index)
-dir: archive/2025-05-18-tool-types-definition/specs
+# 2025-05-18-tool-types-definition/specs (index)
+dir: 2025-05-18-tool-types-definition/specs

 ## role
-Contains specification documents defining tool types and their interfaces for the project.
+Contains specification documents defining tool types, interfaces, and behavioral contracts for the project's tooling system.
 ## parent
-index: archive/2025-05-18-tool-types-definition/.pi-map.index.md
-map: archive/2025-05-18-tool-types-definition/.pi-map.md
+index: 2025-05-18-tool-types-definition/.pi-map.index.md
+map: 2025-05-18-tool-types-definition/.pi-map.md
 ## children
- archive/2025-05-18-tool-types-definition/specs/tool-types-definition
-  index: archive/2025-05-18-tool-types-definition/specs/tool-types-definition/.pi-map.index.md
-  map: archive/2025-05-18-tool-types-definition/specs/tool-types-definition/.pi-map.md
+- 2025-05-18-tool-types-definition/specs/tool-types-definition
+  index: 2025-05-18-tool-types-definition/specs/tool-types-definition/.pi-map.index.md
+  map: 2025-05-18-tool-types-definition/specs/tool-types-definition/.pi-map.md
 ## files
 ## links
-index: archive/2025-05-18-tool-types-definition/specs/.pi-map.index.md
-map: archive/2025-05-18-tool-types-definition/specs/.pi-map.md
+index: 2025-05-18-tool-types-definition/specs/.pi-map.index.md
+map: 2025-05-18-tool-types-definition/specs/.pi-map.md
 ## workflows
 -
 ## dirty
@@ -1,13 +1,13 @@
-# archive/2025-05-18-tool-types-definition/specs
-dir: archive/2025-05-18-tool-types-definition/specs
+# 2025-05-18-tool-types-definition/specs
+dir: 2025-05-18-tool-types-definition/specs

-index: archive/2025-05-18-tool-types-definition/specs/.pi-map.index.md
+index: 2025-05-18-tool-types-definition/specs/.pi-map.index.md

 ## role
-Contains specification documents defining tool types and their interfaces for the project.
+Contains specification documents defining tool types, interfaces, and behavioral contracts for the project's tooling system.
 ## files
 ## arch
-Documentation-driven specification pattern using structured definition files to establish contracts before implementation.
+Document-driven specification pattern using formal interface definitions to establish contracts between tool implementations and consumers, likely supporting code generation or validation.
 ## tags
 -
 ## symbols
@@ -1,18 +1,18 @@
-# archive/2025-05-18-tool-types-definition/specs/tool-types-definition (index)
-dir: archive/2025-05-18-tool-types-definition/specs/tool-types-definition
+# 2025-05-18-tool-types-definition/specs/tool-types-definition (index)
+dir: 2025-05-18-tool-types-definition/specs/tool-types-definition

 ## role
-Defines specifications for a ToolType management system that enables CRUD operations and Docker Compose template validation with variable substitution.
+Defines specifications for a ToolType management system that enables CRUD operations, Docker Compose template validation, and variable substitution for configurable tool deployments.
 ## parent
-index: archive/2025-05-18-tool-types-definition/specs/.pi-map.index.md
-map: archive/2025-05-18-tool-types-definition/specs/.pi-map.md
+index: 2025-05-18-tool-types-definition/specs/.pi-map.index.md
+map: 2025-05-18-tool-types-definition/specs/.pi-map.md
 ## children
 -
 ## files
 - spec.md
 ## links
-index: archive/2025-05-18-tool-types-definition/specs/tool-types-definition/.pi-map.index.md
-map: archive/2025-05-18-tool-types-definition/specs/tool-types-definition/.pi-map.md
+index: 2025-05-18-tool-types-definition/specs/tool-types-definition/.pi-map.index.md
+map: 2025-05-18-tool-types-definition/specs/tool-types-definition/.pi-map.md
 ## workflows
 -
 ## dirty
@@ -1,14 +1,14 @@
-# archive/2025-05-18-tool-types-definition/specs/tool-types-definition
-dir: archive/2025-05-18-tool-types-definition/specs/tool-types-definition
+# 2025-05-18-tool-types-definition/specs/tool-types-definition
+dir: 2025-05-18-tool-types-definition/specs/tool-types-definition

-index: archive/2025-05-18-tool-types-definition/specs/tool-types-definition/.pi-map.index.md
+index: 2025-05-18-tool-types-definition/specs/tool-types-definition/.pi-map.index.md

 ## role
-Defines specifications for a ToolType management system that enables CRUD operations and Docker Compose template validation with variable substitution.
+Defines specifications for a ToolType management system that enables CRUD operations, Docker Compose template validation, and variable substitution for configurable tool deployments.
 ## files
 - spec.md | Define requirements for a ToolType management system with CRUD API, Docker Compose template validation, and variable substitution | dep: REST API, Docker Compose, YAML parser, UUID, authentication/authorization system
 ## arch
-Specification-driven architecture using markdown-based requirements documentation to define system behavior before implementation.
+Specification-driven architecture using markdown-based requirements documentation with structured sections for functional requirements, API design, data models, and validation rules.
 ## tags
 spec, define, requirements, tooltype, management, system, crud, api
 ## symbols
@@ -1,23 +1,23 @@
-# archive/2025-05-18-user-config-management (index)
-dir: archive/2025-05-18-user-config-management
+# 2025-05-18-user-config-management (index)
+dir: 2025-05-18-user-config-management

 ## role
-Archive directory containing historical design documents and planning artifacts for a user configuration management feature that was proposed but not yet implemented.
+Design and planning package for a JSONB-backed user configuration management feature with API and UI components.
 ## parent
-index: archive/.pi-map.index.md
-map: archive/.pi-map.md
+index: ./.pi-map.index.md
+map: ./.pi-map.md
 ## children
- archive/2025-05-18-user-config-management/specs
-  index: archive/2025-05-18-user-config-management/specs/.pi-map.index.md
-  map: archive/2025-05-18-user-config-management/specs/.pi-map.md
+- 2025-05-18-user-config-management/specs
+  index: 2025-05-18-user-config-management/specs/.pi-map.index.md
+  map: 2025-05-18-user-config-management/specs/.pi-map.md
 ## files
 - .openspec.yaml
 - design.md
 - proposal.md
 - tasks.md
 ## links
-index: archive/2025-05-18-user-config-management/.pi-map.index.md
-map: archive/2025-05-18-user-config-management/.pi-map.md
+index: 2025-05-18-user-config-management/.pi-map.index.md
+map: 2025-05-18-user-config-management/.pi-map.md
 ## workflows
 -
 ## dirty
@@ -1,17 +1,17 @@
-# archive/2025-05-18-user-config-management
-dir: archive/2025-05-18-user-config-management
+# 2025-05-18-user-config-management
+dir: 2025-05-18-user-config-management

-index: archive/2025-05-18-user-config-management/.pi-map.index.md
+index: 2025-05-18-user-config-management/.pi-map.index.md

 ## role
-Archive directory containing historical design documents and planning artifacts for a user configuration management feature that was proposed but not yet implemented.
+Design and planning package for a JSONB-backed user configuration management feature with API and UI components.
 ## files
 - .openspec.yaml | Defines an OpenSpec configuration file with schema type and creation date metadata
 - design.md | Design document for a simple key-value user configuration system using PostgreSQL JSONB | dep: PostgreSQL, JSONB
 - proposal.md | Proposes a feature to add persistent user preference storage and management through a JSONB-backed config system with API endpoints and frontend settings UI. | dep: database, API, frontend, UserConfig model, AppShell
 - tasks.md | Project task tracking document for implementing a user settings/config feature with backend API, frontend UI, and verification steps | dep: SQLAlchemy, Alembic, FastAPI/HTTP endpoints, React/frontend router, Docker Compose, ruff, mypy, pytest, TypeScript tooling
 ## arch
-Document-driven design with OpenSpec schema definitions, Markdown-based design/proposal/task tracking, and a planned JSONB-backed key-value storage architecture with REST API and frontend UI components.
+Specification-driven development using OpenSpec schema definitions, paired with markdown-based design documents (design.md, proposal.md, tasks.md) following a proposal → design → task breakdown workflow pattern.
 ## tags
 design, user, jsonb, api, frontend, configuration, .openspec, document
 ## symbols
@@ -1,19 +1,19 @@
-# archive/2025-05-18-user-config-management/specs (index)
-dir: archive/2025-05-18-user-config-management/specs
+# 2025-05-18-user-config-management/specs (index)
+dir: 2025-05-18-user-config-management/specs

 ## role
-Contains archived specification documents for user configuration management features from May 2025.
+Contains specification documents defining requirements and design for the user configuration management feature.
 ## parent
-index: archive/2025-05-18-user-config-management/.pi-map.index.md
-map: archive/2025-05-18-user-config-management/.pi-map.md
+index: 2025-05-18-user-config-management/.pi-map.index.md
+map: 2025-05-18-user-config-management/.pi-map.md
 ## children
- archive/2025-05-18-user-config-management/specs/user-config-management
-  index: archive/2025-05-18-user-config-management/specs/user-config-management/.pi-map.index.md
-  map: archive/2025-05-18-user-config-management/specs/user-config-management/.pi-map.md
+- 2025-05-18-user-config-management/specs/user-config-management
+  index: 2025-05-18-user-config-management/specs/user-config-management/.pi-map.index.md
+  map: 2025-05-18-user-config-management/specs/user-config-management/.pi-map.md
 ## files
 ## links
-index: archive/2025-05-18-user-config-management/specs/.pi-map.index.md
-map: archive/2025-05-18-user-config-management/specs/.pi-map.md
+index: 2025-05-18-user-config-management/specs/.pi-map.index.md
+map: 2025-05-18-user-config-management/specs/.pi-map.md
 ## workflows
 -
 ## dirty
@@ -1,13 +1,13 @@
-# archive/2025-05-18-user-config-management/specs
-dir: archive/2025-05-18-user-config-management/specs
+# 2025-05-18-user-config-management/specs
+dir: 2025-05-18-user-config-management/specs

-index: archive/2025-05-18-user-config-management/specs/.pi-map.index.md
+index: 2025-05-18-user-config-management/specs/.pi-map.index.md

 ## role
-Contains archived specification documents for user configuration management features from May 2025.
+Contains specification documents defining requirements and design for the user configuration management feature.
 ## files
 ## arch
-Documentation-only archive directory with no active code; stores historical design specifications using markdown/plaintext format.
+Documentation-driven development with structured specification files (likely markdown/txt) serving as the single source of truth for implementation requirements and acceptance criteria.
 ## tags
 -
 ## symbols
@@ -1,18 +1,18 @@
-# archive/2025-05-18-user-config-management/specs/user-config-management (index)
-dir: archive/2025-05-18-user-config-management/specs/user-config-management
+# 2025-05-18-user-config-management/specs/user-config-management (index)
+dir: 2025-05-18-user-config-management/specs/user-config-management

 ## role
-Defines technical specifications for a user-configurable theme system with JSONB-based storage and retrieval.
+Defines system requirements for JSONB-based user configuration storage, retrieval, and frontend theme application.
 ## parent
-index: archive/2025-05-18-user-config-management/specs/.pi-map.index.md
-map: archive/2025-05-18-user-config-management/specs/.pi-map.md
+index: 2025-05-18-user-config-management/specs/.pi-map.index.md
+map: 2025-05-18-user-config-management/specs/.pi-map.md
 ## children
 -
 ## files
 - spec.md
 ## links
-index: archive/2025-05-18-user-config-management/specs/user-config-management/.pi-map.index.md
-map: archive/2025-05-18-user-config-management/specs/user-config-management/.pi-map.md
+index: 2025-05-18-user-config-management/specs/user-config-management/.pi-map.index.md
+map: 2025-05-18-user-config-management/specs/user-config-management/.pi-map.md
 ## workflows
 -
 ## dirty
@@ -1,14 +1,14 @@
-# archive/2025-05-18-user-config-management/specs/user-config-management
-dir: archive/2025-05-18-user-config-management/specs/user-config-management
+# 2025-05-18-user-config-management/specs/user-config-management
+dir: 2025-05-18-user-config-management/specs/user-config-management

-index: archive/2025-05-18-user-config-management/specs/user-config-management/.pi-map.index.md
+index: 2025-05-18-user-config-management/specs/user-config-management/.pi-map.index.md

 ## role
-Defines technical specifications for a user-configurable theme system with JSONB-based storage and retrieval.
+Defines system requirements for JSONB-based user configuration storage, retrieval, and frontend theme application.
 ## files
 - spec.md | Define system requirements for user configuration storage, retrieval, and frontend theme application using JSONB key-value pairs.
 ## arch
-Specification-driven design using JSONB key-value store pattern for flexible schema-less configuration persistence with frontend theme binding.
+Specification-driven architecture using JSONB key-value pairs for flexible schema-less user preferences with clear separation between storage backend and frontend consumption patterns.
 ## tags
 spec, define, system, requirements, user, configuration, storage, retrieval
 ## symbols
@@ -1,15 +1,15 @@
-# archive/2026-05-17-auth-oauth (index)
-dir: archive/2026-05-17-auth-oauth
+# 2026-05-17-auth-oauth (index)
+dir: 2026-05-17-auth-oauth

 ## role
-Archive directory containing design documents and proposals for an OAuth2/OIDC authentication system with Authentik integration and JWT token management.
+Authentication and authorization package implementing OAuth2/OIDC integration with Authentik for secure user session management.
 ## parent
-index: archive/.pi-map.index.md
-map: archive/.pi-map.md
+index: ./.pi-map.index.md
+map: ./.pi-map.md
 ## children
- archive/2026-05-17-auth-oauth/specs
-  index: archive/2026-05-17-auth-oauth/specs/.pi-map.index.md
-  map: archive/2026-05-17-auth-oauth/specs/.pi-map.md
+- 2026-05-17-auth-oauth/specs
+  index: 2026-05-17-auth-oauth/specs/.pi-map.index.md
+  map: 2026-05-17-auth-oauth/specs/.pi-map.md
 ## files
 - .openspec.yaml
 - README.md
@@ -17,8 +17,8 @@ map: archive/.pi-map.md
 - proposal.md
 - tasks.md
 ## links
-index: archive/2026-05-17-auth-oauth/.pi-map.index.md
-map: archive/2026-05-17-auth-oauth/.pi-map.md
+index: 2026-05-17-auth-oauth/.pi-map.index.md
+map: 2026-05-17-auth-oauth/.pi-map.md
 ## workflows
 -
 ## dirty
@@ -1,10 +1,10 @@
-# archive/2026-05-17-auth-oauth
-dir: archive/2026-05-17-auth-oauth
+# 2026-05-17-auth-oauth
+dir: 2026-05-17-auth-oauth

-index: archive/2026-05-17-auth-oauth/.pi-map.index.md
+index: 2026-05-17-auth-oauth/.pi-map.index.md

 ## role
-Archive directory containing design documents and proposals for an OAuth2/OIDC authentication system with Authentik integration and JWT token management.
+Authentication and authorization package implementing OAuth2/OIDC integration with Authentik for secure user session management.
 ## files
 - .openspec.yaml | Defines an OpenAPI specification file metadata with schema type and creation date
 - README.md | Documents a project that implements OAuth2/OIDC authentication using Authentik with internal JWTs and database-backed refresh tokens | dep: Authentik, OAuth2, OIDC, JWT
@@ -12,7 +12,7 @@ Archive directory containing design documents and proposals for an OAuth2/OIDC a
 - proposal.md | Proposes a technical implementation plan for adding production-ready OAuth2/OIDC authentication with Authentik integration, JWT session management, and secure token lifecycle handling to a backend API project. | dep: Authentik, OAuth2/OIDC, JWKS, JWT, database, apps/api/src, config, models, auth services, API routes
 - tasks.md | Task tracking document for implementing OIDC/JWT authentication system with refresh tokens in a backend application. | dep: SQLAlchemy, Alembic, Authentik OIDC, pytest, ruff, mypy, asyncpg, PostgreSQL
 ## arch
-Document-driven design specification using markdown-based RFCs, with OpenAPI metadata, separating concerns into design rationale (design.md), implementation planning (proposal.md), task tracking (tasks.md), and project documentation (README.md).
+Layered security architecture with external IdP delegation (Authentik OIDC), internal JWT stateless access tokens, database-backed opaque refresh tokens, and environment-aware cookie security policies.
 ## tags
 oidc, authentik, oauth2, jwt, authentication, tokens, refresh, design
 ## symbols
@@ -1,19 +1,19 @@
-# archive/2026-05-17-auth-oauth/specs (index)
-dir: archive/2026-05-17-auth-oauth/specs
+# 2026-05-17-auth-oauth/specs (index)
+dir: 2026-05-17-auth-oauth/specs

 ## role
-Contains historical specification documents for the OAuth authentication implementation from May 2026, serving as archived design reference.
+Contains specification documents defining requirements, interfaces, and behavior contracts for the OAuth authentication system.
 ## parent
-index: archive/2026-05-17-auth-oauth/.pi-map.index.md
-map: archive/2026-05-17-auth-oauth/.pi-map.md
+index: 2026-05-17-auth-oauth/.pi-map.index.md
+map: 2026-05-17-auth-oauth/.pi-map.md
 ## children
- archive/2026-05-17-auth-oauth/specs/auth-oauth
-  index: archive/2026-05-17-auth-oauth/specs/auth-oauth/.pi-map.index.md
-  map: archive/2026-05-17-auth-oauth/specs/auth-oauth/.pi-map.md
+- 2026-05-17-auth-oauth/specs/auth-oauth
+  index: 2026-05-17-auth-oauth/specs/auth-oauth/.pi-map.index.md
+  map: 2026-05-17-auth-oauth/specs/auth-oauth/.pi-map.md
 ## files
 ## links
-index: archive/2026-05-17-auth-oauth/specs/.pi-map.index.md
-map: archive/2026-05-17-auth-oauth/specs/.pi-map.md
+index: 2026-05-17-auth-oauth/specs/.pi-map.index.md
+map: 2026-05-17-auth-oauth/specs/.pi-map.md
 ## workflows
 -
 ## dirty
@@ -1,13 +1,13 @@
-# archive/2026-05-17-auth-oauth/specs
-dir: archive/2026-05-17-auth-oauth/specs
+# 2026-05-17-auth-oauth/specs
+dir: 2026-05-17-auth-oauth/specs

-index: archive/2026-05-17-auth-oauth/specs/.pi-map.index.md
+index: 2026-05-17-auth-oauth/specs/.pi-map.index.md

 ## role
-Contains historical specification documents for the OAuth authentication implementation from May 2026, serving as archived design reference.
+Contains specification documents defining requirements, interfaces, and behavior contracts for the OAuth authentication system.
 ## files
 ## arch
-Documentation-only archive with no active code; likely contains markdown/ADR-style specification files capturing past architectural decisions for external authentication provider integration.
+Documentation-driven design using specification files (likely markdown or similar) to formalize system requirements before implementation.
 ## tags
 -
 ## symbols
@@ -1,18 +1,18 @@
-# archive/2026-05-17-auth-oauth/specs/auth-oauth (index)
-dir: archive/2026-05-17-auth-oauth/specs/auth-oauth
+# 2026-05-17-auth-oauth/specs/auth-oauth (index)
+dir: 2026-05-17-auth-oauth/specs/auth-oauth

 ## role
-Defines authentication requirements for OAuth2/OIDC integration with Authentik identity provider.
+Defines authentication and authorization requirements for OAuth2/OIDC integration with Authentik identity provider.
 ## parent
-index: archive/2026-05-17-auth-oauth/specs/.pi-map.index.md
-map: archive/2026-05-17-auth-oauth/specs/.pi-map.md
+index: 2026-05-17-auth-oauth/specs/.pi-map.index.md
+map: 2026-05-17-auth-oauth/specs/.pi-map.md
 ## children
 -
 ## files
 - spec.md
 ## links
-index: archive/2026-05-17-auth-oauth/specs/auth-oauth/.pi-map.index.md
-map: archive/2026-05-17-auth-oauth/specs/auth-oauth/.pi-map.md
+index: 2026-05-17-auth-oauth/specs/auth-oauth/.pi-map.index.md
+map: 2026-05-17-auth-oauth/specs/auth-oauth/.pi-map.md
 ## workflows
 -
 ## dirty
@@ -1,14 +1,14 @@
-# archive/2026-05-17-auth-oauth/specs/auth-oauth
-dir: archive/2026-05-17-auth-oauth/specs/auth-oauth
+# 2026-05-17-auth-oauth/specs/auth-oauth
+dir: 2026-05-17-auth-oauth/specs/auth-oauth

-index: archive/2026-05-17-auth-oauth/specs/auth-oauth/.pi-map.index.md
+index: 2026-05-17-auth-oauth/specs/auth-oauth/.pi-map.index.md

 ## role
-Defines authentication requirements for OAuth2/OIDC integration with Authentik identity provider.
+Defines authentication and authorization requirements for OAuth2/OIDC integration with Authentik identity provider.
 ## files
 - spec.md | Specifies OAuth2/OIDC authentication, session security, token refresh, and logout requirements for a web application using Authentik as the identity provider. | dep: Authentik, JWKS, OAuth2, OIDC, HTTP cookies, database
 ## arch
-Requirements specification document following standard markdown-based spec format with no implemented architecture.
+Specification-driven security architecture using standard OAuth2/OIDC flows with session management, token lifecycle, and secure logout patterns.
 ## tags
 oauth2, oidc, authentik, spec, specifies, authentication, session, security
 ## symbols
@@ -1,11 +1,11 @@
-# archive/2026-05-17-database-models (index)
-dir: archive/2026-05-17-database-models
+# 2026-05-17-database-models (index)
+dir: 2026-05-17-database-models

 ## role
-Archive directory containing design documents and proposals for implementing SQLAlchemy 2.0 async database models and Alembic migrations for a PostgreSQL-backed API application.
+Database persistence layer providing SQLAlchemy 2.0 async ORM models and Alembic migration infrastructure for PostgreSQL data management in the Headquarter platform API.
 ## parent
-index: archive/.pi-map.index.md
-map: archive/.pi-map.md
+index: ./.pi-map.index.md
+map: ./.pi-map.md
 ## children
 -
 ## files
@@ -15,8 +15,8 @@ map: archive/.pi-map.md
 - proposal.md
 - tasks.md
 ## links
-index: archive/2026-05-17-database-models/.pi-map.index.md
-map: archive/2026-05-17-database-models/.pi-map.md
+index: 2026-05-17-database-models/.pi-map.index.md
+map: 2026-05-17-database-models/.pi-map.md
 ## workflows
 -
 ## dirty
@@ -1,10 +1,10 @@
-# archive/2026-05-17-database-models
-dir: archive/2026-05-17-database-models
+# 2026-05-17-database-models
+dir: 2026-05-17-database-models

-index: archive/2026-05-17-database-models/.pi-map.index.md
+index: 2026-05-17-database-models/.pi-map.index.md

 ## role
-Archive directory containing design documents and proposals for implementing SQLAlchemy 2.0 async database models and Alembic migrations for a PostgreSQL-backed API application.
+Database persistence layer providing SQLAlchemy 2.0 async ORM models and Alembic migration infrastructure for PostgreSQL data management in the Headquarter platform API.
 ## files
 - .openspec.yaml | Defines an OpenAPI specification file metadata with schema type and creation date
 - README.md | Defines a project for implementing SQLAlchemy database models and Alembic migrations for core entities. | dep: SQLAlchemy, Alembic
@@ -12,7 +12,7 @@ Archive directory containing design documents and proposals for implementing SQL
 - proposal.md | Proposes implementing SQLAlchemy 2.0 async database models and Alembic migrations for core entities in the Headquarter platform | dep: SQLAlchemy 2.0, Alembic, asyncpg, pytest, mypy, ruff
 - tasks.md | Tracks completed implementation tasks for building a SQLAlchemy-based async database layer with models, migrations, seeding, and testing for an API application. | dep: SQLAlchemy, Alembic, Pydantic-settings, PostgreSQL, pytest, mypy, ruff
 ## arch
-Document-driven design with OpenAPI specification metadata, structured planning artifacts (proposal/design/tasks), and async SQLAlchemy 2.0 ORM pattern targeting PostgreSQL with Alembic migration management.
+Async SQLAlchemy 2.0 declarative ORM with Alembic migration tooling, following repository pattern for data access, with model-driven schema design and automated migration generation for PostgreSQL backend.
 ## tags
 sqlalchemy, alembic, database, defines, models, migrations, design, async
 ## symbols
@@ -1,15 +1,15 @@
-# archive/2026-05-17-frontend-foundation (index)
-dir: archive/2026-05-17-frontend-foundation
+# 2026-05-17-frontend-foundation (index)
+dir: 2026-05-17-frontend-foundation

 ## role
-Archive of a completed frontend foundation project delivering a React/TypeScript/Vite starter with authentication, routing, and API integration patterns.
+Establishes a foundational frontend architecture for authenticated React/TypeScript/Vite web applications with routing, API integration, and responsive UI patterns.
 ## parent
-index: archive/.pi-map.index.md
-map: archive/.pi-map.md
+index: ./.pi-map.index.md
+map: ./.pi-map.md
 ## children
- archive/2026-05-17-frontend-foundation/specs
-  index: archive/2026-05-17-frontend-foundation/specs/.pi-map.index.md
-  map: archive/2026-05-17-frontend-foundation/specs/.pi-map.md
+- 2026-05-17-frontend-foundation/specs
+  index: 2026-05-17-frontend-foundation/specs/.pi-map.index.md
+  map: 2026-05-17-frontend-foundation/specs/.pi-map.md
 ## files
 - .openspec.yaml
 - README.md
@@ -17,8 +17,8 @@ map: archive/.pi-map.md
 - proposal.md
 - tasks.md
 ## links
-index: archive/2026-05-17-frontend-foundation/.pi-map.index.md
-map: archive/2026-05-17-frontend-foundation/.pi-map.md
+index: 2026-05-17-frontend-foundation/.pi-map.index.md
+map: 2026-05-17-frontend-foundation/.pi-map.md
 ## workflows
 -
 ## dirty
@@ -1,10 +1,10 @@
-# archive/2026-05-17-frontend-foundation
-dir: archive/2026-05-17-frontend-foundation
+# 2026-05-17-frontend-foundation
+dir: 2026-05-17-frontend-foundation

-index: archive/2026-05-17-frontend-foundation/.pi-map.index.md
+index: 2026-05-17-frontend-foundation/.pi-map.index.md

 ## role
-Archive of a completed frontend foundation project delivering a React/TypeScript/Vite starter with authentication, routing, and API integration patterns.
+Establishes a foundational frontend architecture for authenticated React/TypeScript/Vite web applications with routing, API integration, and responsive UI patterns.
 ## files
 - .openspec.yaml | Defines an OpenAPI specification file metadata with schema type and creation date
 - README.md | Defines a project foundation for a frontend application with authentication, routing, and API integration capabilities.
@@ -12,7 +12,7 @@ Archive of a completed frontend foundation project delivering a React/TypeScript
 - proposal.md | Proposes a frontend foundation for a React/TypeScript web application with authentication, routing, and API integration. | dep: React, TypeScript, Vite, backend auth endpoints (/auth/login, /auth/logout, /auth/me, /auth/refresh)
 - tasks.md | Tracks completed frontend development tasks for building an authenticated web application with routing, API integration, and dashboard UI.
 ## arch
-Documentation-driven architecture with OpenAPI-first API contract, layered design docs (proposal → design → tasks), and modular React patterns including authenticated route guards, responsive shell layout, and centralized API client abstraction.
+Document-driven specification package using OpenAPI metadata, design documents, and task tracking to define a layered frontend architecture with authenticated routing, API client abstraction, and shell-based responsive layout components.
 ## tags
 react, frontend, routing, api, typescript, auth, foundation, application
 ## symbols
@@ -1,19 +1,19 @@
-# archive/2026-05-17-frontend-foundation/specs (index)
-dir: archive/2026-05-17-frontend-foundation/specs
+# 2026-05-17-frontend-foundation/specs (index)
+dir: 2026-05-17-frontend-foundation/specs

 ## role
-Contains archived specification documents for the frontend foundation project dated May 17, 2026, serving as historical reference for design decisions and requirements.
+Contains specification documents defining requirements and design decisions for the frontend foundation layer.
 ## parent
-index: archive/2026-05-17-frontend-foundation/.pi-map.index.md
-map: archive/2026-05-17-frontend-foundation/.pi-map.md
+index: 2026-05-17-frontend-foundation/.pi-map.index.md
+map: 2026-05-17-frontend-foundation/.pi-map.md
 ## children
- archive/2026-05-17-frontend-foundation/specs/frontend-foundation
-  index: archive/2026-05-17-frontend-foundation/specs/frontend-foundation/.pi-map.index.md
-  map: archive/2026-05-17-frontend-foundation/specs/frontend-foundation/.pi-map.md
+- 2026-05-17-frontend-foundation/specs/frontend-foundation
+  index: 2026-05-17-frontend-foundation/specs/frontend-foundation/.pi-map.index.md
+  map: 2026-05-17-frontend-foundation/specs/frontend-foundation/.pi-map.md
 ## files
 ## links
-index: archive/2026-05-17-frontend-foundation/specs/.pi-map.index.md
-map: archive/2026-05-17-frontend-foundation/specs/.pi-map.md
+index: 2026-05-17-frontend-foundation/specs/.pi-map.index.md
+map: 2026-05-17-frontend-foundation/specs/.pi-map.md
 ## workflows
 -
 ## dirty
@@ -1,13 +1,13 @@
-# archive/2026-05-17-frontend-foundation/specs
-dir: archive/2026-05-17-frontend-foundation/specs
+# 2026-05-17-frontend-foundation/specs
+dir: 2026-05-17-frontend-foundation/specs

-index: archive/2026-05-17-frontend-foundation/specs/.pi-map.index.md
+index: 2026-05-17-frontend-foundation/specs/.pi-map.index.md

 ## role
-Contains archived specification documents for the frontend foundation project dated May 17, 2026, serving as historical reference for design decisions and requirements.
+Contains specification documents defining requirements and design decisions for the frontend foundation layer.
 ## files
 ## arch
-Document-based specification storage using date-versioned directory naming convention for temporal organization of project requirements.
+Documentation-driven architecture using specification files to formalize API contracts, component interfaces, and implementation standards before code development.
 ## tags
 -
 ## symbols
@@ -1,18 +1,18 @@
-# archive/2026-05-17-frontend-foundation/specs/frontend-foundation (index)
-dir: archive/2026-05-17-frontend-foundation/specs/frontend-foundation
+# 2026-05-17-frontend-foundation/specs/frontend-foundation (index)
+dir: 2026-05-17-frontend-foundation/specs/frontend-foundation

 ## role
-Defines technical specifications for a React 18+ TypeScript frontend foundation including routing, auth, layout, and HTTP client patterns.
+Defines the technical specification and requirements for a React 18+ TypeScript frontend foundation with routing, authentication, layout, and HTTP client capabilities.
 ## parent
-index: archive/2026-05-17-frontend-foundation/specs/.pi-map.index.md
-map: archive/2026-05-17-frontend-foundation/specs/.pi-map.md
+index: 2026-05-17-frontend-foundation/specs/.pi-map.index.md
+map: 2026-05-17-frontend-foundation/specs/.pi-map.md
 ## children
 -
 ## files
 - spec.md
 ## links
-index: archive/2026-05-17-frontend-foundation/specs/frontend-foundation/.pi-map.index.md
-map: archive/2026-05-17-frontend-foundation/specs/frontend-foundation/.pi-map.md
+index: 2026-05-17-frontend-foundation/specs/frontend-foundation/.pi-map.index.md
+map: 2026-05-17-frontend-foundation/specs/frontend-foundation/.pi-map.md
 ## workflows
 -
 ## dirty
@@ -1,14 +1,14 @@
-# archive/2026-05-17-frontend-foundation/specs/frontend-foundation
-dir: archive/2026-05-17-frontend-foundation/specs/frontend-foundation
+# 2026-05-17-frontend-foundation/specs/frontend-foundation
+dir: 2026-05-17-frontend-foundation/specs/frontend-foundation

-index: archive/2026-05-17-frontend-foundation/specs/frontend-foundation/.pi-map.index.md
+index: 2026-05-17-frontend-foundation/specs/frontend-foundation/.pi-map.index.md

 ## role
-Defines technical specifications for a React 18+ TypeScript frontend foundation including routing, auth, layout, and HTTP client patterns.
+Defines the technical specification and requirements for a React 18+ TypeScript frontend foundation with routing, authentication, layout, and HTTP client capabilities.
 ## files
 - spec.md | This file specifies frontend requirements for a React 18+ TypeScript web application with routing, authentication, layout, and HTTP client configuration. | dep: React 18+, TypeScript 5+, Vite, React Router, Axios/fetch
 ## arch
-Specification-driven architecture with modular concerns (routing, auth, layout, HTTP) documented as requirements for a modern React SPA foundation.
+Specification-driven architecture using React 18 with TypeScript, likely implementing common patterns such as component-based UI, client-side routing, token-based authentication, responsive layout systems, and configurable HTTP interceptors.
 ## tags
 spec, specifies, frontend, requirements, react, typescript, web, application
 ## symbols
@@ -1,15 +1,15 @@
-# archive/2026-05-17-project-management (index)
-dir: archive/2026-05-17-project-management
+# 2026-05-17-project-management (index)
+dir: 2026-05-17-project-management

 ## role
-This package contains archived design documentation and planning artifacts for a project management feature that was implemented with full-stack CRUD operations, ownership enforcement, and SSH key integration.
+Defines specifications, design, and implementation tracking for a full-stack project management feature with authenticated CRUD, ownership enforcement, and SSH key integration.
 ## parent
-index: archive/.pi-map.index.md
-map: archive/.pi-map.md
+index: ./.pi-map.index.md
+map: ./.pi-map.md
 ## children
- archive/2026-05-17-project-management/specs
-  index: archive/2026-05-17-project-management/specs/.pi-map.index.md
-  map: archive/2026-05-17-project-management/specs/.pi-map.md
+- 2026-05-17-project-management/specs
+  index: 2026-05-17-project-management/specs/.pi-map.index.md
+  map: 2026-05-17-project-management/specs/.pi-map.md
 ## files
 - .openspec.yaml
 - README.md
@@ -17,8 +17,8 @@ map: archive/.pi-map.md
 - proposal.md
 - tasks.md
 ## links
-index: archive/2026-05-17-project-management/.pi-map.index.md
-map: archive/2026-05-17-project-management/.pi-map.md
+index: 2026-05-17-project-management/.pi-map.index.md
+map: 2026-05-17-project-management/.pi-map.md
 ## workflows
 -
 ## dirty
@@ -1,10 +1,10 @@
-# archive/2026-05-17-project-management
-dir: archive/2026-05-17-project-management
+# 2026-05-17-project-management
+dir: 2026-05-17-project-management

-index: archive/2026-05-17-project-management/.pi-map.index.md
+index: 2026-05-17-project-management/.pi-map.index.md

 ## role
-This package contains archived design documentation and planning artifacts for a project management feature that was implemented with full-stack CRUD operations, ownership enforcement, and SSH key integration.
+Defines specifications, design, and implementation tracking for a full-stack project management feature with authenticated CRUD, ownership enforcement, and SSH key integration.
 ## files
 - .openspec.yaml | Defines an OpenAPI specification file metadata with schema type and creation date
 - README.md | Defines a project management application that implements create, read, update, delete, listing, and ownership workflows across API and frontend layers
@@ -12,7 +12,7 @@ This package contains archived design documentation and planning artifacts for a
 - proposal.md | Proposes a project management feature implementation covering authenticated CRUD APIs, frontend flows, SSH key integration, and cascading deletion behavior. | dep: authentication, data models, frontend foundation, apps/api/src, apps/web/src
 - tasks.md | Tracks completed tasks for implementing full-stack project management features with ownership enforcement and verification checks.
 ## arch
-Documentation-driven planning architecture using OpenAPI specification metadata, structured markdown design documents (proposal → design → tasks → README), and explicit separation of API/backend concerns from frontend integration workflows.
+Documentation-driven specification pattern using OpenAPI metadata, layered design docs (proposal → design → tasks), and separation of concerns across API/backend and frontend concerns with explicit ownership-based access control.
 ## tags
 project, frontend, management, ownership, design, tasks, defines, .openspec
 ## symbols
@@ -1,25 +1,25 @@
-# archive/2026-05-17-project-management/specs (index)
-dir: archive/2026-05-17-project-management/specs
+# 2026-05-17-project-management/specs (index)
+dir: 2026-05-17-project-management/specs

 ## role
-Contains archived specification documents from a project management snapshot dated May 17, 2026.
+Contains project specifications and requirements documentation for the 2026-05-17-project-management system.
 ## parent
-index: archive/2026-05-17-project-management/.pi-map.index.md
-map: archive/2026-05-17-project-management/.pi-map.md
+index: 2026-05-17-project-management/.pi-map.index.md
+map: 2026-05-17-project-management/.pi-map.md
 ## children
- archive/2026-05-17-project-management/specs/git-repo
-  index: archive/2026-05-17-project-management/specs/git-repo/.pi-map.index.md
-  map: archive/2026-05-17-project-management/specs/git-repo/.pi-map.md
- archive/2026-05-17-project-management/specs/project-management
-  index: archive/2026-05-17-project-management/specs/project-management/.pi-map.index.md
-  map: archive/2026-05-17-project-management/specs/project-management/.pi-map.md
- archive/2026-05-17-project-management/specs/ssh-keys
-  index: archive/2026-05-17-project-management/specs/ssh-keys/.pi-map.index.md
-  map: archive/2026-05-17-project-management/specs/ssh-keys/.pi-map.md
+- 2026-05-17-project-management/specs/git-repo
+  index: 2026-05-17-project-management/specs/git-repo/.pi-map.index.md
+  map: 2026-05-17-project-management/specs/git-repo/.pi-map.md
+- 2026-05-17-project-management/specs/project-management
+  index: 2026-05-17-project-management/specs/project-management/.pi-map.index.md
+  map: 2026-05-17-project-management/specs/project-management/.pi-map.md
+- 2026-05-17-project-management/specs/ssh-keys
+  index: 2026-05-17-project-management/specs/ssh-keys/.pi-map.index.md
+  map: 2026-05-17-project-management/specs/ssh-keys/.pi-map.md
 ## files
 ## links
-index: archive/2026-05-17-project-management/specs/.pi-map.index.md
-map: archive/2026-05-17-project-management/specs/.pi-map.md
+index: 2026-05-17-project-management/specs/.pi-map.index.md
+map: 2026-05-17-project-management/specs/.pi-map.md
 ## workflows
 -
 ## dirty
@@ -1,13 +1,13 @@
-# archive/2026-05-17-project-management/specs
-dir: archive/2026-05-17-project-management/specs
+# 2026-05-17-project-management/specs
+dir: 2026-05-17-project-management/specs

-index: archive/2026-05-17-project-management/specs/.pi-map.index.md
+index: 2026-05-17-project-management/specs/.pi-map.index.md

 ## role
-Contains archived specification documents from a project management snapshot dated May 17, 2026.
+Contains project specifications and requirements documentation for the 2026-05-17-project-management system.
 ## files
 ## arch
-Simple archival storage pattern with date-based directory naming for historical spec versioning.
+Documentation-driven specification pattern with no code architecture; serves as the requirements foundation for downstream implementation packages.
 ## tags
 -
 ## symbols
@@ -1,18 +1,18 @@
-# archive/2026-05-17-project-management/specs/git-repo (index)
-dir: archive/2026-05-17-project-management/specs/git-repo
+# 2026-05-17-project-management/specs/git-repo (index)
+dir: 2026-05-17-project-management/specs/git-repo

 ## role
-Specifies requirements for automatic cleanup of associated Git repositories when project management entities are deleted.
+Defines specification requirements for cascading repository deletion when a project is deleted in a project management system.
 ## parent
-index: archive/2026-05-17-project-management/specs/.pi-map.index.md
-map: archive/2026-05-17-project-management/specs/.pi-map.md
+index: 2026-05-17-project-management/specs/.pi-map.index.md
+map: 2026-05-17-project-management/specs/.pi-map.md
 ## children
 -
 ## files
 - spec.md
 ## links
-index: archive/2026-05-17-project-management/specs/git-repo/.pi-map.index.md
-map: archive/2026-05-17-project-management/specs/git-repo/.pi-map.md
+index: 2026-05-17-project-management/specs/git-repo/.pi-map.index.md
+map: 2026-05-17-project-management/specs/git-repo/.pi-map.md
 ## workflows
 -
 ## dirty
@@ -1,14 +1,14 @@
-# archive/2026-05-17-project-management/specs/git-repo
-dir: archive/2026-05-17-project-management/specs/git-repo
+# 2026-05-17-project-management/specs/git-repo
+dir: 2026-05-17-project-management/specs/git-repo

-index: archive/2026-05-17-project-management/specs/git-repo/.pi-map.index.md
+index: 2026-05-17-project-management/specs/git-repo/.pi-map.index.md

 ## role
-Specifies requirements for automatic cleanup of associated Git repositories when project management entities are deleted.
+Defines specification requirements for cascading repository deletion when a project is deleted in a project management system.
 ## files
 - spec.md | Defines modified requirements for cascading repository deletion when a project is deleted
 ## arch
-Requirements specification document using structured markdown with user stories, acceptance criteria, and behavioral rules for cascade deletion logic.
+Specification-driven design using markdown-based requirements documentation with focus on referential integrity and cascading delete operations across project-repository boundaries.
 ## tags
 spec, defines, modified, requirements, cascading, repository, deletion, project
 ## symbols
@@ -1,18 +1,18 @@
-# archive/2026-05-17-project-management/specs/project-management (index)
-dir: archive/2026-05-17-project-management/specs/project-management
+# 2026-05-17-project-management/specs/project-management (index)
+dir: 2026-05-17-project-management/specs/project-management

 ## role
-Defines modified requirements for a project management system with CRUD operations, ownership-based access control, and SSH key management
+Defines the specification requirements for a project management system including CRUD operations, access control, and SSH key management features.
 ## parent
-index: archive/2026-05-17-project-management/specs/.pi-map.index.md
-map: archive/2026-05-17-project-management/specs/.pi-map.md
+index: 2026-05-17-project-management/specs/.pi-map.index.md
+map: 2026-05-17-project-management/specs/.pi-map.md
 ## children
 -
 ## files
 - spec.md
 ## links
-index: archive/2026-05-17-project-management/specs/project-management/.pi-map.index.md
-map: archive/2026-05-17-project-management/specs/project-management/.pi-map.md
+index: 2026-05-17-project-management/specs/project-management/.pi-map.index.md
+map: 2026-05-17-project-management/specs/project-management/.pi-map.md
 ## workflows
 -
 ## dirty
@@ -1,14 +1,14 @@
-# archive/2026-05-17-project-management/specs/project-management
-dir: archive/2026-05-17-project-management/specs/project-management
+# 2026-05-17-project-management/specs/project-management
+dir: 2026-05-17-project-management/specs/project-management

-index: archive/2026-05-17-project-management/specs/project-management/.pi-map.index.md
+index: 2026-05-17-project-management/specs/project-management/.pi-map.index.md

 ## role
-Defines modified requirements for a project management system with CRUD operations, ownership-based access control, and SSH key management
+Defines the specification requirements for a project management system including CRUD operations, access control, and SSH key management features.
 ## files
 - spec.md | Defines modified requirements for a project management system with CRUD operations, ownership-based access control, and SSH key management
 ## arch
-Requirements specification document using Markdown format with structured sections for functional requirements, non-functional requirements, and system constraints
+Requirements-driven specification document using natural language descriptions of functional requirements, business rules, and system constraints without explicit architectural patterns.
 ## tags
 management, spec, defines, modified, requirements, project, system, crud
 ## symbols
@@ -1,18 +1,18 @@
-# archive/2026-05-17-project-management/specs/ssh-keys (index)
-dir: archive/2026-05-17-project-management/specs/ssh-keys
+# 2026-05-17-project-management/specs/ssh-keys (index)
+dir: 2026-05-17-project-management/specs/ssh-keys

 ## role
-Defines requirements specification for SSH key management with project default key assignment validation
+Specifies requirements for SSH key management and project-level default key assignment with validation rules.
 ## parent
-index: archive/2026-05-17-project-management/specs/.pi-map.index.md
-map: archive/2026-05-17-project-management/specs/.pi-map.md
+index: 2026-05-17-project-management/specs/.pi-map.index.md
+map: 2026-05-17-project-management/specs/.pi-map.md
 ## children
 -
 ## files
 - spec.md
 ## links
-index: archive/2026-05-17-project-management/specs/ssh-keys/.pi-map.index.md
-map: archive/2026-05-17-project-management/specs/ssh-keys/.pi-map.md
+index: 2026-05-17-project-management/specs/ssh-keys/.pi-map.index.md
+map: 2026-05-17-project-management/specs/ssh-keys/.pi-map.md
 ## workflows
 -
 ## dirty
@@ -1,14 +1,14 @@
-# archive/2026-05-17-project-management/specs/ssh-keys
-dir: archive/2026-05-17-project-management/specs/ssh-keys
+# 2026-05-17-project-management/specs/ssh-keys
+dir: 2026-05-17-project-management/specs/ssh-keys

-index: archive/2026-05-17-project-management/specs/ssh-keys/.pi-map.index.md
+index: 2026-05-17-project-management/specs/ssh-keys/.pi-map.index.md

 ## role
-Defines requirements specification for SSH key management with project default key assignment validation
+Specifies requirements for SSH key management and project-level default key assignment with validation rules.
 ## files
 - spec.md | Defines modified requirements for SSH key association with project default-key assignment validation
 ## arch
-Requirements-as-code pattern using markdown-based specification documents for feature definition
+Requirements specification using markdown-based structured documentation pattern.
 ## tags
 key, spec, defines, modified, requirements, ssh, association, project
 ## symbols
@@ -1,23 +1,23 @@
-# archive/2026-05-18-database-setup-recovery (index)
-dir: archive/2026-05-18-database-setup-recovery
+# 2026-05-18-database-setup-recovery (index)
+dir: 2026-05-18-database-setup-recovery

 ## role
-Archive directory preserving historical design documents for database setup and recovery infrastructure in a Dockerized API application.
+This package contains planning and design documents for implementing automatic database setup, migration, and recovery mechanisms for a Dockerized API application.
 ## parent
-index: archive/.pi-map.index.md
-map: archive/.pi-map.md
+index: ./.pi-map.index.md
+map: ./.pi-map.md
 ## children
- archive/2026-05-18-database-setup-recovery/specs
-  index: archive/2026-05-18-database-setup-recovery/specs/.pi-map.index.md
-  map: archive/2026-05-18-database-setup-recovery/specs/.pi-map.md
+- 2026-05-18-database-setup-recovery/specs
+  index: 2026-05-18-database-setup-recovery/specs/.pi-map.index.md
+  map: 2026-05-18-database-setup-recovery/specs/.pi-map.md
 ## files
 - .openspec.yaml
 - design.md
 - proposal.md
 - tasks.md
 ## links
-index: archive/2026-05-18-database-setup-recovery/.pi-map.index.md
-map: archive/2026-05-18-database-setup-recovery/.pi-map.md
+index: 2026-05-18-database-setup-recovery/.pi-map.index.md
+map: 2026-05-18-database-setup-recovery/.pi-map.md
 ## workflows
 -
 ## dirty
@@ -1,17 +1,17 @@
-# archive/2026-05-18-database-setup-recovery
-dir: archive/2026-05-18-database-setup-recovery
+# 2026-05-18-database-setup-recovery
+dir: 2026-05-18-database-setup-recovery

-index: archive/2026-05-18-database-setup-recovery/.pi-map.index.md
+index: 2026-05-18-database-setup-recovery/.pi-map.index.md

 ## role
-Archive directory preserving historical design documents for database setup and recovery infrastructure in a Dockerized API application.
+This package contains planning and design documents for implementing automatic database setup, migration, and recovery mechanisms for a Dockerized API application.
 ## files
 - .openspec.yaml | Defines an OpenSpec configuration file with schema type and creation date metadata
 - design.md | Design document specifying how to implement automatic database migration running, connection retry logic, and graceful error handling on application startup | dep: SQLAlchemy, Alembic, Docker, async context
 - proposal.md | Proposes architectural changes for automatic database initialization, migration management, and seed data handling in a Dockerized API application | dep: alembic, docker-compose, traefik, fastapi/sqlalchemy (implied), postgres (implied)
 - tasks.md | Project task checklist tracking completion status of database initialization, error handling, Docker integration, and testing work items.
 ## arch
-Document-driven design archive containing OpenSpec configuration, architectural proposals, and task tracking for implementing resilient database initialization with migrations, connection retry logic, and graceful error handling.
+Documentation-driven architecture using OpenSpec for schema configuration, with designs for startup-time database initialization, connection retry with exponential backoff, migration running, and seed data handling integrated into Docker container orchestration.
 ## tags
 design, database, handling, docker, .openspec, automatic, migration, error
 ## symbols
@@ -1,19 +1,19 @@
-# archive/2026-05-18-database-setup-recovery/specs (index)
-dir: archive/2026-05-18-database-setup-recovery/specs
+# 2026-05-18-database-setup-recovery/specs (index)
+dir: 2026-05-18-database-setup-recovery/specs

 ## role
-Contains database setup and recovery specifications from a 2026-05-18 archive snapshot.
+Contains specification documents defining requirements for database setup and recovery procedures.
 ## parent
-index: archive/2026-05-18-database-setup-recovery/.pi-map.index.md
-map: archive/2026-05-18-database-setup-recovery/.pi-map.md
+index: 2026-05-18-database-setup-recovery/.pi-map.index.md
+map: 2026-05-18-database-setup-recovery/.pi-map.md
 ## children
- archive/2026-05-18-database-setup-recovery/specs/database-initialization
-  index: archive/2026-05-18-database-setup-recovery/specs/database-initialization/.pi-map.index.md
-  map: archive/2026-05-18-database-setup-recovery/specs/database-initialization/.pi-map.md
+- 2026-05-18-database-setup-recovery/specs/database-initialization
+  index: 2026-05-18-database-setup-recovery/specs/database-initialization/.pi-map.index.md
+  map: 2026-05-18-database-setup-recovery/specs/database-initialization/.pi-map.md
 ## files
 ## links
-index: archive/2026-05-18-database-setup-recovery/specs/.pi-map.index.md
-map: archive/2026-05-18-database-setup-recovery/specs/.pi-map.md
+index: 2026-05-18-database-setup-recovery/specs/.pi-map.index.md
+map: 2026-05-18-database-setup-recovery/specs/.pi-map.md
 ## workflows
 -
 ## dirty
@@ -1,13 +1,13 @@
-# archive/2026-05-18-database-setup-recovery/specs
-dir: archive/2026-05-18-database-setup-recovery/specs
+# 2026-05-18-database-setup-recovery/specs
+dir: 2026-05-18-database-setup-recovery/specs

-index: archive/2026-05-18-database-setup-recovery/specs/.pi-map.index.md
+index: 2026-05-18-database-setup-recovery/specs/.pi-map.index.md

 ## role
-Contains database setup and recovery specifications from a 2026-05-18 archive snapshot.
+Contains specification documents defining requirements for database setup and recovery procedures.
 ## files
 ## arch
-Specification-driven documentation pattern using date-versioned archival storage for system recovery procedures.
+Documentation-driven specification pattern with structured requirement definitions for system recovery capabilities.
 ## tags
 -
 ## symbols
@@ -1,18 +1,18 @@
-# archive/2026-05-18-database-setup-recovery/specs/database-initialization (index)
-dir: archive/2026-05-18-database-setup-recovery/specs/database-initialization
+# 2026-05-18-database-setup-recovery/specs/database-initialization (index)
+dir: 2026-05-18-database-setup-recovery/specs/database-initialization

 ## role
 Defines software requirements for automatic database initialization, connection resilience, seed data management, and startup error messaging using Gherkin-style scenarios.
 ## parent
-index: archive/2026-05-18-database-setup-recovery/specs/.pi-map.index.md
-map: archive/2026-05-18-database-setup-recovery/specs/.pi-map.md
+index: 2026-05-18-database-setup-recovery/specs/.pi-map.index.md
+map: 2026-05-18-database-setup-recovery/specs/.pi-map.md
 ## children
 -
 ## files
 - spec.md
 ## links
-index: archive/2026-05-18-database-setup-recovery/specs/database-initialization/.pi-map.index.md
-map: archive/2026-05-18-database-setup-recovery/specs/database-initialization/.pi-map.md
+index: 2026-05-18-database-setup-recovery/specs/database-initialization/.pi-map.index.md
+map: 2026-05-18-database-setup-recovery/specs/database-initialization/.pi-map.md
 ## workflows
 -
 ## dirty
@@ -1,14 +1,14 @@
-# archive/2026-05-18-database-setup-recovery/specs/database-initialization
-dir: archive/2026-05-18-database-setup-recovery/specs/database-initialization
+# 2026-05-18-database-setup-recovery/specs/database-initialization
+dir: 2026-05-18-database-setup-recovery/specs/database-initialization

-index: archive/2026-05-18-database-setup-recovery/specs/database-initialization/.pi-map.index.md
+index: 2026-05-18-database-setup-recovery/specs/database-initialization/.pi-map.index.md

 ## role
 Defines software requirements for automatic database initialization, connection resilience, seed data management, and startup error messaging using Gherkin-style scenarios.
 ## files
 - spec.md | Defines software requirements for automatic database initialization, connection resilience, seed data management, and startup error messaging using Gherkin-style scenarios.
 ## arch
-Behavior-driven specification using Gherkin syntax to define acceptance criteria for database lifecycle operations.
+Behavior-driven specification using Gherkin syntax (Given/When/Then) to define executable requirements for database lifecycle management.
 ## tags
 spec, defines, software, requirements, automatic, database, initialization, connection
 ## symbols
@@ -1,23 +1,23 @@
-# archive/2026-05-18-simplify-authentik-auth (index)
-dir: archive/2026-05-18-simplify-authentik-auth
+# 2026-05-18-simplify-authentik-auth (index)
+dir: 2026-05-18-simplify-authentik-auth

 ## role
-Contains historical design documents and planning artifacts for a completed authentication system migration from JWT tokens to session-based cookies with Authentik OAuth2 integration.
+Authentication system migration package for replacing JWT/OIDC token-based auth with session-based cookies using Authentik OAuth2.
 ## parent
-index: archive/.pi-map.index.md
-map: archive/.pi-map.md
+index: ./.pi-map.index.md
+map: ./.pi-map.md
 ## children
- archive/2026-05-18-simplify-authentik-auth/specs
-  index: archive/2026-05-18-simplify-authentik-auth/specs/.pi-map.index.md
-  map: archive/2026-05-18-simplify-authentik-auth/specs/.pi-map.md
+- 2026-05-18-simplify-authentik-auth/specs
+  index: 2026-05-18-simplify-authentik-auth/specs/.pi-map.index.md
+  map: 2026-05-18-simplify-authentik-auth/specs/.pi-map.md
 ## files
 - .openspec.yaml
 - design.md
 - proposal.md
 - tasks.md
 ## links
-index: archive/2026-05-18-simplify-authentik-auth/.pi-map.index.md
-map: archive/2026-05-18-simplify-authentik-auth/.pi-map.md
+index: 2026-05-18-simplify-authentik-auth/.pi-map.index.md
+map: 2026-05-18-simplify-authentik-auth/.pi-map.md
 ## workflows
 -
 ## dirty
@@ -1,17 +1,17 @@
-# archive/2026-05-18-simplify-authentik-auth
-dir: archive/2026-05-18-simplify-authentik-auth
+# 2026-05-18-simplify-authentik-auth
+dir: 2026-05-18-simplify-authentik-auth

-index: archive/2026-05-18-simplify-authentik-auth/.pi-map.index.md
+index: 2026-05-18-simplify-authentik-auth/.pi-map.index.md

 ## role
-Contains historical design documents and planning artifacts for a completed authentication system migration from JWT tokens to session-based cookies with Authentik OAuth2 integration.
+Authentication system migration package for replacing JWT/OIDC token-based auth with session-based cookies using Authentik OAuth2.
 ## files
 - .openspec.yaml | Defines an OpenSpec configuration file with schema type and creation date metadata
 - design.md | Design document for migrating a backend authentication system from JWT tokens to session cookies with OAuth2/Authentik integration | dep: Authentik (OAuth2), Redis (optional), backend database, frontend
 - proposal.md | Proposes simplifying an Authentik-based authentication system by replacing JWT/token-based auth with session-based cookies | dep: Authentik, OAuth2, session cookies, database user model, frontend auth state
 - tasks.md | Project task list for migrating an application from JWT/OIDC authentication to session-based authentication using Authentik | dep: Authentik, Alembic, python-jose, ruff, mypy, pytest
 ## arch
-Document-driven design process using OpenSpec schema configuration, structured design/proposal/task documents, and date-based archival organization for tracking architectural decisions and migration planning.
+Documentation-driven migration planning with specification files (OpenSpec), design documents, proposals, and task tracking—no implementation code, purely planning artifacts for a backend auth architecture change.
 ## tags
 authentik, authentication, design, jwt, session, .openspec, migrating, system
 ## symbols
@@ -1,18 +1,18 @@
-# archive/2026-05-18-simplify-authentik-auth/specs (index)
-dir: archive/2026-05-18-simplify-authentik-auth/specs
+# 2026-05-18-simplify-authentik-auth/specs (index)
+dir: 2026-05-18-simplify-authentik-auth/specs

 ## role
-Defines technical specifications for a streamlined Authentik-based OAuth2 authentication system with stateless session management
+Defines technical specifications for a simplified OAuth2 authentication system using Authentik with stateless signed session cookies
 ## parent
-index: archive/2026-05-18-simplify-authentik-auth/.pi-map.index.md
-map: archive/2026-05-18-simplify-authentik-auth/.pi-map.md
+index: 2026-05-18-simplify-authentik-auth/.pi-map.index.md
+map: 2026-05-18-simplify-authentik-auth/.pi-map.md
 ## children
 -
 ## files
 - spec.md
 ## links
-index: archive/2026-05-18-simplify-authentik-auth/specs/.pi-map.index.md
-map: archive/2026-05-18-simplify-authentik-auth/specs/.pi-map.md
+index: 2026-05-18-simplify-authentik-auth/specs/.pi-map.index.md
+map: 2026-05-18-simplify-authentik-auth/specs/.pi-map.md
 ## workflows
 -
 ## dirty
@@ -1,14 +1,14 @@
-# archive/2026-05-18-simplify-authentik-auth/specs
-dir: archive/2026-05-18-simplify-authentik-auth/specs
+# 2026-05-18-simplify-authentik-auth/specs
+dir: 2026-05-18-simplify-authentik-auth/specs

-index: archive/2026-05-18-simplify-authentik-auth/specs/.pi-map.index.md
+index: 2026-05-18-simplify-authentik-auth/specs/.pi-map.index.md

 ## role
-Defines technical specifications for a streamlined Authentik-based OAuth2 authentication system with stateless session management
+Defines technical specifications for a simplified OAuth2 authentication system using Authentik with stateless signed session cookies
 ## files
 - spec.md | Defines a simplified OAuth2 authentication flow using Authentik with stateless signed session cookies | dep: Authentik, HMAC-SHA256, OAuth2
 ## arch
-Specification-driven design documenting a stateless authentication architecture using signed JWT cookies to eliminate server-side session storage
+Specification-driven design using markdown documentation to define authentication flow requirements before implementation
 ## tags
 oauth2, authentik, spec, defines, simplified, authentication, flow, stateless
 ## symbols
--- a/Show More
+++ b/Show More