Carmine Paolino
3a4db99577
CONTRIBUTING.md says what fits and what does not: no other audio sources, no DRM circumvention, no browser engine, no telemetry, no hosted service. AGENTS.md and the Copilot instructions hold coding agents to the same lines, the issue forms and a pull request template ask for the reading up front, and CI now runs the full battery by default: clippy and tests with and without features, doc lints, and the docs site build. The guide's "does not do" list catches up with lyrics having shipped and says why lossless is out for now.
1.0 KiB
Copilot instructions for Fastpotify
Use AGENTS.md and CONTRIBUTING.md as the source of truth for every change
and review.
When reviewing a pull request, prioritize correctness, regressions, product fit, cross-platform behaviour, UI-thread blocking, credential exposure, and unnecessary dependencies. Treat violations of the documented product boundaries as blockers. In particular, flag alternate sources for Spotify audio, DRM circumvention, embedded browser engines, telemetry, and hosted Fastpotify services.
Check that behavioural changes have focused tests and that user-visible settings, files, and network access are documented. For UI changes, ask for visual evidence when the pull request does not provide it. Do not spend review comments on formatting that rustfmt already enforces.
CI passing is necessary but not proof that a change is correct. Give concrete, actionable findings tied to changed lines; avoid generic summaries and do not approve or recommend merging code that you cannot substantively evaluate.