fix(data): rename MuseScore to MuseScore Studio, add its macOS bundle id

[jeffreylouden]

Fixes AUREO-1311

Description

The desktop notation app has been MuseScore Studio since 4.3. This PR is the catalog half of the five-site rename in AUREO-1311. The other four sites are changed in existential-engineering/racks#3781: the three scanner tables and packages/lib/src/constants/daws.ts.

Changes in data/software/muse-group-musescore.yaml:

• name: MuseScore → name: MuseScore Studio
• searchTerms: MuseScore Studio → MuseScore, because "MuseScore" is still the umbrella name for the ecosystem. MuseScore 4 and MuseHub stay.
• New identifiers.bundle: org.musescore.MuseScore. Upstream sets it from MUSE_APP_NAME_MACHINE_READABLE_COMPAT, and it is unchanged through v4.7.5 (see version.cmake at that tag). Under the identifier fallback rule, bundle fills standalone, which is the entry's only format. Ableton Live and Bitwig use the same pattern.
• The slug, id and versions are unchanged. The only listed version, 4.7.5, shipped as MuseScore Studio, so there is no pre-4.3 history to keep.

Why the identifier is part of the rename

Studio tries an identifier match (heuristic 2) before it falls back to the name score, and the macOS DAW scanner reports the bundle id as the identifier. With this id in the catalog, macOS matches the entry on every Studio build, whether its scanner reports the old name MuseScore or the new one. Without the id, MuseScore against MuseScore Studio scores 0.85, and validateMatch rejects it (measured in the issue).

On Windows and Linux the scanner's identifier is not a stable id: it is the uninstall display name on Windows and the .desktop file name on Linux. On those platforms the name stays the match key.

Merge order

existential-engineering/racks#3781 merges first. Merge this PR only once a Studio release that carries it has shipped. Every installed Studio downloads the newest catalog.sqlite:

• If this PR merges first, every current Windows and Linux install stops matching MuseScore.
• If racks ships first, new builds miss MuseScore on Windows and Linux only until this PR publishes.

Even in the right order, Studio builds older than racks#3781 will stop matching MuseScore on Windows and Linux once this publishes, because their scanner still says MuseScore. macOS is covered by the identifier. Merging accepts that cost, as AUREO-1311's "both sides move together" plan implies.

Type of Change

• New software/plugin entry
• New hardware entry
• New manufacturer entry
• Update to existing entry
• Bug fix
• Schema or script change

Checklist

