feat(channels): email thread follow on Aurinko with keyed participant proofs, dormant behind nyxbot:thread-follow (0.59.0) - #1763
Merged
Conversation
added 10 commits
October 4, 2026 07:39
…es with bounded history, dormant behind nyxbot:thread-follow (T1 A+B)
…th owner controls and UI, behind nyxbot:thread-follow (T1 C)
…ollow-c # Conflicts: # Cargo.lock # backend/Cargo.toml # cli/Cargo.toml # cli/src/wizard/bundle-meta/index.hash # frontend/package-lock.json # frontend/package.json
…t proofs, dormant behind nyxbot:thread-follow (T1 E) Merges origin/main (0.57.0). Aurinko threads become followable after an explicit To: address or a verified reply; guest history requires the requester's keyed HMAC participant proof. Legacy Aurinko inbound/callback shape is unchanged apart from the additive raw_data.email block, private DMs on other adapters keep a zero-read fast path, and existing bindings keep their pre-facts eligibility.
…ollow-email # Conflicts: # cli/src/wizard/bundle-meta/index.hash
…ollow-email # Conflicts: # cli/src/wizard/bundle-meta/index.hash
📊 Code coverage
Gate: line coverage must stay at or above the threshold. Ratchet plan (W21): Backend → 55%, CLI → 50%, Frontend → 30% by quarter end. |
…ollow-email # Conflicts: # cli/src/wizard/bundle-meta/index.hash
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
T1 PR E: email threads on Aurinko become followable, dormant behind
nyxbot:thread-follow(default off).To:of the connected mailbox (MailboxTo), or a reply verified against a retained NyxID message (VerifiedReply). Email partitions share one thread across participants.email-participantdomain) is among that message's participant fingerprints. No recipient addresses are persisted.private_chats = everyonefor guests). Conflicting legacy sender settings for one thread refuse with a reconcile message rather than picking one.send_bound_thread_reply.Backward compatibility
reply_to_platform_message_idstaysNone. The only addition is araw_data.emailblock, which is omitted when the audit key is unavailable, leaving the legacy message intact.private_thread(Telegram etc.) keep a zero-DB-read exit, decided from adapter capabilities before any flag or thread lookup.ThreadCapabilities.private_threadis omitted unless true, so/channel-platformsoutput changes only for Aurinko.ThreadAddressvariants fall back to the existingserde(other)default on older replicas.Validation
RUST_MIN_STACK=1572864);cargo +1.98.1 clippy --all-targets -D warnings; fmt.reply_tovalue, the eligibility fallback and the HMAC wording.