[github-actions]

Automated real merge of ml-explore/mlx-swift main (863ee9f, 4 commit(s) not yet in this fork) into main. Upstream changes: ml-explore/mlx-swift@35c10b4...863ee9f

Merge this PR with a merge commit ("Create a merge commit"), not squash or rebase. Squashing orphans the upstream commits and the fork commits that downstream repos pin (submodule SHAs).

Upstream commits

• 863ee9f Add Sendable closures and 3-parameter VJP support to MLXCustomFunction (#481) (Shubhransh Gupta)
• 12a704a Add shardedToAllPredicate (#503) (Ronald Mannak)
• 17f6470 Fix iOS 26.2 launch crash from Logger.isEnabled (#494) (Purav Manot)
• 26d685a compile and vmap can produce Sendable closures from Sendable inputs (#469) (David Koski)

Needs a human look

• Fork-sensitive paths changed by this merge:
  • Package.swift
• The merge deletes files that upstream deleted:
  • Source/cLogSupport/cLogSupport.c
  • Source/cLogSupport/include/cLogSupport.h
• Upstream also changed workflow files; the bot does not apply them (the default token cannot push workflow changes), apply by hand if wanted:
  • .github/workflows/release.yml

What was checked

• Git merged cleanly (no conflicts, no -X ours/theirs); the fork's workflows were restored unchanged.
• Size: 21 files changed, 1116 insertions(+), 476 deletions(-).
• Syntax: 14 changed Swift file(s) parsed with swiftc 6.2.
• Not run by the bot: a build, the tests, a Metal toolchain. CI on this PR must be green before merging.

Bot disclosure

Prepared by the upstream-sync GitHub Actions workflow. The workflow never approves, reviews or merges; no human has reviewed this merge yet.

• I have read this PR description in full and approve it as my own

[solderzzc]

Closing in favor of a real merge of upstream main through 43c90af, with CI, following #26. This bot PR is also stale: upstream has three commits after 863ee9f, and its release.yml still references the removed cLogSupport framework.