Should you build your own Spotify Premium?

Build a closest honest personal substitute for Spotify Premium in an empty repository.
Use Python 3.12, FastAPI, SQLite, ffmpeg, and a local web interface; do not offer alternative stacks.
The core loop is: index and stream a legally owned personal music library, analyze local files, and provide playlists and search for private playback.
Make the first run work locally with one documented command.
Store all user data locally by default and make export straightforward.
Put secrets in .env, ship .env.example, and never commit credentials.
Index only user-selected folders and preserve source audio without modification.
Read tags and artwork, calculate loudness and waveform data, and detect exact duplicates by hash.
Provide albums, artists, playlists, search, queue, favorites, and resumable local playback.
Add optional creator tools for trim, normalize, split stems through a local model, and export new files.
Keep all rights and source information attached to imported tracks and display it during export.
Document that the application does not provide music, licensing, distribution, or royalty collection.
Include clear empty, loading, success, and recoverable error states.
Add input validation, safe filenames, and graceful handling of unavailable APIs.
Write focused tests for the core transformation and one end-to-end happy path.
Create a README with setup, architecture, permissions, data location, and backup steps.
Do not add accounts, billing, telemetry, analytics, or a hosted control plane.
Do not claim to reproduce proprietary data, network liquidity, regulated access, or frontier infrastructure.
Deliberately leave out copyrighted catalog acquisition or sharing.
Deliberately leave out streaming-service circumvention.
Deliberately leave out royalty accounting, label distribution, and global content delivery.
Finish by running the tests and listing the exact commands used.