base red: revert the chats-mirror link into cmux-app-ffi (5a6a9c108b1, unpinned FFI)

Merged
LA
7d ago
+7-27

Summary

Base red on feat-cmux-next: the cmux-next checks job reports "red check: Check the app FFI pin" on every push since 5a6a9c108b1.

5a6a9c108b1 ("cmux-app-ffi: link the chat index mirror (CCmuxChatsMirrorFFI)") was a direct push, not a PR. It made cmux-chats-mirror a Cargo path dependency of cmux-app-ffi, so the crate became an app FFI input. No release was published for it and the pin did not move:

  • The app-ffi-release.yml push run for 5a6a9c108b1 (41149681296) was cancelled.
  • The dispatch at 942efe90d5f (41150186727) is still queued for a Blacksmith macOS runner, more than an hour later.

The standing order is to revert first. This PR is a clean git revert of 5a6a9c108b1. The cmux-chats-mirror crate stays in the cmux-tui workspace (aaa31184e32 and 123cfaa557f stay). These parts go:

  • the crate's link into the app static library
  • the header export in build-app-ffi.sh
  • the release smoke link and header compare
  • the cross-build header list
  • the license-list row
  • the pin-owner line

No Swift code uses CCmuxChatsMirrorFFI yet (git grep finds none in Packages/).

To re-land: put the link back, let app-ffi-release.yml publish it, then pin the new URL and checksum in the same push or in the bot's re-pin PR.

Takes back 5a6a9c108b1 (direct push, no PR number): its FFI change landed without a release and pin, so every PR inherits a red "Check the app FFI pin".

Testing

Check: scripts/cmux-next/check-app-ffi-pin.sh --verify-release (the step's command on a feat push).

Observed / Not run

Observed: I ran the checks above on a Linux VM and saw the results above. The fleet compile-check result is in a comment below.
Not run: cargo test -p cmux-app-ffi, and no local Rust build. The revert removes one pub use and one path dependency, back to the tree that c0331557f54's release built.

Changelog

none

Proof

CI, FFI wiring only; no UI.