android: post real system-tray notifications when a run needs the operator

The app already had an in-app attention surface but nothing in the system
tray. This adds the app's own Android notifications for the two events that
need a person: a run waiting for a decision (highest importance) and a run
that failed. A successful, running or cancelled run raises nothing.

- RunAlerts.kt: the pure model. Maps the attention list's kinds to run
  alerts, coalesces several into one grouped summary, dedupes one
  notification per run+kind via AlertLedger (never repeated while the run
  stays failed or waiting), clears on resolution/dismissal/arrival, and
  decides the one-time permission prompt and tap destination. Unit-tested.
- RunNotifier.kt: the Android edge. Creates the single "Runs that need you"
  channel, posts/clears through NotificationManagerCompat, and reports
  notificationsAllowed() from POST_NOTIFICATIONS (API 33+) / the system
  notification switch. Posted from the app's own process.
- Manifest: POST_NOTIFICATIONS runtime permission; PipelinesApplication
  creates the channel before anything can post.
- SettingsRepository/AppViewModel: remembers that the permission was asked
  once (never nags), keeps notificationsAllowed fresh on resume, feeds the
  tray from the same attention flow, and clears a run's notification when
  the operator arrives at it.
- PipelinesApp/DecisionPrompt/RunDetailScreen: the one-time rationale before
  the system dialog, asked at a sensible moment (first run that needs the
  operator, or first open of the attention surface), degrading to the
  existing in-app surface on refusal; a waiting run's tap opens its decision
  sheet (pipelines://run/<id>?action=decide), a failed run's tap opens the
  run; reaching a run clears its notification.
- Attention.kt: drops the Finished kind so a successful run is never
  announced on any surface (the operator's rule), keeps the deep-link parser
  (now carrying an optional action) and still decodes an older state's
  looked-at-finished set.
- AttentionTest.kt / RunAlertsTest.kt: the mapping (waiting and failed
  only), the permission paths (granted, refused, not-yet-asked), coalescing
  and clearing, dedupe, and the tap destination.

Checks: `:app:assembleDebug` and `:app:testDebugUnitTest --rerun-tasks`
pass (578 tests, 0 failures). Reflected-where-it-belongs check: this is an
android/-only change and the packaged authoring skill references and the
packaged templates describe the server's ntfy notification authoring, not
the Android app's tray, so none of them needs updating. No README or other
shared documentation file was touched.
This commit is contained in:
2026-10-17 23:56:47 +01:00
parent 79ebba62c7
commit 54fecbb454
16 changed files with 1010 additions and 83 deletions
+8
View File
@@ -3,6 +3,14 @@
<uses-permission android:name="android.permission.INTERNET" />
<uses-permission android:name="android.permission.ACCESS_NETWORK_STATE" />
<!--
POST_NOTIFICATIONS is requested at runtime on Android 13+ (API 33), the
first time a run actually needs the operator or the attention surface is
opened, and asked at most once: a refusal degrades to the in-app Needs you
surface rather than nagging. Runs that need the operator post into the one
"Runs that need you" channel from the app's own process.
-->
<uses-permission android:name="android.permission.POST_NOTIFICATIONS" />
<application
android:allowBackup="true"