chore(project-map): refresh .pi-map role/arch summaries

Regenerate project map artifacts across backend, docs, openspec, and
root to refresh role descriptions and architectural notes after recent
service-registry and observability changes.

Co-authored-by: el Gentleman <gentleman@pi.local>

docs/.pi-map.index.md

@@ -2,7 +2,7 @@
 dir: docs
 
 ## role
-Documentation package containing architectural plans, requirements, and operational guides for the "Manage" media library application and its observability stack.
+Documentation directory containing architecture, planning, and operational reference materials for the project.
 ## parent
 index: ./.pi-map.index.md
 map: ./.pi-map.md

docs/.pi-map.md

@@ -4,16 +4,16 @@ dir: docs
 index: docs/.pi-map.index.md
 
 ## role
-Documentation package containing architectural plans, requirements, and operational guides for the "Manage" media library application and its observability stack.
+Documentation directory containing architecture, planning, and operational reference materials for the project.
 ## files
 - MIGRATION_PLAN.md | This file documents the architecture, API design, and step-by-step migration plan for transitioning an application from a Streamlit monolith to a FastAPI and React SPA. | dep: FastAPI, React, Vite, TypeScript, pydantic-settings, @tanstack/react-query, ag-grid-react, recharts, tailwindcss
-- REQUIREMENTS.md | Living requirements and decision log document for "Manage," a web application for browsing Jellyfin media libraries and inspecting corresponding media files on disk over SSH. | dep: React, TypeScript, shadcn/ui, Tailwind CSS, lucide-react, TanStack Table, Vitest, Jellyfin API, SQLite, Prometheus, Grafana, Alertmanager, OIDC
+- REQUIREMENTS.md | This file is a living requirements and decision log detailing the product goals, architecture, and feature specifications for a web application that manages a remote Jellyfin media library and inspects server files over SSH.
 - monitoring-logging-design.md | Design document detailing a self-hosted observability architecture (metrics, logs, dashboards, alerting) for integration with a platform called Manage. | dep: Prometheus, Grafana, Node Exporter, Grafana Loki, Grafana Alloy, Alertmanager, Authentik, Traefik
 - observability-runbooks.md | Provides operational runbooks, configuration, and maintenance procedures for deploying and managing a standalone observability stack. | dep: Prometheus, Grafana, Loki, Alloy, Alertmanager, Node Exporter, Docker Compose, Traefik
 ## arch
-Static markdown documentation organized as living specs, design docs, and runbooks without code structure or dependencies.
+Flat collection of standalone Markdown documents covering requirements tracking, migration planning, and observability/operational runbooks.
 ## tags
-react, design, observability, migration, plan, requirements, prometheus, grafana
+design, react, observability, architecture, migration, plan, requirements, runbooks
 ## symbols
 -
 ## workflows

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

@@ -2,7 +2,7 @@
 dir: docs/superpowers
 
 ## role
-Documentation directory for advanced features, capabilities, or customization guides within the project.
+Documentation directory for advanced features, plugins, or capabilities (currently empty).
 ## parent
 index: docs/.pi-map.index.md
 map: docs/.pi-map.md

docs/superpowers/.pi-map.md

@@ -4,10 +4,10 @@ dir: docs/superpowers
 index: docs/superpowers/.pi-map.index.md
 
 ## role
-Documentation directory for advanced features, capabilities, or customization guides within the project.
+Documentation directory for advanced features, plugins, or capabilities (currently empty).
 ## files
 ## arch
-Flat-file documentation structure (currently empty of content files), serving as a namespace for specialized or extended documentation topics.
+Flat file structure intended for Markdown or supplementary documentation resources.
 ## tags
 -
 ## symbols

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

@@ -2,14 +2,13 @@
 dir: docs/superpowers/specs
 
 ## role
-Specification documents defining approved architectural designs for major features of the media library viewer project.
+Contains design specification documents for major features and system modules.
 ## parent
 index: docs/superpowers/.pi-map.index.md
 map: docs/superpowers/.pi-map.md
 ## children
 -
 ## files
-- 2026-05-08-obsidian-documentation-design.md
 - 2026-05-11-backup-monitoring-design.md
 ## links
 index: docs/superpowers/specs/.pi-map.index.md

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

@@ -4,14 +4,13 @@ dir: docs/superpowers/specs
 index: docs/superpowers/specs/.pi-map.index.md
 
 ## role
-Specification documents defining approved architectural designs for major features of the media library viewer project.
+Contains design specification documents for major features and system modules.
 ## files
-- 2026-05-08-obsidian-documentation-design.md | Defines the approved documentation structure for an Obsidian-based knowledge vault for the Manage media library viewer project, targeting developers, contributors, operators, and deployers. | dep: Obsidian, FastAPI, React, TypeScript, Vite, MUI, D3, AG Grid, Docker, Traefik, Authentik, Paramiko, PyJWT, SQLite
 - 2026-05-11-backup-monitoring-design.md | Design document for a standalone backup monitoring module with HTTP API ingestion, SQLite storage, automated alerting, and React frontend for a media library viewer application. | dep: FastAPI, React, SQLite, OIDC/JWT, D3, existing MonitoringPoller
 ## arch
-Dated Markdown design documents following a specification pattern, each capturing requirements, architecture decisions, and implementation plans for distinct system components.
+Dated markdown files following a specification-driven development pattern, each documenting complete system designs including storage, APIs, alerting, and frontend integration.
 ## tags
-design, obsidian, 2026, 05, documentation, react, sqlite, backup
+design, backup, monitoring, sqlite, react, 2026, 05, 11
 ## symbols
 -
 ## workflows