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:
Developer
2026-07-09 14:05:56 +00:00
parent 98f17f6e5d
commit ec7ebd7013
189 changed files with 1215 additions and 428 deletions
@@ -4,11 +4,11 @@ dir: openspec/changes/archive/configurable-dashboard-widgets/specs/dashboard-wid
index: openspec/changes/archive/configurable-dashboard-widgets/specs/dashboard-widgets/.pi-map.index.md
## role
Defines the specification document for a Phase 1 configurable dashboard widget system with persisted layouts and REST API access.
Specification document defining Phase 1 requirements for a configurable dashboard widget system with persistence, REST API, and compile-time registries.
## files
- spec.md | Define Phase 1 requirements for a persisted, configurable dashboard widget system with closed compile-time registries, SQLite persistence, REST API, and independent widget data fetching. | dep: SQLite, Pydantic, TanStack Query, shadcn/ui, JWT/API-key auth, Jellyfin client, Grafana/Prometheus settings, SSH task runner, BackupDashboardSummary
## arch
Specification document outlining a closed compile-time registry pattern with SQLite persistence, REST API layer, and independent widget data fetching architecture.
Specification-driven design pattern defining bounded context requirements for a widget system using closed registries, SQLite persistence layer, REST API endpoints, and independent data-fetching widgets.
## tags
widget, sqlite, api, spec, define, phase, requirements, persisted
## symbols