feat(updates): show cumulative version-range changelogs

[veryCrunchy]

Summary

• publish cumulative, bounded user-facing change records in Android and desktop update manifests
• tag each change with the main-history source sequence where it first appeared
• show every change introduced after the installed build and through the selected target build
• recheck the selected update channel immediately before installation and stop if a newer target appeared or freshness cannot be confirmed
• continue accepting legacy manifests that contain no structured change list

This is propagative across intervening builds. An update from build 100 to build 105 includes changes first introduced in builds 101, 102, 103, 104, and 105; it is not limited to build 105's own release fragment.

Follow-up to #269.

Validation

On the dedicated build host at 6b7bc93730f74179d20ff99413069d4a55f8f9d0:

• 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. The desktop suite ran 2,472 tests with one unrelated skipped test.

[obiente-cloud]

Obiente preview

NC Native · ebf826b162db · 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.