[aharlap]

Pin Studio's main build containing Praxity/praxity-studio#1843. Exported decks fetch the previous and next slides' images at low priority, reducing photos appearing after slide text during navigation.

Studio version 0.3.0, source 5003117df3db719a22addcea3d735b04f42605e1, comes from producer run 39556177329. Admit, build and publish succeeded. Both archive inventories report that exact clean source revision and version. The producer now uses praxity-cli-0.3.0-macos-* filenames; the archive bytes are unchanged when renamed to Rubato's Studio asset convention.

The archives are hosted on Rubato's asset-only experimental prerelease v0.1.1-tools.experimental.20261021.1. It contains only two Studio archives, with no pack manifest or installer bootstrap. Latest remains v0.1.1; stable-channel configuration and all other tool pins are unchanged.

SHA-256:

• darwin-arm64: 6e6250325da26114ede9fe0583efc727780eb2e70f8d5122e5938a9d7433b789
• darwin-x64: 694d9a259d02983d513cf39cb7a1c51f3faa86ff7d4545d864c949a61b1cc6ec

Each digest matches all four checks:

1. The build job's output passed to publish as EXPECTED_ARM64_SHA256 or EXPECTED_X64_SHA256.
2. The archive downloaded from Studio candidate release ID 419233198, its GitHub asset digest and original .sha256 file.
3. Rubato's uploaded asset digest, authenticated asset readback and anonymous download from its published URL.
4. The checked-in pack.json digest, also asserted through each architecture's installation plan.

Rubato's verifyStudioArchive passes for both architectures, checking the exact clean revision, root, absence of links, payload inventory, legal files, notices, packaged skill and private-path scan.

The README and existing manifest/version tests follow the new pin. The legacy version-suffix test now supplies an explicit legacy version, preserving coverage while the current producer reports 0.3.0 without a SHA suffix. Updated manifest tests failed against the old pin before the manifest changed.

Validation:

• npm run validate and npm run validate:release pass using npm.cmd on Windows.
• Affected tests run under WSL: node --test test/manifest.test.mjs test/local-install.test.mjs test/update.test.mjs test/install.test.mjs test/install-platform.test.mjs. 112 pass, four baseline failures. All manifest, local-install, update and platform-selection tests pass.
• Four remote-manifest cases in test/install.test.mjs also fail on unchanged main 30db686. The fixture invokes real curl, which reports curl: (6) Could not resolve host: fixture.invalid and Manifest download failed; rerun the same command after resolving it. No test expectations were weakened.
• Native macOS installation jobs are left to CI.

Follow-up commit: pack.json records Studio as 0.3.0-main.5003117d, the <base>-main.<sha8> form scripts/publish-studio-pack.mjs writes. A bare 0.3.0 would read as a formal Studio release and make the next main pin compare equal to this one.

Review: 1/0/0 0/0/0; fixes 1. Opus controller review of the pin and a recheck of the fix; restored the -main. version suffix.

🤖 Generated with Claude Code