feat: support native read state and recent channel activity

[kalvinnchau]

Summary

• Add purpose-bound native read-state decoding, signing, publication, snapshot retrieval, and recent channel-activity queries.
• Share signed admission/cooldowns and receipt checks with the existing transport; retain packaged workflow and channel-write capabilities after rebasing.
• Isolate the native workflow quota test origin so its admission pause does not leak into later read-state tests.

Validation

• Rebased onto main e304e3f5 (feat: persist sidebar preferences in packaged desktop #440 sidebar preferences). Conflicts were additive: sidebar and read-state commands, IPC handlers and tests coexist. Read-state Rust code now uses the nostr 0.45 import paths from feat: persist sidebar preferences in packaged desktop #440 (Keys, NostrSecretKey, Event).
• Mandatory pre-push Lefthook group passed at c26d5bda: types and related unit tests, design system, Rust Clippy.
• cargo test --offline --locked -p buzz-foundation -- --test-threads=1: 164 passed, 4 ignored, plus 1 integration test. A parallel run hit the two known host_command timing flakes.
• vitest run src/features/relay/: 87 files / 1,445 tests passed. git diff --check origin/main..HEAD passed.

Review and readiness

• Three independent review lanes cleared the previous head ef653a95, including the feat: enable packaged channel writes, encrypted recipes, and direct messages #436 overlap. The feat: persist sidebar preferences in packaged desktop #440 conflict resolution on top of it has not been re-reviewed by those lanes.
• A human (Kalvin) tested the change in the app and approved it. An agent ran the browser journey; the native agent run was skipped by the human.
• The pre-existing stale-pending recovery risk is tracked in fix: recover stale pending read-state publication after relay age rejection #447: fix: recover stale pending read-state publication after relay age rejection #447 .

buzz-review-completed

[wesbillman]

Changes requested:

• P2 — Public contribution metadata: All six commits (84e74764 through c26d5bda) expose internal deployment/account identifiers in their author/committer contact fields; 84e74764 and e66690c0 also include them in co-author contacts. Use public-safe contribution addresses for those fields while preserving actual am/peon authorship. Valid Signed-off-by trailers are explicitly exempt; this finding does not request changing them.

No additional production-code defects found after transport/lifecycle tracing and independent native codec/IPC review. The pre-existing stale-pending recovery limitation is already tracked in #447, not a new finding here.

Star Lord automated source review via Wes’s account. Head c26d5bda5ce65069551c2deaf02d4b611318fb44; base e304e3f59aa8ae89a3982d9f144cc933ccaea5b7. No local tests, builds or app execution. The inspected hosted CI snapshot was still running; Windows validation was skipped. Reported human app testing was not independently reproduced.

[wesbillman]

The existing P2 contribution-metadata finding remains unchanged; valid Signed-off-by trailers remain exempt. No additional production-code defects found in this pass, including the independent native Rust/IPC review; the pre-existing stale-pending limitation stays tracked in #447.

Star Lord automated follow-up via Wes’s account; COMMENT only, not approval. Head c26d5bda5ce65069551c2deaf02d4b611318fb44, base e304e3f59aa8ae89a3982d9f144cc933ccaea5b7: full Vitest 5,447/5,447 passed, typecheck and diff checks passed on a clean worktree. Hosted required CI is green; Windows was skipped, and I did not independently exercise the packaged native workflow or rerun Rust tests locally.