feat(support): add in-app report conversations

[veryCrunchy]

Summary

• refresh retained private report capabilities while the signed-in app is open
• show a global privacy-safe banner when a report status changes or support sends a new message
• display private report status and the bounded conversation in Diagnostics settings
• let reporters reply in the app and explicitly mark updates as read
• persist only the acknowledged status and last-read maintainer message ID, not message bodies or capability URLs beyond the existing private receipt
• validate same-origin capabilities, response size, status values, timestamps, authors, message IDs, and message sizes before exposing server data

Depends on Obiente/support#4 for the capability conversation endpoints and maintainer question workflow.

Follow-up to #351.

Validation

On the dedicated build host at ad10d1d5f7cb697d341331d637874bf62217f2f2:

• bash tools/check-repository.sh
• bash tools/test-prerelease-update-contract.sh
• ./gradlew --no-daemon :ui:desktopTest :androidApp:testDebugUnitTest :androidApp:verifyReleaseLintGate --max-workers=1 -Pkotlin.incremental=false

All passed. Gradle reported BUILD SUCCESSFUL with 123 actionable tasks. Tests cover private status refresh, maintainer-message unread state, durable read acknowledgement across restart, capability-scoped reporter replies, and request paths.

[obiente-cloud]

Obiente preview

NC Native · 35b7bbe580f1 · Removed

View preview status

View in Obiente

_{Obiente updates this comment as the preview changes.}

[chatgpt-codex-connector]

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.
To continue using code reviews, add credits to your account and enable them for code reviews in your settings.