chore: bump to v0.1.40

[alexkroman]

Version bump for the v0.1.40 release. Bumped by the release-bump workflow
(run) — CFBundleShortVersionString
0.1.39 → 0.1.40 and CFBundleVersion 39 → 40, with Info.plist regenerated by xcodegen.

Merging this starts the release workflow: release.yml triggers on a push to main touching
project.yml, builds and notarizes the DMG, then parks on the release-publish environment for
the ship gate.

Shipping in v0.1.40

• d8491e2 — send recent dictations and the caret's text as conversation_context; key terms as word_boost
• 825d4f9 — remove per-PR dev builds; split debug/release bundle IDs
• 35c308c — raise the engine coverage gate to 88% and add a mutation harness
• b7513b0 — aggregate independent checks to report all failures at once
• e577f19 — docs: add an evals README, move the engine guide into the package
• 86b557e — document engine APIs, settings, update checking, and embedding constraints

🤖 Generated with Claude Code

[alexkroman]

Closed for now — holding v0.1.40 until the AirPods PR lands.

Nothing shipped: main is untouched at 35c308c, no v0.1.40 tag exists, and release never triggered (it fires only on a push to main touching project.yml). The version is not burned — release-bump.sh only refuses a version whose tag already exists on origin.

The branch release/v0.1.40 still carries the bump commit (68960a5, pure version metadata), so resuming is just: reopen this PR, update the branch from main, merge. Merging then ships AirPods in v0.1.40.

[alexkroman]

Reopening: the AirPods fix landed on main as 2b1a7f7 (#133), so the hold is over.

The bump commit (68960a5) is unchanged and still just the two version lines in project.yml + Info.plist. It's based on 35c308c rather than main's tip, which is fine here — main requires linear history but not an up-to-date branch (strict: false), and nothing merged since touches either file. The merge queue builds the candidate against main's tip anyway, so check verifies the bump with the AirPods fix before it lands.

Merging this starts release on its own (push to main touching project.yml). Publishing then parks on the release-publish gate for you to test the DMG and approve.