Terminal mail qualification, 0.2.0#

Dated 2026-10-05. This expansion builds on the immutable v0.1.1 bar release; its historical artifacts and compiler migration evidence are preserved. Terminal write acceptance uses fictional accounts. No production message, contact or invitation was changed.

Exact source and scope#

• Runtime source: 7568a2467b5a93142259bc50057a177c3acf7150.
• Application/package/manifest version: 0.2.0.
• Exact compiler: Zig 0.17.0, source 7647adab80dd088f4de3610fd245915a912eb6ad.
• libvaxis: 6fd944a27fb3d6f596e981076381a3131f2448b4; zigimg: c701c9f99779d7ddf594dcc6da8f858fd277d61f; uucode: ea62149739404a73c202b48a33bf6dd2af4bd9b0.
• Local qualification: native Linux x86_64, static musl, baseline CPU, Debug and assertion-enabled Safe. LLVM builds include the terminal client. The system compiler was left unchanged.

The bar keeps separate read-only accounts, 30-row snapshots and configured Chrome-profile routing. Terminal modes add complete messages/threads, explicit pagination, bounded private caching, a Vim-oriented libvaxis TUI, split composition, $EDITOR takeover, contacts, reversible mail changes, attachments and iTIP invitation replies. Calendar views and permanent deletion are unsupported. No tmux or second terminal engine is required.

Local terminal correctness#

Both modes passed 120 unit executions across the main, codec and provider suites (52 + 21 + 47), and all active standalone probes compiled. Final artifact identities:

Each final binary passed 42 CLI cases, 19 isolated PTY workflows and seven independent terminal HTTP tests. Fixture and terminal-cell-model helpers passed 12 and six checks; the existing UI model passed its 1,000 replacement cycles. The test corpus contains three fictional accounts with 96 messages each and deliberately overlapping opaque IDs.

Checks cover account/cache/cursor isolation, MIME and charset decoding, reply/reply-all identity, binary attachments, draft restart and uncertain-send deduplication, private/special-file refusal, atomic disk-quota overlap, contact concurrency, invitation identities, bounded framing/backpressure, editor failure/interruption and terminal restoration. The HTTP peer verified literal headers and the complete 128 KiB request, rejected redirects without forwarding, enforced internal ten-second stalled/trickled deadlines and rejected requests/responses over the 3 MiB transport bound.

Terminal memory and quiet CPU#

Both Safe workloads completed 100 warm-up cycles, 1,000 measured cycles and a 60-second quiet interval. Acceptance thresholds remained 4 MiB maximum warm RSS/PSS growth and less than 0.5% of one CPU core. Neither process grew after warm-up or used a CPU tick during its quiet minute; the TUI emitted no unsolicited render output.

The terminal allocator's 64 MiB ceiling and fixed backend/HTTP 16 MiB reservation are separate accounting bounds. Linux RSS/PSS measure the complete process including their touched pages, runtime and stacks. An external editor and terminal emulator have their own processes. These workload measurements are not absolute RSS guarantees. Memory accounting and reproduction contracts provide details.

Preserved failures and findings#

Failed development receipts remain private and unchanged. Fixes addressed incorrect directory descriptor permissions, external-editor foreground restoration/readback ownership, rewriting an unchanged body during metadata-only mutation, and an input queue copied by value onto a bounded runtime stack. These are application defects, not established compiler regressions.

Independent PTY tests also exposed incomplete UTF-8 input loss at the pinned libvaxis 1,024-byte read boundary. A project-owned bounded adapter now preserves trailing partial codepoints and owns queued text. The exact 2,349-byte body and eight forced fragmentation cases pass in both modes. Source inspection separately established the pre-existing linked-libc foreground-wrapper gap and the exact 0.17 removal of deprecated Allocator.dupeZ. Durable wiki findings distinguish dependency findings, source/API changes and application bugs.

Remaining release and live boundaries#

Local bar regression passed 13 integration and 13 transport cases in each mode, launch/callback/FD probes and an isolated synthetic Secret Service lifecycle. Safe backend memory passed 1,000 cycles with a 6,516 KiB peak RSS, zero warm growth and zero quiet CPU. The closed-background workload passed 1,001 refresh jobs with one active worker, bounded pending jobs and a 6,512 KiB peak RSS.

The unchanged offscreen Quickshell UI passed 1,000 open/close cycles after 200 warm-ups. Omagma's closed UI share was 16,004 KiB PSS over baseline, warm growth 296 KiB, with zero GUI/backend quiet CPU. All 1,204 views were destroyed. Its existing 20 MiB attributed-PSS and 2 MiB warm-growth gates were preserved; this is Qt lifecycle qualification, not a new compositor input claim.

The immutable v0.2.0 release is tagged at 550a0128fe9a5532c0b253585e1426f8f9c927bc. Release CI passed native Ubuntu Linux x86_64 and ARM unit/probe, bar, terminal, keyring and memory gates. Both architectures passed 42 CLI, 19 PTY and seven wire cases in each mode; their CLI/TUI soaks completed 1,000 cycles and quiet minutes with zero warm growth and zero measured quiet CPU. ARM terminal coverage is distinct from ARM Quickshell desktop coverage.

Actual downloaded assets passed complete checksums, normalized/privacy-audited archive contents, static ELF checks (no PT_INTERP or DT_NEEDED), extracted version/build-info and reservation accounting. The x86_64 binary is byte-identical to the local Safe artifact above; ARM SHA-256 is a61aecdbb5a085e6acc83b08334bea3a06cd95086693d65447aa21ca2f4d60b0. Running the downloaded x86_64 path passed another 42 CLI, 19 PTY and seven wire cases. The prior 1,000-cycle results apply to those exact executable bytes.

Initial private read-only live acceptance found incoming-address compatibility defects. One anonymous account passed two 20-message pages, a full message and a two-message thread. Another rejected its first page with InvalidAddress; the third rejected its second page with TooManyRecipients. A bounded targeted diagnostic confirmed static error identifiers without logging real mail or addresses. The failed receipts remain private, and no mutations or browser opening occurred. The outgoing parser's strict address grammar and 32-recipient ceiling were incorrectly shared with incoming reading. Local deployment was held for a new patch release; v0.2.0 assets remain unchanged.

Separate terminal Desktop OAuth credentials/capabilities preserve the bar's strict read-only grant. Live read paging, write permissions, Gmail/People behavior and recipient delivery need dedicated live acceptance. A user-provided test mailbox is required for initial sends, contact changes and invitation replies; synthetic success does not establish remote deduplication or delivery.