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

..

debug/res/xml

fix(security): declare explicit network security config to forbid cleartext

2026-07-20 23:39:12 -05:00

main

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

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

test/java/com/runicgateway/app

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

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