wtclaude 21b6ddc29b fix(notifications): resolve an item's relative url, and document the CI trigger ...

Two things the live rig found, and the README half of the trigger change.

Phase 7 specifies an inbox item's `url` is RELATIVE-ONLY and validates it as
such — right for a browser already on the site, a dead link on a phone. The
first cut here only opened `http(s)`-prefixed strings, so on the rig every link
in the inbox did nothing at all. `InboxViewModel.linkFor` now resolves against
the configured base with OkHttp's `HttpUrl.resolve`, which absolutises the path
and returns null for anything that would not end up http(s) — so a `javascript:`
or `intent:` url in a notification body opens nothing.

Co-Authored-By: Claude <noreply@anthropic.com>

2026-08-31 09:27:39 -05:00

..

licenses

feat(theme): draw the app in the shard's chosen type families (M12 phase 3)

2026-08-08 05:45:31 -05:00

src

fix(notifications): resolve an item's relative url, and document the CI trigger

2026-08-31 09:27:39 -05:00

build.gradle.kts

chore(sonar): wire JaCoCo coverage and clear actionable smells

2026-07-22 13:58:52 -05:00

proguard-rules.pro

feat(release): m6 release mechanics — signed APK, R8, version guard, icons

2026-07-20 03:35:06 -05:00