Developer

Audience: Contributors and future maintainers. Goal: Understand code map and verification expectations. Type: explanation

Start with the page that matches the job in front of you. The docs keep human workflow pages separate from compact reference so you can read only what you need.

Pages

• Architecture: backend, database, frontend, and tools.
• Development: local setup and commands.
• Testing and verification: risk-based checks.
• Release checklist: final audit before publishing.

Privacy habit

Use placeholders such as <library-db> and <music-folder> in notes, issues, and examples. Do not publish private paths, usernames, real track names, or personal library data.