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>
This commit is contained in:
Developer
2026-06-26 09:10:19 +00:00
parent 7d252489de
commit 648320abfd
22 changed files with 55 additions and 57 deletions
+1 -4
View File
@@ -2,7 +2,7 @@
dir: openspec/changes
## role
Contains OpenSpec change records documenting proposed, accepted, and rejected modifications to the project's API specification or design.
Directory for tracking proposed and applied changes to the project's OpenAPI specification.
## parent
index: openspec/.pi-map.index.md
map: openspec/.pi-map.md
@@ -10,9 +10,6 @@ map: openspec/.pi-map.md
- openspec/changes/archive
index: openspec/changes/archive/.pi-map.index.md
map: openspec/changes/archive/.pi-map.md
- openspec/changes/jellyfin-service-registry
index: openspec/changes/jellyfin-service-registry/.pi-map.index.md
map: openspec/changes/jellyfin-service-registry/.pi-map.md
## files
## links
index: openspec/changes/.pi-map.index.md
+2 -2
View File
@@ -4,10 +4,10 @@ dir: openspec/changes
index: openspec/changes/.pi-map.index.md
## role
Contains OpenSpec change records documenting proposed, accepted, and rejected modifications to the project's API specification or design.
Directory for tracking proposed and applied changes to the project's OpenAPI specification.
## files
## arch
Artifact-based directory pattern storing individual change proposals as structured files (likely YAML or Markdown) for specification governance and audit trails.
Follows the "changes folder" pattern where each change proposal is stored as a structured markdown file describing modifications, rationale, and migration steps.
## tags
-
## symbols
+4 -1
View File
@@ -2,7 +2,7 @@
dir: openspec/changes/archive
## role
Archive directory for superseded or completed OpenSpec change proposals.
Archive directory for historical change records and specifications that have been completed or superseded.
## parent
index: openspec/changes/.pi-map.index.md
map: openspec/changes/.pi-map.md
@@ -16,6 +16,9 @@ map: openspec/changes/.pi-map.md
- openspec/changes/archive/decommission-monitoring-poller
index: openspec/changes/archive/decommission-monitoring-poller/.pi-map.index.md
map: openspec/changes/archive/decommission-monitoring-poller/.pi-map.md
- openspec/changes/archive/jellyfin-service-registry
index: openspec/changes/archive/jellyfin-service-registry/.pi-map.index.md
map: openspec/changes/archive/jellyfin-service-registry/.pi-map.md
- openspec/changes/archive/observability-service-registry
index: openspec/changes/archive/observability-service-registry/.pi-map.index.md
map: openspec/changes/archive/observability-service-registry/.pi-map.md
+2 -2
View File
@@ -4,10 +4,10 @@ dir: openspec/changes/archive
index: openspec/changes/archive/.pi-map.index.md
## role
Archive directory for superseded or completed OpenSpec change proposals.
Archive directory for historical change records and specifications that have been completed or superseded.
## files
## arch
Flat directory pattern serving as a historical repository of YAML or Markdown change specification files.
Simple file-based archive pattern storing obsolete or completed change documents without active processing logic.
## tags
-
## symbols
@@ -1,11 +1,11 @@
# openspec/changes/jellyfin-service-registry (index)
dir: openspec/changes/jellyfin-service-registry
# openspec/changes/archive/jellyfin-service-registry (index)
dir: openspec/changes/archive/jellyfin-service-registry
## role
Documentation and planning package for migrating Jellyfin service configuration from machine-level settings to a service-registry model.
Archived change specification for migrating Jellyfin configuration from machine-level settings to a service-registry model.
## parent
index: openspec/changes/.pi-map.index.md
map: openspec/changes/.pi-map.md
index: openspec/changes/archive/.pi-map.index.md
map: openspec/changes/archive/.pi-map.md
## children
-
## files
@@ -13,8 +13,8 @@ map: openspec/changes/.pi-map.md
- proposal.md
- tasks.md
## links
index: openspec/changes/jellyfin-service-registry/.pi-map.index.md
map: openspec/changes/jellyfin-service-registry/.pi-map.md
index: openspec/changes/archive/jellyfin-service-registry/.pi-map.index.md
map: openspec/changes/archive/jellyfin-service-registry/.pi-map.md
## workflows
-
## dirty
@@ -1,16 +1,16 @@
# openspec/changes/jellyfin-service-registry
dir: openspec/changes/jellyfin-service-registry
# openspec/changes/archive/jellyfin-service-registry
dir: openspec/changes/archive/jellyfin-service-registry
index: openspec/changes/jellyfin-service-registry/.pi-map.index.md
index: openspec/changes/archive/jellyfin-service-registry/.pi-map.index.md
## role
Documentation and planning package for migrating Jellyfin service configuration from machine-level settings to a service-registry model.
Archived change specification for migrating Jellyfin configuration from machine-level settings to a service-registry model.
## files
- design.md | Design document for completing the migration of Jellyfin service configuration from machine-level settings to service-registry instances, involving removal of legacy media_root and path_prefix fields across backend, frontend, and docs. | dep: integrations/jellyfin.py, integrations/jellyseerr.py, dependencies.py, settings_store.py, path_utils.py, routers/files.py, types/index.ts, Settings.tsx, docs/REQUIREMENTS.md, CHANGELOG.md
- proposal.md | Proposes completing a migration of Jellyfin configuration from machine-level settings to a service registry, removing dead fields and legacy UI elements.
- tasks.md | Defines a task checklist for completing the migration of Jellyfin from machine-level configuration to a service registry, including backend/frontend cleanup and documentation updates. | dep: backend/src/media_library_viewer_api/services/settings_store.py, backend/src/media_library_viewer_api/path_utils.py, backend/tests, frontend/src/types/index.ts, frontend/src/pages/Settings.tsx, frontend/src/pages/__tests__/Settings.test.tsx, docs/REQUIREMENTS.md, CHANGELOG.md
## arch
OpenSpec change-proposal structure consisting of three coordinated documents (design, proposal, tasks) that define the rationale, technical approach, and implementation checklist for a cross-stack refactoring effort.
OpenSpec change-document pattern consisting of three coordinated documents: proposal (rationale), design (technical approach), and tasks (implementation checklist).
## tags
py, settings, backend, frontend, src, jellyfin, service, md
## symbols