beta: debug report through the share sheet; transfers settle in seconds

[cryptskii]

Two fixes from tonight's hardware run.

1. The debug report goes out through the share sheet, with the app's log

The diagnostics screen's Download button built a blob: link and clicked it. An Android WebView ignores that, so the button did nothing and then showed "Diagnostics downloaded". The report it would have saved also held no log of the wallet itself, only the bridge's method names and payload sizes.

Share report replaces it. The native side writes the report and opens the Android share sheet with it (a FileProvider over the report's cache directory only). The report holds:

• the app version and install time, the device model, the Android version and the supported ABIs;
• what the app measured: session, identity and architecture as before, plus each contact's send state as Rust derives it (ready, or blocked and why) and its chain tip;
• the app's own log, from disk and from logcat's current buffer;
• the bridge log.

The app log on disk. logcat keeps only minutes of the app's log. App.onCreate starts a logcat child that writes this app's lines to files/diagnostics/app.log:

• Rust (DSM_RUST) and every other tag at Info;
• the WebView compositor's per-frame tags (View, GPUAUX, BufferQueueProducer) silenced;
• rotated at 1 MB across 8 files.

The report includes those files oldest first, then logcat's current buffer with the compositor's lines filtered out. It also says whether the on-disk log is running.

2. A two-phone transfer settles in seconds

On two A16s with both apps open, Alice could not send back to Carol for 48 s after Carol's transfer had arrived. Alice's own log shows her acceptance delivered at 14:37:14, her send refused at 14:37:37 (Waiting for the peer to finalize a transfer you received), and Carol's certificate applied at 14:38:02.

The causes:

• the poller ran every 5 s while settling, and every 60 s otherwise, even with the app on screen;
• wallet.send refused at once while the certificate was on its way.

The changes:

• Settling: while settlement work is outstanding, the poller runs every 2 s. That covers a sender awaiting the acceptance, a recipient owing its reply or awaiting the certificate, and a certificate not yet at quorum.
• App on screen: with nothing settling, the poller runs every 5 s instead of every 60 s.
• Sending: when the recipient's certificate for a transfer this device accepted is still outstanding, wallet.send syncs every 1.5 s for up to 20 s before the send-ready authority decides.

The finality barrier itself is unchanged: a certificate that never arrives still refuses the send.

Verification

• Settlement tests: the bilateral finality tests pass against local storage nodes: harness, r1 (role reversal), r2a (still refused, now after the wait) and r2b. cargo clippy -p dsm_sdk --all-targets -D warnings and cargo fmt are clean.
• Frontend: type-check and lint are clean, and the diagnostics suites pass (23 tests). The real-code guard passes.
• Kotlin: not compiled locally (no Android SDK here). This PR's Android build is its first compile.
• On a phone: nothing has run on a phone yet.
• Share path: no unit test, since testing it would need a new test double, which the real-code guard refuses.
• Code map: the Rust change will need its intent pins refreshed.

🤖 Generated with Claude Code

https://claude.ai/code/session_01Y4wDTToHmJfkYYJvMKXt3u

[cryptskii]

Code map fails on 03652f3d because this PR changes Rust in dsm_sdk (inbox_poller.rs, session_manager.rs, app_router_impl.rs). That moves the intent pins for the code the evidence tests reach, so their recorded digests no longer match.

This failure is caused by this PR. The fix is the usual repin:

1. Build the requirement map locally for this tree.
2. Run the evidence tests the moved pins name.
3. Repin through ci/intent_pins.py's rules, code-only.

That's in progress, and the repin will land as the next push on this branch.

---

Generated by Claude Code

[cryptskii]

Android Instrumented Tests (managed device) failed on cf7ec496 before any test ran. Gradle's managed-device setup could not install an SDK component on the runner:

InstallFailedException: Failed to install the following SDK components:
    emulator Android Emulator

This failure isn't caused by this PR: no test body ran, and nothing in this PR touches the emulator or the SDK setup. I'll re-run the failed job once when the rest of the run finishes; GitHub refuses a re-run while the run is still going. A second failure gets treated as real.

---

Generated by Claude Code