cmux-next: pin CCmuxAppFFI to cmux-app-ffi-d3d3f420 (base red after #33133)

Merged
TE
4d ago
+2-2

Base red fix. Cause: #33133 (iMessage connector data bridge, squash d3d3f420) changed cmux-layout-reducer-ffi (new imessage.rs, a Cargo dependency) and cmux-app-ffi/Cargo.lock but left the CCmuxAppFFI pin alone, so "Check the app FFI pin" in cmux-next checks has been red on feat-cmux-next since d3d3f420 (push run 41650904609; that check was the only red there). #33881 had moved the FFI inputs too.

app-ffi-release run 41650900719, published cmux-app-ffi-d3d3f420820ff448d4f0b85e75fedc39369a56e5. The bot pin PR #33923 then closed without the pin commit (its head was force-pushed to a base commit), so this PR pins that release by hand: URL and checksum 267fc1ede0e107fcc57be43e33cf1308b25803da1512ab32ea27486188f54742, which match the release's SHA256SUMS and SOURCE_SHA.

Verified: scripts/cmux-next/check-app-ffi-pin.sh --verify-release on this branch (based on feat-cmux-next ea7b41be) prints "sources match d3d3f420" and "release built from d3d3f420 with checksum 267fc1ed...".

Risk: one pin line, no source change.

🤖 Generated with Claude Code

Agent session: agent session


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


Summary by cubic

Fixes the red "Check the app FFI pin" check on feat-cmux-next by pinning CCmuxAppFFI to the cmux-app-ffi-d3d3f420 release.

#33133 changed cmux-layout-reducer-ffi and cmux-app-ffi's Cargo.lock without updating the pin. The new URL and checksum match the published release's SHA256SUMS; there are no source changes.