• I have run pnpm validate and it passes (also pnpm typecheck and pnpm format:check)
• YAML files follow the existing format
• Manufacturer exists (or I'm adding it in this PR)
• Categories and formats are from the schema files
• Identifiers are accurate, if provided (bundle IDs, etc.). Source: MuseScore v4.7.5 version.cmake and src/app/CMakeLists.txt.
• Any hp I added or changed names its source in the description

Additional Notes

What changes in racks#3781:

• name: "MuseScore Studio" in the Linux, macOS and Windows scanner tables and in packages/lib/src/constants/daws.ts
• The macOS app_name_pattern / appNamePattern is widened to ^MuseScore( Studio)?( \d+)?$, with a Rust test.

Upstream facts behind the pattern, checked at v4.7.5:

• The stable macOS DMG still ships MuseScore 4.app; buildscripts/ci/macos/package.sh has a TODO to rename it (Finish renaming to Studio, now that there is a major version number change musescore/MuseScore#32235). Upstream main already packages MuseScore Studio.app, with bundle id org.musescore.MuseScoreStudio5.
• Current macOS installs are therefore already detected through the bundle id. The wider pattern is for 5.0.
• On Linux, the .desktop file's Name= is MuseScore Studio 4.7, which the Linux table's musescore substring already matches.

The red audit check comes from dependency advisories already present on main and is not caused by this PR. The tested fix is in the comment below.

🤖 Generated with Claude Code

https://claude.ai/code/session_01TxMVXrJziUWrnvcksQgLM1

Summary by CodeRabbit

• Updates
  • Renamed the catalog entry to MuseScore Studio.
  • Kept “MuseScore” as a search term and added its macOS app identifier for matching.

[changeset-bot]

🦋 Changeset detected

Latest commit: ebf85ba

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package

Name	Type
catalog	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

• Configuration used: Repository: existential-engineering/catalog/.coderabbit.yaml
• Review profile: CHILL
• Plan: Advanced
• Run ID: a9d63d13-6ae3-4966-a78f-caa7d0f3bef0

📥 Commits

Reviewing files that changed from the base of the PR and between 347c298 and ebf85ba.

📒 Files selected for processing (2)

• .changeset/musescore-studio.md
• data/software/muse-group-musescore.yaml

Included review availability: This review used your included allowance. 8 included reviews remain after this review. Your included PR review attempts over the past 7 days set your current allowance at 10 reviews per hour.

---

Walkthrough

The catalog entry is renamed to MuseScore Studio. It uses “MuseScore” as a search term and adds the macOS bundle identifier org.musescore.MuseScore. A patch changeset records the catalog update.

Changes

MuseScore Studio catalog

Layer / File(s)	Summary
Catalog identity and matching data/software/muse-group-musescore.yaml, .changeset/musescore-studio.md	The catalog entry is renamed to MuseScore Studio, uses “MuseScore” as a search term, and adds the org.musescore.MuseScore identifier. The changeset describes the update.

Priority: ⬇️ Low

Estimated code review effort: 1 (Trivial) | ~3 minutes

Change: Bug fix

Merge Risk: 🔵 Low · up to ebf85

This renames MuseScore to MuseScore Studio and adds a macOS bundle ID, so macOS matching should keep working. Older Windows and Linux Studio builds may stop recognizing the entry until the updated Studio release ships. Merge once that release is out, as the PR description already requests.

Architecture Summary

Architecture risk: 🔵 Low · up to ebf85

The change affects 1 system.

Changed systems: data

Architecture concerns
No architecture-level concerns identified.

Review details

Systems and components

• observed — data (service) was modified; 1 changed file maps to changed impact.

Before / after behavior

• observed — Modified behavior in data/software/muse-group-musescore.yaml: The catalog entry’s name changes from “MuseScore” to “MuseScore Studio.”
• observed — Modified behavior in data/software/muse-group-musescore.yaml: The search term changes from “MuseScore Studio” to “MuseScore.”
• observed — Modified behavior in data/software/muse-group-musescore.yaml: Adds an identifiers mapping with the bundle identifier org.musescore.MuseScore.
• observed — Modified behavior in .changeset/musescore-studio.md: Adds a patch changeset for the catalog with a release note describing the MuseScore Studio rename, retained search term, and macOS bundle identifier matching.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0…
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly and concisely describes the main changes: renaming MuseScore to MuseScore Studio and adding the macOS bundle identifier.

✨ Finishing Touches 💡 1

🧪 Generate unit tests (beta)

• Commit to this branch
• Create a new PR

🛠️ Fix failing CI checks 💡

• Commit to this branch
• Create a new PR

• Autopilot · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

---

_{Comment @coderabbitai help to get the list of available commands.}

[jeffreylouden]

audit is red, and the cause is not in this PR. pnpm audit --audit-level=high reports two new advisories against packages already pinned in main's lockfile. This PR changes no dependency files: the diff is one YAML entry and a changeset. The same failure reproduces locally on the unchanged lockfile.

• shell-quote@1.10.0 (critical, GHSA-pqg4-j6r4-53mv), via @changesets/cli > launch-editor. Patched in 1.11.0.
• source-map-js@1.2.1 (high, GHSA-68fv-2mgg-jv7q), via vitest > vite > postcss. Patched in 1.2.2.

I searched the open PRs and found no fix. I can't open one from this session, because it may only push to this PR's branch, and dependency changes would widen this PR. Here is the fix I tested locally. With these overrides, pnpm install --no-frozen-lockfile followed by pnpm audit reports "No known vulnerabilities found":

--- a/pnpm-workspace.yaml
+++ b/pnpm-workspace.yaml
@@ -27,6 +27,10 @@
 # - esbuild >=0.28.1: vite/tsx pull esbuild@0.28.0, vulnerable to
 #   GHSA-g7r4-m6w7-qqqr (arbitrary file read via dev server). Patched in 0.28.1.
+# - shell-quote >=1.11.0: @changesets/cli > launch-editor pulls 1.10.0,
+#   GHSA-pqg4-j6r4-53mv (critical). Patched in 1.11.0.
+# - source-map-js >=1.2.2: vitest > vite > postcss pulls 1.2.1,
+#   GHSA-68fv-2mgg-jv7q (event-loop DoS). Patched in 1.2.2.
 #
@@ -47,3 +51,5 @@
 overrides:
   vite: ">=8.0.16 <9"
   esbuild: ">=0.28.1"
+  shell-quote: ">=1.11.0"
+  source-map-js: ">=1.2.2"

The lockfile change also needs regenerating with pnpm install; it touches 18 lines. I did not re-run the job: the failure follows from the lockfile, so a re-run would fail the same way. The open import PRs (#927 and #929–#932) are presumably blocked by the same check. Once a fix lands on main, I'll merge main into this branch.

As the PR body says, this PR must still not merge before the racks scanner rename ships.

---

Generated by Claude Code