music-release-metadata-linterlisted

# Music Release Metadata Linter ## Overview Audit a music or media project folder and produce a practical release-readiness report. The linter should help creators find missing files, weak metadata, rights risks, split gaps, platform-delivery blockers, and Suede intake issues before a release or transfer package is created. Public v1 is offline-first: inspect local files and supplied metadata, do not upload to Suede, write to a registry, call distribution APIs, request private keys, or claim legal clearance. ## Workflow 1. Identify the source folder or supplied files. 2. Ask for the output location if it is not obvious. 3. Read `references/lint-rules.md` for the lint categories and severity model. 4. If working on a local folder, run `scripts/lint_release.py` to generate `release-lint-report.md` and `release-lint-report.json`. 5. Read `references/fix-guidance.md` when turning findings into specific next actions. 6. If the user wants Suede intake prep, use the report to decide whether to invoke or recommend the `suede-rights-passport` package workflow. 7. Do not invent release metadata. Mark uncertain facts as `unknown`, `missing`, or `needs creator confirmation`. 8. End with a concise summary: report path, score, highest-severity findings, and next fixes. ## Quick Start ```bash python3 /path/to/music-release-metadata-linter/scripts/lint_release.py \ /path/to/music-project \ --output /path/to/release-lint-output ``` If the source folder contains a metadata file, pa