alex/manage
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

chore: regenerate stale .pi-map.md / .pi-map.index.md project maps

Browse Source 
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
Download Patch File Download Diff File Expand all files Collapse all files
openspec/changes/archive/observability-service-registry/.pi-map.index.md
+1 -1
View File
@@ -2,7 +2,7 @@
dir: openspec/changes/archive/observability-service-registry
## role
Proposal and design documentation package detailing the migration of observability services from environment-variable configuration to a dynamic service registry model.
OpenSpec change proposal package documenting the migration of observability services (Alertmanager, Grafana, Prometheus) from environment-variable configuration to a dynamic service registry model.
## parent
index: openspec/changes/archive/.pi-map.index.md
map: openspec/changes/archive/.pi-map.md
openspec/changes/archive/observability-service-registry/.pi-map.md
+2 -2
View File
@@ -4,13 +4,13 @@ dir: openspec/changes/archive/observability-service-registry
index: openspec/changes/archive/observability-service-registry/.pi-map.index.md
## role
Proposal and design documentation package detailing the migration of observability services from environment-variable configuration to a dynamic service registry model.
OpenSpec change proposal package documenting the migration of observability services (Alertmanager, Grafana, Prometheus) from environment-variable configuration to a dynamic service registry model.
## files
- design.md | Design document describing the migration of observability services from environment-variable configuration to a dynamic service registry model.
- proposal.md | This file is a technical proposal document outlining changes to migrate observability services (Alertmanager, Grafana, Prometheus) from environment variables to a first-class service registry.
- tasks.md | Task breakdown document detailing a 5-slice implementation plan for migrating observability services (Alertmanager, Grafana, Prometheus) to a service registry pattern with UI-based configuration.
## arch
OpenSpec change-documentation pattern consisting of three structured Markdown artifacts: a proposal (intent), a design (technical approach), and tasks (implementation breakdown).
OpenSpec structured proposal pattern consisting of three documents: design.md (technical design), proposal.md (change justification and scope), and tasks.md (incremental implementation plan broken into 5 slices).
## tags
design, document, observability, services, service, registry, proposal, environment
## symbols