Repository navigation
feat(native): qualify MLX public progress cancellation and recovery - #279
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds a versioned native MLX lifecycle through the existing TrainingAPI/RunsAPI and host-owned stores. Start returns an owned run, numeric progress is bounded and authenticated, public cancellation distinguishes request from confirmed termination, and cold reconciliation recovers the original attempt without resubmission or stored-PID signaling. Legacy synchronous selections remain supported.
The config-first Mac workflow binds completion, cancellation or abrupt caller-loss scenarios into fresh root-signed admissions. Real M4 qualification at execution source e29c7da covers two three-update completions, confirmed cancellation and caller-loss/cold recovery per SFT/GRPO method. All four completions passed saved-adapter reload, finite parameter changes, public verification and 20 delivered artifact hash checks. Final head 9524bae changes documentation only; executable bytes are identical.
Validation: 186 final-source Darwin controls without skips, five real MLX numerical cases, targeted host/worker/public controls, and independent source reviews R4/R5. Final independent review R6 ACCEPTS exact 9524bae for bounded source/evidence/package/claim scope, with no actionable findings. It independently checked eight RSA admissions, 757 captured Git members, all eight one-claim outcomes/progress, 20 artifact hashes, four scalar adapter deltas/reload bindings and archive/installed-byte equivalence. Final wheel/sdist preserve qualified executable/runtime bytes; differences are README metadata only. The final isolated installed-base consumer passes without optional SDK/ML dependencies. All seven maintenance checks are CURRENT; Ruff, diff and skill synchronization pass.
Post-expiry gate is now complete. Actual Mac UTC 2026-10-27T22:39:33Z exceeded all eight original signed deadlines (22:39:31Z). New processes reverified all four completed runs and read all eight outcomes/logs using original authority. All manifests, outcomes, progress entries and timestamps matched; post-read SQLite snapshots retain exactly one process claim per attempt. No training was started, authority renewed or admission changed. These root-owned final read results supplement the earlier pre-expiry snapshot documented in the source report. Machine-readable proof is retained as post-expiry-independent-check-r3.json and post-expiry-claim-counts-r3.json under the private qualification evidence root.
Evidence and exact limits: docs/review/native-mlx-lifecycle-qualification.md. Ordinary qualification remains independently host-authenticated; no default authority or global capability promotion. Actual-ML acknowledgement loss was not separately injected; passing Darwin CPU controls are separate scope. Checkpoint continuation, arbitrary models/OS, quality, full desktop distribution, package publication and Syntunia deployment remain outside this change. Current CI is the remaining integration gate.