release: 0.68.1

[noahgift]

Release bump for 0.68.1 (06x release schedule §4.2): bump-version.sh 0.68.1 across every workspace, and the CHANGELOG section below.

When this merges, rel-068-1-autopilot/autopilot.sh runs the rest of the train, fail-closed (APR-RELEASE-001 §4): T-1 deep run, pre-publish dogfood, tag + release, clean-room.yml dispatched on the tag with the run id recorded (T-3), all release assets checked with scripts/check_release_assets.sh, publish preflight, the crates.io cascade (T-4, automated per operator 2026-09-13), install.sh --version receipts on intel and gx10 plus the CUDA asset receipts on gx10 and yoga, and the epic and milestone close.

The crates.io release of the 0.68 line. v0.68.0 is a GitHub-only release (tag and binaries stand; install.sh verified on x86_64 and aarch64) — its clean-room on the tag passed A0–B1 for the first time ever on a tag and stopped at B2: lib tests in aprender-core and aprender-test-showcase named path-only dev-dependencies that cargo publish deletes (#3425). 0.68.1 carries that fix — the tests moved out of src/ to targets the published crates do not carry, all 72 lib-test binaries build in published form — plus the two infra gate repairs that made the chain provable (infra#650 tag ref materialized, infra#652 A1 [patch.crates-io] overlay at the tag). Everything else is 0.68.0: Qwen 3.5 on the CPU, the one-line installer, the release-train gates.

Fixed

• fix(publish): lib tests in aprender-core and aprender-test-showcase named path-only dev-deps that cargo publish deletes — clean-room B2 red on v0.68.0 (fix(publish): lib tests in aprender-core and aprender-test-showcase named path-only dev-deps that cargo publish deletes — clean-room B2 red on v0.68.0 #3425)

Changed

• refactor(parity): the refusal call site pushed run to B- — CB-200 back to the 601 baseline (refactor(parity): the refusal call site pushed run to B- — CB-200 back to the 601 baseline #3415)
• audit: 2026-09-17 07:00Z — T-2 pass 3, the 602nd site removed (refactor(parity): the refusal call site pushed run to B- — CB-200 back to the 601 baseline #3415), rulings applied, T-4 stops at the dry-run (audit: 2026-09-17 07:00Z — T-2 pass 3, the 602nd site removed (#3415), rulings applied, T-4 stops at the dry-run #3417)
• audit: 2026-09-17 08:25Z — T-2 GO, v0.68.0 tagged with 16 assets, clean-room stop on an infra clone defect fixed and re-dispatched (audit: 2026-09-17 08:25Z — T-2 GO, v0.68.0 tagged with 16 assets, clean-room stop on an infra clone defect fixed and re-dispatched #3419)
• audit: 2026-09-17 10:00Z — clean-room through B1 on v0.68.0, B2 fixed, v0.68.0 GitHub-only, 0.68.1 to crates.io (audit: 2026-09-17 10:00Z — clean-room through B1 on v0.68.0, B2 fixed, v0.68.0 GitHub-only, 0.68.1 to crates.io #3426)

🤖 Generated with Claude Code

no-close: #650 652 3415 3417 3419 3425 3426 — referenced by the 0.68.1 release notes; the bump PR closes nothing.

[github-actions]

§13.11 rung 1 — quorum shadow verdict

S13-SHADOW pr=3450 head=ef0549ef0d8bd2078cdb13f45568dd5922cb7505 verdict=REFUSE class=Q1 arm_rc=1

Shadow mode: this records a verdict and merges nothing. A refusal
to arm is not a block (§13 adds zero rows to §7) — the pull request is
exactly as green as it was.

[noahgift]

PMAT-3445 (#3445) — the defect is live on this train. Measured 2026-09-17 ~13:45Z:

• gh api repos/paiml/aprender/milestones/5 → open_issues=2: CPU: Qwen3.5 / Qwen3.8 hybrid GGUFs are refused entirely — no fallback exists #3091 (issue, P1, open) and this PR.
• The running autopilot (/mnt/nvme-raid0/agent-wt/rel-068-1-autopilot/autopilot.sh, pid 3021358, 3450 wait dryrun) has no milestone read in its tag block; the only read is close (line 239), after publish.

When this PR merges, v0.68.1 will be tagged with #3091 still open in its milestone. That is the 0.68.0 failure again. Before the tag, either close #3091 or carry it: gh issue edit 3091 --milestone 0.69.0, plus a slipped_from: 0.68.0 comment.

The gate (scripts/check_milestone_cut.sh <milestone>, exit 0 only when the milestone has 0 open items) is in progress on branch PMAT-3445-t0-milestone-gate. Once it lands, it goes at the top of the autopilot's if run_step tag block.