[repeat98]

Every Digitakt/Digitone module PR edited the same lines of two files, so each merge left the other open module PRs conflicted until they were refreshed and checked again. This is the first of two PRs that remove that.

What changes

• Changelog: release notes move from src/community/module-changelogs.json to one file per module, src/community/module-changelogs/<id>.json (Digitakt/Digitone: <machine>-<id>.json). Each file is that module's list of releases, unchanged.
• Generated, no longer committed: src/catalog/machine-modules.json and src/community/module-changelogs.json.
  • npm ci writes them through a new prepare script, and so do npm run check/build (first step) and npm run dev.
  • Every import keeps its path, so the app, the Worker and the scripts are unchanged.
  • Both are byte-for-byte or content-identical to what main had committed. Checked after merging current main, which includes Add RAM Record and Playback 1.3.1 for Digitakt OS 1.53 and 1.54 #572, Add Per-step Note Accumulator 1.1.1 for Digitakt OS 1.53 and 1.54 #574 and Add CC Assignment Names 2.1.1 for Digitakt OS 1.53 and 1.54 #576.
• Author-release scope: the same rules, per file. An author may edit only their own modules' notes files, and every published entry must stay. "Already published" for a Digi module now means its folder exists on main, which is exactly what the generated list contained.
• Worker deploys: a Digi manifest change now decides the Worker redeploy directly. Before, that decision came from the diff of the committed module list, so without this a Digi version bump would not have redeployed the Worker.
• Docs: AGENTS.md, ADD_A_MODULE, DEVELOPER_WORKFLOW, MODULE_AUTHOR_UPDATES, sdk/AGENTS.md and four draft notes now name the per-module file.

Still shared after this

vendor/elekloader/catalog/catalog.json and its lock. Every Digi module PR still adds pins there and changes the catalogue hash. The next PR builds that catalogue from each module's own import record. Until then, npm run catalog:resolve (#609) resolves those two files.

Octatrack FX PRs still serialize on sdk/catalog.json sourceRevision, which every compiled package depends on. That is a rebuild, not a merge conflict.

Open PRs that need a one-time move after this merges

#577, #560, #555 and #412 edit the old changelog file. After git merge main stops on the two deleted files:

1. Copy your module's entries into src/community/module-changelogs/<id>.json.
2. Run git rm src/catalog/machine-modules.json src/community/module-changelogs.json.
3. Run npm run prepare, then commit.

This PR did exactly that when merging main.

Tested

• npm run check -- --base origin/main passed after the final merge with main: 284 test files, 2,326 tests, plus lint, typecheck, bundle and sdk checks.
• Fresh-checkout case: with both generated files deleted, npm run prepare recreates them, identical to main's committed versions.
• New or changed tests:
  • a failing prepare stops the check before anything else runs;
  • an author may add notes to their own file, but not empty it, delete it, or edit another module's file;
  • a new Digi module triggers the Worker deploy.

🤖 Generated with Claude Code