Squashes the working tree that had accumulated on cloud-agent. Two
strands of work, kept in one commit at the maintainer's request.
Crash and stability (this session):
- Subscribe to MetricKit so crash, hang, CPU, and disk-write diagnostics
are recorded on device. Keyboard-extension memory kills are the most
likely way a user loses the keyboard mid-sentence and iOS does not
classify them as crashes, so they never reach App Store Connect.
- Upload those reports to POST /v1/analytics/diagnostics from internal
builds only (local Debug and TestFlight), reusing the analytics
installation identifier and skipping entirely when analytics are off.
App Store builds keep everything on device.
- Shed the Chinese engine, English lexicon, and in-flight pipeline work
at the 40 MiB and 48 MiB budget thresholds instead of waiting for a
system memory warning that jetsam often preempts.
- Install audio taps with the input node's live format through one
shared adaptive resampler, so an audio-route change mid-recording no
longer raises an uncatchable format-mismatch exception. Covers the
dictation preview and the Mac recorder, which still used the pattern
the Flow capture path had already moved away from.
- Harden the librime bridge: never pass a nil string across a nonnull
boundary when a user dictionary holds malformed UTF-8, null-check the
engine API vector, and distrust a candidate count without its array.
- Guard the expanded candidate grid against a list that shrinks while
the collection view is still laying out against the previous count.
- Resolve localized text without the App Group so the screen shown when
that container is missing renders its message instead of crashing on
launch, which is the one situation it exists to handle.
- Gate CI on the App Group and Keychain wiring that the keyboard
extension hard-depends on, with a self-test proving the check fails.
Clipboard, reply, and semantics (pre-existing working tree):
- Unify the reply center, refresh keyboard AI features, and add native
event and reminder exporters.
- Expand clipboard semantic routing with authored corpora and a
product-blind holdout, plus the scripts that build and validate them.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Remove the test-mode unlimited personal-style corpus bypass and replace it with a real 1,250-character minimum gate. Production stays at 2,500. Training-corpus export and the diagnostics view now use a 5,000-character upper bound so the user's full private history never leaves the device in a single export.
- Add PolishStyleLearningCorpusBuilder.testBuildEffectiveCharacterCount (1,250) and trainingExtractionMaximumCharacterCount (5,000); trainingWindow(from:maximumCharacterCount:) accepts a custom cap.
- PolishStylesView: drop bypassesStyleLearningCharacterGate in favor of styleLearningMinimumCharacterCount, unify the ready/remaining text, remove the obsolete polishStyles.learn.testBuildReady key.
- PolishStyleCorpusExportStore: pass the 5,000 cap to trainingWindow and expose trainingExtractionMaximumCharacterCount in the export schema.
- FlowDiagnosticsSettingsView: show the export-sized (5,000-cap) corpus so the diagnostics match what the export ZIP actually contains.
- Tests: rewrite the export cap test for 5,000, add below-cap coverage, add trainingWindow(maximumCharacterCount:) unit coverage, and convert the old UI test into a regression test for the 1,250 test-build minimum.
- L10n: drop the testBuildReady string in en + zh-Hans, update diagnostics.corpus.ready to mention 5,000.
- CHANGELOG: bilingual entry under [Unreleased].
rockyandClaude Opus 5