chore: regenerate stale .pi-map.md / .pi-map.index.md project maps
Project map had drifted: claimed recharts unused (was used), ObservabilityPage.tsx
exists (refactored to service-tabs/), missed JellyfinNowPlayingWidget +
authentik/backups service types. Regenerate to reflect post-change reality:
new Qbittorrent/LineSeriesChart/Prometheus{Gauge,Mean}Widget files,
service_data.py/qbittorrent_store.py, canonical prometheus-charting +
service-storage specs, archived changes.
This commit is contained in:
@@ -2,7 +2,7 @@
|
||||
dir: docs/superpowers
|
||||
|
||||
## role
|
||||
Documentation directory for advanced features, plugins, or capabilities (currently empty).
|
||||
Documentation directory for the project's "superpowers" feature set, concepts, or capabilities.
|
||||
## parent
|
||||
index: docs/.pi-map.index.md
|
||||
map: docs/.pi-map.md
|
||||
|
||||
@@ -4,10 +4,10 @@ dir: docs/superpowers
|
||||
index: docs/superpowers/.pi-map.index.md
|
||||
|
||||
## role
|
||||
Documentation directory for advanced features, plugins, or capabilities (currently empty).
|
||||
Documentation directory for the project's "superpowers" feature set, concepts, or capabilities.
|
||||
## files
|
||||
## arch
|
||||
Flat file structure intended for Markdown or supplementary documentation resources.
|
||||
Flat file-based documentation structure with no code files present.
|
||||
## tags
|
||||
-
|
||||
## symbols
|
||||
|
||||
@@ -2,7 +2,7 @@
|
||||
dir: docs/superpowers/plans
|
||||
|
||||
## role
|
||||
Documentation directory containing detailed implementation plans for specific project features or standalone systems.
|
||||
Documentation directory containing implementation plans for major system features and infrastructure improvements.
|
||||
## parent
|
||||
index: docs/superpowers/.pi-map.index.md
|
||||
map: docs/superpowers/.pi-map.md
|
||||
|
||||
@@ -4,11 +4,11 @@ dir: docs/superpowers/plans
|
||||
index: docs/superpowers/plans/.pi-map.index.md
|
||||
|
||||
## role
|
||||
Documentation directory containing detailed implementation plans for specific project features or standalone systems.
|
||||
Documentation directory containing implementation plans for major system features and infrastructure improvements.
|
||||
## files
|
||||
- 2026-05-11-backup-monitoring.md | Implementation plan for building a standalone backup monitoring system with FastAPI backend, SQLite storage, and React frontend that receives HTTP reports, tracks jobs/runs/alerts, and provides dashboards with validation and alerting. | dep: FastAPI, SQLite, Pydantic, React, TypeScript, TanStack Query, D3, MUI, Python uuid/time/json modules
|
||||
## arch
|
||||
Flat-file markdown documentation following a date-prefixed naming convention (`YYYY-MM-DD-feature.md`) to organize chronological planning artifacts.
|
||||
Date-prefixed Markdown files following a structured planning format with technical requirements, architecture decisions, and implementation steps.
|
||||
## tags
|
||||
backup, monitoring, fastapi, sqlite, react, 2026, 05, 11
|
||||
## symbols
|
||||
|
||||
@@ -2,7 +2,7 @@
|
||||
dir: docs/superpowers/specs
|
||||
|
||||
## role
|
||||
Contains design specification documents for major features and system modules.
|
||||
Documentation directory containing design specifications for system features
|
||||
## parent
|
||||
index: docs/superpowers/.pi-map.index.md
|
||||
map: docs/superpowers/.pi-map.md
|
||||
|
||||
@@ -4,11 +4,11 @@ dir: docs/superpowers/specs
|
||||
index: docs/superpowers/specs/.pi-map.index.md
|
||||
|
||||
## role
|
||||
Contains design specification documents for major features and system modules.
|
||||
Documentation directory containing design specifications for system features
|
||||
## files
|
||||
- 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 files following a specification-driven development pattern, each documenting complete system designs including storage, APIs, alerting, and frontend integration.
|
||||
Single-file design documents using structured Markdown with architectural decisions, data models, and component descriptions
|
||||
## tags
|
||||
design, backup, monitoring, sqlite, react, 2026, 05, 11
|
||||
## symbols
|
||||
|
||||
Reference in New Issue
Block a user