fix(nebula): republish 19 bake receipts with their moved recipe paths

[alowpoly]

Change

Deploy run 38099305364 failed in "Build the site". #1513 moved the recipe paths of 19 nebula volumes into each object's folder, but each volume's published receipt (prepared/delivery.json) still recorded the old paths. The deploy build compares receipt and recipe, found them different, re-baked the volumes on the runner and stopped on m42-volume with "Compact input belongs to another object".

Now each of the 19 receipts records its current recipe. Only the receipt's recipe field changes; no other baked file changes. The 19 inventories pin the new receipts.

Prepared assets

• Published the bytes: 19 receipts, uploaded with the publish tool's single-key wrangler call.
• Committed the refreshed inventory.json, and no baked files.
• No bake: every recipe difference is a moved path, and the moved inputs are byte-identical or differ only in path strings.

Evidence and limits

Proves the change: every nebula receipt on R2 compared with its recipe. On main 19 of 40 differ; on this branch 0 differ. All 19 new keys return 200 as application/json from the asset host, byte-identical to the local files.

Clean: check-no-hashes.

Not run: the deploy build itself; the next Deploy run is the test. sun-cor1-density has no receipt in its inventory, as on main.

Known and unchanged: M42's replay fails whenever it runs, because its compact input says m42 and its recipe says m42-volume. This change only stops the deploy from reaching it.

PR rules: titles, PDS4 provenance and ISO plain language.