Repository navigation
fix(native): keep history visible on upgraded devices; pin Air AssemblyAI behaviour and macOS arm64 recipe - #63
Conversation
The founder inbox picker defaulted to the Kameron view. A device upgrading from a build without the picker (the Air's 0.1.9-assemblyai.2, official 0.1.10) has no saved view, so it opened on Kameron, where every thread without an inbox record, which is all prior history, is hidden; the notification filter used the same view. Default to All instead. A view the user already picked is saved and keeps winning. Also pin the AssemblyAI behaviour the Air relies on with zero-network mock regressions: universal-3-5-pro header and raw key, config then audio parts, mono 16 kHz 16-bit WAV header and samples, language_code only when not auto, word_boost with preferred terms only, 401/402/403 rejected-key, 429 rate-limit, 5xx unavailable without leaking upstream text, and alias plus filler post-processing. These already pass on release/native-0.1.10. Task: CLO-866 Model: claude-opus-5-5 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
macOS desktop packaging needs clang, sips and iconutil, so the Apple Silicon Air candidate cannot be built on the Linux builders. Add a pinned recipe for that host plus a platform-neutral qualifier. build-mac-arm64-desktop.sh (bash 3.2 compatible) refuses anything but an Apple Silicon macOS 13+ host with Command Line Tools, the engines Node, a clean tracked tree and native/ equal to upstream v0.1.10. It derives SDKROOT and CXXFLAGS (or validates host-provided values) with a real clang++ probe, reuses the official v0.1.10 arm64 resource monitor (zip and binary pinned by SHA-256), passes the four public Connect keys from .env.example, sets no update feed, and builds unsigned through the supported build script. qualify-desktop-app.py then gates the app: version and bundle id, arm64 main executable and node-pty, codesign verification, no app-update.yml, AssemblyAI and founder-inbox markers, public relay config, no credential patterns, and records asar/server/web hashes. Upstream's official 0.1.10 Linux and macOS apps carry byte-identical server and web bundles, so the recipe also requires the Air build to reproduce the Linux reference build of 26e726e (server 966504d, bin.mjs b68a6c92, web 264d5422). Task: CLO-866 Model: claude-opus-5-5 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
RESULTRESULT (CLO-866, source-only, Air ARM64 lane). Linear isn't reachable from the builder, so this PR is the durable record. State: source tested; no Air artifact. The macOS arm64 app must be built on an Apple Silicon Mac with Source and CI
AssemblyAI parity with the Air's 0.1.9-assemblyai.2. The new assertions pass unchanged on
All mock fetch; no paid or live call. Founder picker: the default view was Kameron, which hides all unclassified (historical) threads on any upgraded device. It's now All, and saved views persist. The test fails on Linux reference build of
Upstream's official 0.1.10 Linux and macOS apps carry byte-identical server and web trees, so the Air build is gated on reproducing these three hashes. Pinned Air inputs:
Air host handoff (original Air owner only, after unlock and handback):
Omarchy note: the staged AppImage Unrelated, not fixed (identical on Unverified: a real Air build, GUI, microphone, live AssemblyAI, Connect and passkeys on the Air; browser tests. Merge path: review, then a SHA-guarded merge of PR #63 at |
RESULTRESULT (CLO-866): corrected Linux x64 desktop AppImage built from merged Source: Artifact:
Build:
Qualification:
Supersedes: the staged Not verified: GUI launch, microphone, live AssemblyAI and the Omarchy install. Those belong to the JEFFDESK host owner after jobs finish, normal unlock and handback. Keep the currently installed app and the |
CHECKPOINTCHECKPOINT (CLO-866): transport of the
|
Why
Jeff's Apple Silicon Air runs a custom 0.1.9-assemblyai.2 build. The next candidate for it is the native 0.1.10 line (
release/native-0.1.10,eed9ff77). Before handing that over I compared the Air's AssemblyAI behaviour and data path with this source.Changes
26e726e2fix(contracts):founderInboxViewnow defaults to All. A view the user already picked is saved and still wins.universal-3-5-promodel header and raw-keyauthorizationconfigthenaudio(dictation.wav,audio/wav)language_codeonly when the language isn'tautoword_boostcarrying preferred terms onlyrejected-key, 429 →rate-limit, 5xx →unavailable, with no upstream text leaking into errorsenandauto), with filler removal switchable offac699e86build(closura): an Air-only macOS arm64 recipe (scripts/closura/build-mac-arm64-desktop.sh) plus a platform-neutral qualifier (scripts/closura/qualify-desktop-app.py). macOS packaging needsclang,sipsandiconutil, so it can't run on the Linux builders.3d34c9ef…for the resource monitorf021339a…(an arm64 Mach-O; reused only whilenative/equals v0.1.10).env.exampleclang++probe, or the host's own values are validated.com.t3tools.t3code; arm64 executable andpty.node;codesign --verify; noapp-update.yml; AssemblyAI and inbox markers; public relay config; no credential patterns.966504d0…,bin.mjsb68a6c92…, web264d5422…).Verification (local, ASUS; no paid or provider calls)
eed9ff77expected 'kameron' to be 'all')eed9ff77vp run check:changedtypecheckvp run check:changedtests26e726e2(noble recipe)b4142c92…, every qualifier gate passes, glibc max 2.39, shipped web default iswithDecodingDefault("all")No Air artifact exists yet. It has to be built on the Air (or another Apple Silicon Mac) with the recipe.
Unrelated, not fixed here (identical on
eed9ff77)apps/server/src/provider/AgentContextBudget.test.tsfails: the agent context exceeds the committed budget after the inbox port. CI doesn't run it.INBOX_CAPABILITYexport. That makes the pre-commit hook fail on any commit to this branch. I ran format, lint, typecheck and tests explicitly and committed with the hook skipped.Air handoff (host owner only, after the usual unlock and handback)
On the Air: check out this commit, run
vp install, then:scripts/closura/build-mac-arm64-desktop.sh --work ~/.cache/t3-mac --output-dir <empty dir> --build-version 0.1.10.Use CLO-810's SDKROOT/CXXFLAGS if set; otherwise the probe picks them. Keep
manifest.json.Before cutover:
/Applications/T3 Code (Beta).appaside and confirm itsContents/Resources/app.asarsha256 isba78964291f322b67389ff939ad584d6c8a39fe4eb86d122ab52177948aba73c.~/.t3and~/Library/Application Support/t3code-v2(plusT3 Code (Alpha)if present) while T3 is stopped.0.1.10 adds database migrations 090–096, so this backup is the only way back to 0.1.9.
Install by replacing the app, then launch.
Accept:
Rollback: quit T3, restore the saved
.app,~/.t3and the userData folder.Task: CLO-866
🤖 Generated with Claude Code