# openspec/changes/archive/2026-07-09-service-storage-harness dir: openspec/changes/archive/2026-07-09-service-storage-harness index: openspec/changes/archive/2026-07-09-service-storage-harness/.pi-map.index.md ## role Specification and change-management archive for the "service-storage-harness" feature, documenting the full OpenSpec SDD lifecycle from proposal through verification. ## files - apply-progress.md | Documents the completion progress and detailed deliverables of a 35-task "service-storage-harness" software feature implementation across four code slices. - archive-report.md | This file is an archive report documenting the completion and archival of the `service-storage-harness` change within an OpenSpec SDD workflow. | dep: OpenSpec, git, pytest, ruff, npm, vitest - design.md | This document outlines the software design for a service storage harness and qBittorrent integration, detailing database migrations, per-service data isolation, and widget data retrieval. | dep: sqlite3, requests, asyncio - proposal.md | Proposal document describing a service storage harness abstraction with qBittorrent widget integration and MediaIndex migration for a homelab management dashboard. | dep: SQLite, Pydantic, recharts, @tanstack/react-table, Fernet, qBittorrent Web API - spec.md | Defines acceptance requirements and specifications for implementing a service storage harness with qBittorrent widgets, MediaIndex migration, and cascade-delete wiring. - sync-report.md | Documentation report detailing the synchronization of the `service-storage-harness` OpenSpec change artifacts into a canonical specification format. | dep: openspec - tasks.md | Task breakdown document outlining a phased implementation plan for a service storage harness, qBittorrent integration, and MediaIndex migration across backend and frontend. - verify-report.md | Fresh-context adversarial verification report documenting the read-only test and spec-coverage results for the `service-storage-harness` change. ## arch Document-driven specification archive following a structured SDD workflow (proposal → design → spec → tasks → implementation → verification → archival) with multiple artifacts capturing each phase. ## tags service, report, storage, harness, openspec, qbittorrent, progress, archive ## symbols - ## workflows - ## dirty -