[developing-today]

Refs developing-today-forks/openchamber#1466.

Why

Code's lock pinned openchamber at e1ad0521, whose recorded x86_64-linux node_modules fixed-output hash (sha256-WJn5…) does not reproduce on amd-6 — the failure filed as openchamber#1466, which aborted the (merged) #4880 cascade deploy at its build gate: everything else in the activation closure built green; only openchamber-node_modules-2.5.0 failed, identically across two full builds. Openchamber re-baked the hash in openchamber#1453 (commit 8bd0721ab). This PR moves code's pin to openchamber main f46050fc0, which contains the fix.

Lock diff

flake.lock only, the openchamber node alone: rev e1ad05211895… → f46050fc0d6d9…, narHash sha256-J/jSc+E+… → sha256-GBbIfUow…, lastModified updated. No other node moved. (Obtained with nix flake lock --update-input openchamber, after moving the laptop's stale fetcher cache aside — its first resolution landed on a mid-range rev.)

Openchamber range e1ad0521 → f46050fc0 (19 commits)

• nix/hashes.json: x86_64-linux → sha256-H2NGcbn/5V9dWLnMXEd0xLufNuYkpFV6obHOP7OScVo= (id(roc): F11.15 smaller example modules — wasm-opt -Os + strip, all 7 rebuilt ≤400 KB (#555) #1453) — the only packaging change.
• flake.nix: R2 substituter hostname rename (cache-host-swap, id(web): world records view shows a lone stale page when an input event restarts a paginated fetch — fresh pages are silently discarded #1458) — already fleet-wide.
• Openchamber's own flake.lock is unchanged across the range: its nested opencode pairing stays at fork 2d912e02, exactly what the cascade design relies on.
• nix/modules/** untouched: services.openchamber options, the generated start wrapper, and the package attr are unchanged.
• The rest is web/UI/CI only (scheduled-task run-limit settings, quota credential-read classification incl. id(web): collab reconnects re-send the original identity token — the AUTH_OK refresh never reaches the socket that needs it #1463, dead outside-file grant removal, pm-dispatch CI vendoring).

Verification (laptop amd-6, this branch)

• nixosConfigurations.amd user home configuration evaluates cleanly (activationPackage drv 428wik0560…); services.openchamber / services.opencode / services.mcpx .enable all evaluate true.
• The openchamber package as consumed through this flake builds: /nix/store/rmng4jvr…-openchamber-2.5.0 (openchamber --version → 2.5.0); its node_modules FOD output /nix/store/fy4h9xis…-openchamber-node_modules-2.5.0 is realised and valid — possible only with the re-baked H2NG hash in force.
• Dry-run census of the amd user activationPackage: 35 derivations to build / 123 paths to fetch; the closure's five openchamber derivations (node_modules FOD, package, openchamber-start, .service, .socket) are all present in their fixed forms. The aborted deploy had the rest of this closure green, and the single failing element was the FOD now proven fixed.

Merging this re-arms the #4880 cascade deploy on the laptop (build → switch → verify, rollback-armed).

Not merged — for review first.

---

^{Open in [code]smith · Need help on this PR? Tag @codesmith-bot with what you need.}

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

Run configuration

• Source mode: Auto
• Repository: Unavailable
• Branch: Unavailable
• File: No configuration file from this repository applied
• Commit: Unavailable
• Layers: defaults
• Review profile: CHILL
• Plan: Advanced
• Run ID: 3d8bdd1d-a03b-443c-85f7-9173a946b8d5

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• Trigger review

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

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

Share

• X
• Mastodon
• Reddit
• LinkedIn

CodeRabbit Verify

• Run CodeRabbit Verify to test the changes in this pull request.