diff --git a/.planning/phases/07-design-system-polish/07-13-PLAN.md b/.planning/phases/07-design-system-polish/07-13-PLAN.md
new file mode 100644
index 0000000..2bf727a
--- /dev/null
+++ b/.planning/phases/07-design-system-polish/07-13-PLAN.md
@@ -0,0 +1,3239 @@
+---
+phase: 07-design-system-polish
+plan: 13
+type: execute
+wave: 1
+gap_closure: true
+depends_on:
+  - 07-12
+files_modified:
+  - prowler-client/flutter/lib/src/l10n/strings.dart
+  - prowler-client/flutter/lib/src/widgets/horizon_sliver.dart
+  - prowler-client/flutter/lib/src/widgets/connect_dial.dart
+  - prowler-client/flutter/lib/src/widgets/error_banner.dart
+  - prowler-client/flutter/lib/src/state/connection_state.dart
+  - prowler-client/flutter/lib/src/state/error_state.dart
+  - prowler-client/flutter/lib/src/screens/home/home_screen.dart
+  - prowler-client/flutter/lib/src/screens/logs/logs_screen.dart
+  - prowler-client/flutter/lib/src/screens/servers/servers_screen.dart
+  - prowler-client/flutter/pigeons/prowler_platform.dart
+  - prowler-client/flutter/lib/src/generated/prowler_platform.g.dart
+  - prowler-client/flutter/android/app/src/main/kotlin/com/prowler/client/generated/ProwlerPlatform.g.kt
+  - prowler-client/flutter/android/app/src/main/kotlin/com/prowler/client/MainActivity.kt
+  - prowler-client/android/app/src/main/java/com/prowler/client/vpn/ProwlerVpnService.kt
+  - prowler-client/flutter/test/widget/connect_dial_test.dart
+  - prowler-client/flutter/test/widget/error_banner_test.dart
+  - prowler-client/flutter/test/widget/no_config_nudge_test.dart
+  - prowler-client/flutter/test/widget/a11y_semantics_test.dart
+  - .planning/debug/AP4-EXCEPTION-D-07-16-START-FAILED-DISCONNECTED-SUPPRESSION.md
+  - .planning/phases/07-design-system-polish/designer-delivery-5-redline-v3-ping/PING.md
+  - .planning/phases/07-design-system-polish/07-07-SUMMARY.md
+  - .planning/phases/07-design-system-polish/07-13-SUMMARY.md
+  - .planning/ROADMAP.md
+  - .planning/STATE.md
+autonomous: false
+requirements:
+  - REQ-14
+  - REQ-15
+
+user_setup:
+  - service: design-system-team
+    why: "B-1 horizon-sliver halo composition reset requires a spec amendment (redline v3) before implementation. Plan-author composes the ping; user sends + waits for designer response; tactical close (Wave 8a) can ship without B-1, full close (Wave 8b) blocks on amendment + implementation."
+    env_vars: []
+    dashboard_config:
+      - task: "Review .planning/phases/07-design-system-polish/designer-delivery-5-redline-v3-ping/PING.md, ship to design-system team, await redline v3 amendment, then re-dispatch plan to implement against amended geometry"
+        location: "Designer comm channel"
+
+must_haves:
+  truths:
+    - "Home screen renders WITHOUT the `Home` title (PROWLER eyebrow + dial as headline only)"
+    - "Splash hold on AVD cold-launch ≤ 1000ms wall-time from launcher tap to Home first-frame (target 800ms; ceiling 1000ms accommodates AVD measurement noise)"
+    - "strings.dart no longer carries `Strings.statusIdle` consumers on the Home dial-meta (`statusIdle` either removed entirely or its Home-screen call site removed); LAYER chip never renders `— · idle` em-dash placeholder pair; EXIT chip never renders bare em-dash; connected meta row suppresses empty `exitCode`/`latencyMs` (no literal `exit · ms`); EXIT chip on L1 reads `direct` and drops the ` ms` suffix when latency is null; `Strings.serversSection` reads `One server per layer.`"
+    - "Connected meta row never renders the literal text `exit  · ` (two spaces around the divider) or ends with bare ` ms` when latencyMs is null (B-2)"
+    - "On three consecutive `ProwlerNative.start()` failures (xray-core retry exhaustion), Dart receives ONE `error` Status (no immediate `idle`/`disconnected` clobber) AND a `ConnectError(code: connectFailed)` flows through `errorEventsProvider` AND `ErrorBanner` renders `Strings.errConnectFailedHeading` + `Strings.errConnectFailedBody` (B-3)"
+    - "Dart-side `errorLatchTransformer` in `connection_state.dart` (~20 LOC defense-in-depth — `INVESTIGATION-260516-blockers.md` Item 3 SCOPE REDUCER calls it the `~30 LOC of insurance`) latches the dial to `DialState.error` when observing `[connecting, error, idle]` without an intervening `connected` frame. The D-07-16 Kotlin lift means the trailing `idle` shouldn't fire — but if a future regression reintroduces the disconnected broadcast, the Dart latch keeps the dial in error and the test-case-B widget test trips. THIS is the regression gate for the AP-4 exception (B-3)."
+    - "Tapping the dial with a config where `validate(mode:)` returns `'L<N> config missing for <Mode> mode'` shows a SnackBar carrying `Strings.errNoConfigNudge` AND navigates to `/settings` via `context.go('/settings')` (B-4)"
+    - "Dial Semantics.label interpolates the dial's textual state (e.g. `Connect to VPN. Currently Tap to prowl.` / `Connect to VPN. Currently Connecting….`) — NOT the bare `_label(state)` value (A-1)"
+    - "Home info IconButton has tooltip + Semantics.label (A-2); Logs copy IconButton has Semantics.label (A-2)"
+    - "Per-field Reset hit-target on Servers screen ≥ 48dp logical (A-3 — Material 48dp minimum)"
+    - "AP-4 byte-freeze exception for `prowler-client/android/app/src/main/java/com/prowler/client/vpn/ProwlerVpnService.kt:256-303` (2-line edit per D-07-16) is documented at `.planning/debug/AP4-EXCEPTION-D-07-16-START-FAILED-DISCONNECTED-SUPPRESSION.md` AND cited in the relevant task's commit subject"
+    - "After ALL v0.7.0 items land + UX team unconditional sign-off on the v4.2 re-shoot bundle (full close), Phase 7 closes: ROADMAP 07-07 + 07-12 + 07-13 flip to [x]; STATE.md `total_plans: 40` (v2.0 in-scope: 4+16+7+13 — rev-2 WARNING W3 locked convention), `completed_plans` advances 36→40 (+1 W3 recount for the previously-excluded P6 plan + 3 closures for 07-07/07-12/07-13), `completed_phases` 6→7, `percent` 95→100"
+  artifacts:
+    - path: ".planning/debug/AP4-EXCEPTION-D-07-16-START-FAILED-DISCONNECTED-SUPPRESSION.md"
+      provides: "Formal AP-4 exception record for the D-07-16 2-line Kotlin lift (precedent: 5 prior AP4-EXCEPTION-*.md docs in same directory)"
+      contains: "D-07-16"
+      min_lines: 30
+    - path: ".planning/phases/07-design-system-polish/designer-delivery-5-redline-v3-ping/PING.md"
+      provides: "Copy-paste-ready markdown body the user ships to design-system team requesting redline v3 amendment for B-1 horizon-sliver halo composition reset"
+      contains: "HORIZON-SLIVER-REDLINE"
+      min_lines: 60
+    - path: "prowler-client/flutter/pigeons/prowler_platform.dart"
+      provides: "ConnectErrorCode.connectFailed enum value (D-07-17) — Kotlin emits it via ErrorEventListener when `ProwlerNative.start()` raises after exhausted xray retries; Dart maps it to errConnectFailed* strings"
+      contains: "connectFailed"
+    - path: "prowler-client/flutter/lib/src/state/connection_state.dart"
+      provides: "Dart-side `errorLatchTransformer` (~20 LOC defense-in-depth per rev-2 plan-checker BLOCKER B1 fix). Latches the dial to error when observing `[connecting, error, idle]` without an intervening `connected` frame; regression-gates the D-07-16 AP-4 Kotlin lift even if it reverts."
+      contains: "errorLatchTransformer"
+      min_lines: 80
+    - path: "prowler-client/flutter/test/widget/no_config_nudge_test.dart"
+      provides: "Widget test for B-4 — empty-config dial-tap surfaces SnackBar(errNoConfigNudge) + navigates to /settings via go_router"
+      min_lines: 40
+    - path: "prowler-client/flutter/test/widget/a11y_semantics_test.dart"
+      provides: "a11y semantics regression test — 4 testWidgets cases: A-1 dial Semantics.label state interpolation, A-2 Home info IconButton + Logs copy IconButton Semantics.label (rev-2 WARNING W2: locked tests via IconButton.tooltip → Tooltip → Semantics.label auto-forward), A-3 ProwlInput reset ≥48dp touch target"
+      min_lines: 80
+    - path: ".planning/phases/07-design-system-polish/07-07-SUMMARY.md"
+      provides: "07-07 (Designer asset integration) close record — written at Wave 8b after v4.1 re-shoot UX team unconditional sign-off"
+      min_lines: 20
+    - path: ".planning/phases/07-design-system-polish/07-13-SUMMARY.md"
+      provides: "This plan's close record (Wave 8b)"
+      min_lines: 40
+  key_links:
+    - from: "prowler-client/flutter/lib/src/widgets/connect_dial.dart"
+      to: "prowler-client/flutter/lib/src/l10n/strings.dart"
+      via: "Strings.errNoConfigNudge SnackBar text + Strings.dialIdle/dialConnecting/dialConnected/dialError state interpolation in Semantics.label"
+      pattern: "errNoConfigNudge|Currently \\$\\{?_label"
+    - from: "prowler-client/flutter/lib/src/widgets/connect_dial.dart"
+      to: "prowler-client/flutter/lib/app.dart (go_router)"
+      via: "context.go('/settings') after empty-config validation issue surfaces"
+      pattern: "context\\.go\\(['\"]/settings['\"]\\)"
+    - from: "prowler-client/flutter/pigeons/prowler_platform.dart"
+      to: "prowler-client/flutter/lib/src/widgets/error_banner.dart"
+      via: "Pigeon-regen of ConnectErrorCode.connectFailed feeds error_banner _templateFor switch case mapping to Strings.errConnectFailedHeading/Body"
+      pattern: "case pigeon\\.ConnectErrorCode\\.connectFailed"
+    - from: "prowler-client/android/app/src/main/java/com/prowler/client/vpn/ProwlerVpnService.kt"
+      to: "prowler-client/flutter/lib/src/state/connection_state.dart"
+      via: "Skipping the disconnected broadcast on start-failed prevents the error→idle clobber on the Pigeon onStatusChanged stream"
+      pattern: "start-failed"
+    - from: "prowler-client/flutter/lib/src/state/connection_state.dart"
+      to: "prowler-client/flutter/test/widget/connect_dial_test.dart"
+      via: "Dart-side errorLatchTransformer is asserted by widget-test case B (`[connecting, error, idle]` → dial latches error). If the D-07-16 Kotlin lift reverts, the test still passes because the Dart-side latch holds; this IS the regression gate."
+      pattern: "errorLatchTransformer|test case B"
+    - from: "prowler-client/flutter/lib/src/widgets/error_banner.dart"
+      to: "prowler-client/flutter/lib/src/l10n/strings.dart"
+      via: "connectFailed case returns (Strings.errConnectFailedHeading, Strings.errConnectFailedBody, ...) with btnRetry + btnSwitchLayer actions"
+      pattern: "errConnectFailedHeading"
+---
+
+<!-- rev-2: 2026-05-16 — plan-checker BLOCKERs B1+B2 + WARNINGs W1-W5 addressed. -->
+<!-- rev-3: 2026-05-16 — plan-checker rev-2 WARNINGs (STATE.md math reconciliation, ROADMAP list-item flip prose) + INFOs (latch test wires .transform, 02d config teardown) addressed. Ready for execute-phase dispatch. -->
+
+<objective>
+Close the v0.7.0 ship list — the UX team's CONDITIONAL sign-off at
+`.planning/phases/07-design-system-polish/designer-delivery-4-ux-team-review/UX-REVIEW.md`
+plus the B-4 gap surfaced by `INVESTIGATION-260516-blockers.md`. Eight items
+total: three firm blockers (B-1 halo composition, B-2 empty meta-row, B-3
+silent-fail wiring), four polish must-fixes (§1 drop Home title, §2 splash
+hold, §3 5 copy rewrites, §4a a11y trio), and one investigation-surfaced
+partial (B-4 no-config nudge).
+
+The locked decisions in `07-CONTEXT.md ## v0.7.0 Gap Closure` are NON-NEGOTIABLE:
+  * **D-07-15** — B-1 fix path = redline v3 amendment FIRST, then implementation
+    (spec-amend-before-deviate keeps the spec→impl chain clean). Wave 7 ships
+    the ping; full Phase-7 close (Wave 8b) blocks on amendment + impl.
+  * **D-07-16** — B-3 fix path = AP-4 byte-freeze EXCEPTION on
+    `ProwlerVpnService.kt:256-303` (Wave 3, 2-line Kotlin edit collapses B-3
+    from ~120 LOC Dart-side latch transformer to ~30 LOC). Precedent: 5 AP-4
+    exceptions already granted in Phase 6 per `06-LEARNINGS.md` lines 124-134.
+    Cited in commit subject + new `.planning/debug/AP4-EXCEPTION-D-07-16-*.md`
+    record. INVESTIGATION caveat: the addresses cited in UX-REVIEW are
+    `:281-303`; per file inspection the `stopLocked()` private function spans
+    256-303 — the actual edit lives in `stopLocked()` which is called from the
+    catch block at line 262 via `stopLocked("start-failed")`. The fix is to
+    suppress the trailing `statusSink.disconnected(reason)` call (line 301)
+    when `reason == "start-failed"` so the error frame at line 257 isn't
+    immediately clobbered.
+    **rev-2 BLOCKER B1 fix:** Wave 4 (Task 6) ALSO adds a ~20 LOC Dart-side
+    `errorLatchTransformer` in `lib/src/state/connection_state.dart` —
+    described in `INVESTIGATION-260516-blockers.md` Item 3 as the "~30 LOC of
+    insurance" SCOPE REDUCER caller. This is defense-in-depth: the Kotlin
+    lift alone suffices for the B-3 user-visible bug, but if a future
+    regression reintroduces the disconnected broadcast, the Dart-side latch
+    keeps the dial in error. The latch is REGRESSION-GATED by widget-test
+    case B: `[connecting, error, idle]` → dial latches `DialState.error`
+    (test passes even if Kotlin lift reverts, because Dart-side latch holds).
+  * **D-07-17** — B-3 ConnectError = add new `ConnectErrorCode.connectFailed`
+    enum value to `pigeons/prowler_platform.dart` (regenerates both .g.dart
+    and .g.kt; `pigeons/` is allowed under AP-4 because it's not Phase-5
+    routing/dispatch source). Kotlin `ErrorEventListener` synthesises and
+    pushes the `ConnectError(code: connectFailed)` on `start-failed` so the
+    Dart `errorEventsProvider` surfaces it via the existing Pigeon stream.
+  * **D-07-18** — B-4 no-config signal shape = `ScaffoldMessenger.showSnackBar`
+    with `Strings.errNoConfigNudge` + `context.go('/settings')`.
+
+Wave structure (8 waves, with B-1 async-blocker split into 7→8a→8b):
+  * **Wave 1** (3 parallel trivial tasks): §1 drop Home title, §2 splash hold
+    cut, §3 5 copy rewrites
+  * **Wave 2** (B-2): empty-value suppression in Home dial-meta + quick-row
+  * **Wave 3** (B-3 platform + AP-4 doc): D-07-16 2-line Kotlin lift on
+    `ProwlerVpnService.kt` + D-07-17 Pigeon enum add + regen + AP-4-EXCEPTION
+    doc — sequenced INSIDE one task so commit-atomicity matches the lift
+  * **Wave 4** (B-3 Dart): error_banner._templateFor maps connectFailed →
+    errConnectFailed*; widget test asserts the connecting→error sequence
+    surfaces ErrorBanner (regression-gates the clobber)
+  * **Wave 5** (B-4): no-config SnackBar + auto-nav to /settings; widget test
+  * **Wave 6** (§4a a11y): A-1 dial Semantics state interpolation; A-2
+    info/copy IconButton tooltip+Semantics; A-3 Servers reset-button 48dp
+    touch-target audit + bump
+  * **Wave 7** (B-1 async-blocker handoff): PING.md composition; user-handoff
+    checkpoint (autonomous:false)
+  * **Wave 8a** (tactical close): re-shoot v4.1 bundle covering only screens
+    affected by Waves 1-6 (02-home, 02e-home-dial-connected, 02d-home-dial-error
+    triggered via B-3, 04-/04b-/04c-servers); UX team confirms 7-of-8 blockers
+    resolved
+  * **Wave 8b** (full close, post-B-1): after design redline v3 amendment
+    lands AND B-1 implemented in a follow-up plan AND v4.2 re-shoot UX-team
+    unconditional sign-off — write 07-07-SUMMARY.md + 07-13-SUMMARY.md, flip
+    ROADMAP 07-07/07-12/07-13 to [x], STATE.md progress 36→40 (+1 W3 recount + 3 closures) / percent 95→100 at full close. Phase 7 closes.
+
+Total ~190 LOC across 11 source + 4 test files + 2 doc artifacts + 1
+AP-4-exception record + the 4 close-time meta-files. Tactical close (Wave 8a)
+unblocks v0.7.0 ship of 7 items; full close (Wave 8b) caps Phase 7 after the
+B-1 round-trip.
+
+Purpose: close UX team's conditional sign-off on v0.7.0; close Phase 7; unblock
+Phase 8 (Windows) which UX team explicitly cleared to start as soon as B-1/B-2/B-3
+land per UX-REVIEW.md §7.
+
+Output: 8 items resolved, ~190 LOC merged, Phase 7 closed via Wave 8b, ROADMAP
++ STATE updated, AP-4 exception formally recorded.
+</objective>
+
+<execution_context>
+@$HOME/.claude/get-shit-done/workflows/execute-plan.md
+@$HOME/.claude/get-shit-done/templates/summary.md
+</execution_context>
+
+<context>
+@.planning/PROJECT.md
+@.planning/ROADMAP.md
+@.planning/STATE.md
+@.planning/phases/07-design-system-polish/07-CONTEXT.md
+@.planning/phases/07-design-system-polish/designer-delivery-4-ux-team-review/UX-REVIEW.md
+@.planning/phases/07-design-system-polish/INVESTIGATION-260516-blockers.md
+@.planning/phases/06-flutter-ui-settings/06-LEARNINGS.md
+@.planning/debug/AP4-EXCEPTION-BUG-B-FIX.md
+@prowler-client/flutter/lib/src/l10n/strings.dart
+@prowler-client/flutter/lib/src/state/connection_state.dart
+@prowler-client/flutter/lib/src/state/connection_actions.dart
+@prowler-client/flutter/lib/src/state/error_state.dart
+@prowler-client/flutter/lib/src/widgets/connect_dial.dart
+@prowler-client/flutter/lib/src/widgets/error_banner.dart
+@prowler-client/flutter/lib/src/widgets/horizon_sliver.dart
+@prowler-client/flutter/lib/src/screens/home/home_screen.dart
+@prowler-client/flutter/lib/src/screens/logs/logs_screen.dart
+@prowler-client/flutter/lib/src/screens/servers/servers_screen.dart
+@prowler-client/flutter/pigeons/prowler_platform.dart
+@prowler-client/android/app/src/main/java/com/prowler/client/vpn/ProwlerVpnService.kt
+@prowler-client/flutter/android/app/src/main/kotlin/com/prowler/client/MainActivity.kt
+@prowler-client/flutter/lib/app.dart
+@prowler-client/flutter/lib/src/services/prowler_config_validation.dart
+@prowler-client/flutter/test/widget/connect_dial_test.dart
+@prowler-client/flutter/test/widget/error_banner_test.dart
+
+<interfaces>
+<!-- Extracted from codebase. Executor uses these directly — no exploration needed. -->
+
+From `prowler-client/flutter/lib/src/l10n/strings.dart` (current strings touched
+by §3 + B-4):
+```dart
+// Existing — touched by §3:
+static const String statusIdle = 'idle';                  // §3 row 1: remove from Home dial-meta consumer
+static const String quickBypassExitDash = '—';            // §3 rows 2-3: stop using on idle Home quick-row
+static const String serversSection = 'Endpoints. One per layer.';  // §3 row 5: rewrite to 'One server per layer.'
+
+// Existing — B-3 surfaces these via the new ConnectErrorCode.connectFailed mapping:
+static const String errConnectFailedHeading = 'Connection failed.';
+static const String errConnectFailedBody =
+    'We tried 3 times. Switch layer or check your network.';
+
+// NEW string to add (B-4 per D-07-18):
+// static const String errNoConfigNudge = 'Paste a vless:// config to start.';
+```
+
+From `prowler-client/flutter/lib/src/state/connection_actions.dart` lines 30-48
+(the call site whose return is currently discarded in connect_dial.dart):
+```dart
+Future<List<String>> connect(pigeon.Mode mode) async {
+  final model.ProwlerConfig cfg =
+      await ref.read(configRepositoryProvider.future);
+  final List<String> issues = cfg.validate(mode: mode);
+  if (issues.isNotEmpty) {
+    return issues;          // ← returned but discarded at connect_dial.dart:186-191
+  }
+  final pigeon.ProwlerConfig pigeonCfg = _toPigeonConfig(cfg);
+  try {
+    await pigeon.ProwlerHostApi().connect(mode, pigeonCfg);
+    return const <String>[];
+  } on PlatformException catch (e) {
+    return <String>['${e.code}: ${e.message ?? "(no message)"}'];
+  }
+}
+```
+
+From `prowler-client/flutter/lib/src/services/prowler_config_validation.dart`
+lines 26-49 (validation reasons — used to discriminate "config missing" vs
+"config malformed" per INVESTIGATION-260516-blockers.md Item 1):
+```dart
+// Returns 'L1 config missing for Direct mode' / 'L2 config missing for Bypass mode'
+// / 'L3 config missing for Relay mode' when the target mode has no Lx slot —
+// this is the "no-config" branch B-4 must catch.
+// Other returned strings ('server address is empty', '... must be bare host',
+// 'port out of range', '... UUID is not v4 shape') are malformed-config cases
+// that already get surfaced by the existing connect-then-Pigeon-error path.
+```
+
+From `prowler-client/flutter/lib/src/widgets/connect_dial.dart` lines 185-191
+(the B-4 fix site — currently throws away the validation issues):
+```dart
+} else {
+  // Idle/error → connect using the user's most recent layer
+  // choice (defaults to Mode.direct on first launch).
+  final pigeon.Mode target = ref.read(lastSelectedModeProvider);
+  await ref
+      .read(connectionActionsProvider.notifier)
+      .connect(target);
+  // ← B-4 fix lands here: capture the returned List<String>, branch on
+  //   `.contains('config missing for')`, fire SnackBar + go('/settings').
+}
+```
+
+From `prowler-client/flutter/lib/src/widgets/connect_dial.dart` lines 172-175
+(the A-1 Semantics fix site — current label is `_label(state)`, i.e. just the
+state string, not the full interpolated sentence):
+```dart
+return Semantics(
+  label: _label(state),     // ← A-1 fix: change to "Connect to VPN. Currently ${_label(state)}."
+  button: true,
+  child: GestureDetector(
+```
+
+From `prowler-client/android/app/src/main/java/com/prowler/client/vpn/ProwlerVpnService.kt`
+lines 256-303 (the D-07-16 AP-4-exception edit site). The relevant flow:
+  * Line 256-264: catch (t: Throwable) emits `statusSink.error(...)` THEN
+    calls `stopLocked("start-failed")` (line 262) and rethrows.
+  * Line 281-303: `stopLocked(reason)` — final lines (300-302):
+    ```kotlin
+    currentMode = MODE_NONE
+    if (hadSession) {
+        dependencies.statusSink.disconnected(reason)
+    }
+    ```
+  * D-07-16 LIFT (2-line edit): change line 301 from
+    `if (hadSession) {` to `if (hadSession && reason != "start-failed") {`
+    OR equivalently add a `reason != "start-failed"` clause. The condition
+    skips the `disconnected("start-failed")` broadcast that immediately
+    clobbers the error frame.
+  * After this lift, Dart's `connection_state.dart` re-emits ONLY the `error`
+    Status (no trailing idle), so the dial latches `DialState.error`
+    naturally.
+
+From `prowler-client/flutter/android/app/src/main/kotlin/com/prowler/client/ErrorEventListener.kt`
+(the Kotlin synthesis path for B-3 — read line 1 to confirm shape; if it
+exposes a `pushError(ConnectError)` or equivalent, use it from
+ProwlerHostApiImpl's connect-catch to inject the new connectFailed code. If
+the listener is pure-passive over an EventChannel sink, add a sibling
+synthesiser following the same Pigeon `@EventChannelApi onError()` shape.
+Executor inspects + reports the actual shape; the task body has fallback
+guidance.
+
+From `prowler-client/flutter/lib/src/widgets/error_banner.dart` lines 91-125
+(the exhaustive `_templateFor` switch that needs the new connectFailed case
+AFTER pigeon regen lands the enum value — see Wave 3/4 sequencing):
+```dart
+(String, String, List<Widget>) _templateFor(
+  BuildContext context, WidgetRef ref, pigeon.ConnectErrorCode code,
+) {
+  switch (code) {
+    case pigeon.ConnectErrorCode.networkUnavailable: …
+    case pigeon.ConnectErrorCode.serverUnreachable: …
+    case pigeon.ConnectErrorCode.coreCrashed: …
+    case pigeon.ConnectErrorCode.consentDenied: …
+    case pigeon.ConnectErrorCode.switchFailed: …
+    // ← Wave 4 adds:
+    // case pigeon.ConnectErrorCode.connectFailed:
+    //   return (Strings.errConnectFailedHeading,
+    //           Strings.errConnectFailedBody,
+    //           <Widget>[ _btn(Strings.btnRetry, () => _retry(ref)),
+    //                     _btn(Strings.btnSwitchLayer, () => context.go('/layers')) ]);
+  }
+}
+```
+
+From `prowler-client/flutter/pigeons/prowler_platform.dart` lines 29-35
+(the enum that Wave 3 extends — Pigeon 26.3.2 canonical Dart enum syntax):
+```dart
+enum ConnectErrorCode {
+  networkUnavailable,
+  serverUnreachable,
+  coreCrashed,
+  consentDenied,
+  switchFailed,
+  // ← Wave 3 adds: `connectFailed,` after switchFailed
+}
+```
+Regen command (per 07-12 precedent + Phase 6 06-02 SUMMARY):
+```bash
+cd prowler-client/flutter && \
+  dart run pigeon --input pigeons/prowler_platform.dart
+```
+This rewrites:
+  - `lib/src/generated/prowler_platform.g.dart`
+  - `android/app/src/main/kotlin/com/prowler/client/generated/ProwlerPlatform.g.kt`
+DO NOT hand-edit those files — they appear in `files_modified:` only because
+the regen step rewrites them.
+
+From `prowler-client/flutter/lib/src/screens/home/home_screen.dart` lines
+86-103 (the §1 fix site — the `Home` title literal lives on line 88 in the
+`TopBar(...)` invocation):
+```dart
+TopBar(
+  eyebrow: 'PROWLER',
+  title: 'Home',                  // ← §1: change to '' (empty) or remove the param if TopBar accepts nullable
+  right: IconButton(
+    icon: const Icon(LucideIcons.info, size: 20, color: ProwlerTokens.fog),
+    onPressed: () => showAboutProwlerSheet(context),  // ← A-2: add Semantics.label / tooltip
+  ),
+),
+```
+Investigate `TopBar`'s `title` param signature (likely `String title` not
+`String? title`); if non-nullable, pass empty string `''` and the TopBar
+should render no title row (verify the TopBar widget collapses on empty
+string — if it renders an empty band, also tweak TopBar to suppress the slot
+when empty; treat as a small TopBar refactor in the same task).
+
+From `prowler-client/flutter/lib/src/screens/home/home_screen.dart` lines
+129-194 (B-2 fix sites — the _buildDialMeta + _buildQuickRow methods):
+
+  * Line 134-160 (connected branch): currently always renders
+    `'exit '` + code + ` · ` + `'$ms ms'` — when code is empty AND ms is
+    empty, the user sees literally `exit  · ` and ` ms`. B-2 fix: branch
+    inside the connected case on `code.isNotEmpty && status.exitCode != null`
+    + `status.latencyMs != null` and suppress the empty parts.
+  * Line 196-213 (_buildQuickRow): currently renders layerValue
+    `'— · idle'` when `activeMode == null` (idle state) and exitValue from
+    `quickBypassExitDash` (the em-dash). §3 + B-2 fix: when state == idle,
+    show `'not connected'` instead of `'— · idle'`; when state == idle, the
+    EXIT chip shows nothing (hide) or `'not connected'`; when state ==
+    connected with `activeMode == Mode.direct` AND `exitCountry == null`,
+    show `'direct'` as the EXIT value (NOT `'— · ms'`).
+
+From `prowler-client/flutter/lib/src/screens/logs/logs_screen.dart` lines
+97-109 (A-2 fix site — copy IconButton):
+```dart
+right: asyncBuf.maybeWhen(
+  data: (List<pigeon.LogLine> lines) => IconButton(
+    icon: const Icon(LucideIcons.copy, size: 20, color: ProwlerTokens.fog),
+    onPressed: lines.isEmpty ? null : () => _copyToClipboard(lines),
+    tooltip: 'Copy logs to clipboard',     // ← tooltip already present, but
+                                            //   need an explicit
+                                            //   Semantics(label:) wrap OR
+                                            //   IconButton's tooltip already
+                                            //   feeds Semantics by default —
+                                            //   confirm with TalkBack/Semantics
+                                            //   debugger first
+  ),
+  orElse: () => const SizedBox.shrink(),
+),
+```
+
+From `prowler-client/flutter/lib/src/screens/servers/servers_screen.dart`
+(the A-3 fix site — per-field Reset icons live inside `ProwlInput`'s
+`onResetPressed` slot. The reset icon button widget lives in
+`prowler-client/flutter/lib/src/widgets/prowl_input.dart`; executor reads
+that file in Wave 6 Task 3, confirms the existing icon button's
+hit-area dimensions, and either:
+  (a) wraps the icon in an `IconButton` with `iconSize: 20, padding:
+      EdgeInsets.all(14)` so total touch-target = 20 + 2*14 = 48dp, OR
+  (b) wraps in `SizedBox(width: 48, height: 48, child: …)` if it's a bare
+      InkResponse — pick whichever matches the existing widget shape.
+NOTE: UX team's A-3 is scoped to Servers; the same Reset icon may appear on
+other screens (Settings) — fix at the ProwlInput widget level so all consumers
+inherit the touch-target compliance.
+
+From `prowler-client/flutter/android/app/src/main/kotlin/com/prowler/client/MainActivity.kt`
+(the §2 fix site — splash hold). Current MainActivity does NOT call
+`installSplashScreen()` (the Android 12+ SplashScreen API entry point); it
+extends `FlutterFragmentActivity` and the Android-12 splash hold is
+controlled by `windowSplashScreenAnimationDuration` (defaults to 1000ms,
+configured in `android/app/src/main/res/values-v31/styles.xml` if set; if
+absent, Android picks the duration based on cold-start latency, typically
+~1.6s on AVD per UX-REVIEW frame_02 measurement).
+
+§2 fix options (investigate in Wave 1):
+  (a) **Declarative (preferred):** add
+      `<item name="android:windowSplashScreenAnimationDuration">800</item>`
+      to `LaunchTheme` in BOTH `values-v31/styles.xml` AND
+      `values-night-v31/styles.xml`. Cleanest fix; no MainActivity edit.
+      Note Android caps animation-duration at 1000ms (anything higher is
+      clamped); 800ms is in-range.
+  (b) **Programmatic:** call `installSplashScreen().setKeepOnScreenCondition { false }`
+      in MainActivity.onCreate BEFORE super.onCreate (per
+      androidx.core.splashscreen 1.0+ contract); requires adding the
+      `androidx.core:core-splashscreen` Gradle dep.
+Pick (a) — pure resource edit, no Gradle/Kotlin churn, and the
+declarative duration is exactly the UX team's specified value.
+
+NOTE on splash hold measurement: the UX team's "~1.6s" is the wall-clock
+between launcher-tap and Home first-frame. The Android-12 splash window
+itself has TWO durations:
+  (i) `windowSplashScreenAnimationDuration` (icon fade-in, declarative, 0-1000ms)
+  (ii) the post-engine-init hand-off (Flutter's first-frame draw triggers
+       splash hide via `FlutterNativeSplash.preserve()`/`.remove()` if used,
+       OR the system removes splash on Activity-ready).
+
+Project does NOT use `FlutterNativeSplash.preserve()`/`.remove()` in main.dart
+(grepped — only the codegen `dart run flutter_native_splash:create` step
+appears, which configures the Android-12 splash declaratively). So splash
+auto-hides on first-frame; cutting (i) from 1000→800ms reclaims ~200ms +
+relies on the engine cold-start to do the rest. Validate empirically in
+Wave 8a re-shoot.
+
+From `prowler-client/flutter/test/widget/connect_dial_test.dart` lines 21-30
+(test-double pattern for ConnectionStatus — Wave 4 B-3 widget test reuses
+this pattern):
+```dart
+class _FakeConnStatus extends ConnectionStatus {
+  _FakeConnStatus(this._fakeStatus);
+  final pigeon.Status _fakeStatus;
+  @override
+  Stream<pigeon.Status> build() => Stream<pigeon.Status>.value(_fakeStatus);
+}
+```
+For B-3 test (multi-frame stream): change `Stream.value(...)` to
+`Stream.fromIterable([connecting, error])` and add a `pumpAndSettle()` to
+ensure both frames flush.
+
+From `prowler-client/flutter/test/widget/error_banner_test.dart` lines 31-40
+(test-double pattern for ErrorEvents — reuse for Wave 4 B-3 widget test):
+```dart
+class _FakeErrEvents extends ErrorEvents {
+  _FakeErrEvents(this._fake);
+  final pigeon.ConnectError _fake;
+  @override
+  Stream<pigeon.ConnectError> build() =>
+      Stream<pigeon.ConnectError>.value(_fake);
+}
+```
+
+From `.planning/debug/AP4-EXCEPTION-BUG-B-FIX.md` (template for the new
+D-07-16 exception doc — read first to mirror format/structure exactly).
+
+</interfaces>
+
+</context>
+
+<tasks>
+
+<task type="auto">
+  <name>Task 1 (Wave 1a — §1 drop Home title): Remove `Home` title from HomeScreen TopBar — keep PROWLER eyebrow + info icon; verify TopBar collapses cleanly when title is empty</name>
+  <files>
+    prowler-client/flutter/lib/src/screens/home/home_screen.dart,
+    prowler-client/flutter/lib/src/widgets/top_bar.dart
+  </files>
+  <action>
+**Step 1 — Inspect TopBar's `title` param contract.** Read
+`prowler-client/flutter/lib/src/widgets/top_bar.dart` and confirm:
+  (a) Whether `title` is `String` (non-nullable, requires `''` or sentinel)
+      or `String?` (nullable, requires `null` and conditional rendering).
+  (b) Whether TopBar currently renders an empty band / placeholder when title
+      is empty string, or already collapses cleanly.
+
+**Step 2 — Edit HomeScreen TopBar invocation** at
+`prowler-client/flutter/lib/src/screens/home/home_screen.dart` line 86-89.
+Current:
+```dart
+TopBar(
+  eyebrow: 'PROWLER',
+  title: 'Home',
+  right: IconButton(...),
+),
+```
+
+If TopBar's `title` is `String?`: change to `title: null`.
+If TopBar's `title` is `String`: change to `title: ''` AND modify TopBar
+widget to suppress the title slot when the string is empty (use a small
+`if (title.isNotEmpty)` guard around the title Text widget — pattern
+matches the existing `if (right != null)` slot pattern if present).
+
+This implements UX-REVIEW §1 — "Kill the `Home` title. Keep `Connect` as the
+tab label." The tab label `Strings.navConnect` is in `bottom_nav.dart`'s
+NavigationBar and is NOT touched by this task (it's already correct).
+
+Per the alternative spec from UX-REVIEW §1 final paragraph: "If you want to
+keep a title for nav-stack reasons, make it `Tap to prowl` and remove the
+duplicate caption under the dial." DO NOT take this alternative path — the
+plan-author confirms with UX-REVIEW that the dial caption is the load-bearing
+copy (it's the dial's affordance), so dropping Home wins over duplicating
+Tap-to-prowl. The dial caption stays.
+
+Per CLAUDE.md "extension over duplication": modify the existing TopBar
+widget's title slot once rather than creating a TopBarNoTitle variant. Other
+screens that pass `title: 'Layers'` etc. continue rendering their title
+normally — only the empty/null case is added.
+
+**No new strings** — `Strings.navConnect` already exists (line 75) and is
+unchanged; the Home screen TopBar simply drops its title.
+
+**REQ-14 lexicon check:** no new user-visible strings, no forbidden vocab
+introduced.
+
+**Per D-07-14 light-touch:** trivial Flutter-lib-only edit; no AP-4
+considerations.
+  </action>
+  <verify>
+    <automated>
+      bash -c '
+      set -euo pipefail
+      cd /home/parf/projects/work/prowler/prowler-client/flutter
+      # Gate 1: Home screen TopBar no longer passes title: "Home".
+      ! grep -nE "title:\s*[\x27\x22]Home[\x27\x22]" lib/src/screens/home/home_screen.dart
+      # Gate 2: HomeScreen build() still contains PROWLER eyebrow + info icon.
+      grep -q "eyebrow:\s*[\x27\x22]PROWLER[\x27\x22]" lib/src/screens/home/home_screen.dart
+      grep -q "LucideIcons.info" lib/src/screens/home/home_screen.dart
+      # Gate 3: dart analyze clean on the touched files.
+      flutter analyze lib/src/screens/home/home_screen.dart lib/src/widgets/top_bar.dart
+      # Gate 4: widget tests still pass (no regression on existing Home tests).
+      flutter test test/widget/connect_dial_test.dart --reporter compact
+      echo "Task 1 (§1) gates PASS"
+      '
+    </automated>
+  </verify>
+  <done>
+    HomeScreen TopBar invocation no longer carries `title: "Home"`; the
+    eyebrow `PROWLER` and the info IconButton remain. TopBar widget either
+    collapses cleanly on null/empty title or is patched to do so. `flutter
+    analyze` clean. UX-REVIEW §1 closed.
+  </done>
+</task>
+
+<task type="auto">
+  <name>Task 2 (Wave 1b — §2 splash hold): Cut Android 12+ splash hold from ~1.6s to ~800ms via declarative `windowSplashScreenAnimationDuration` in values-v31/styles.xml + values-night-v31/styles.xml</name>
+  <files>
+    prowler-client/flutter/android/app/src/main/res/values-v31/styles.xml,
+    prowler-client/flutter/android/app/src/main/res/values-night-v31/styles.xml
+  </files>
+  <action>
+**Step 1 — Add `windowSplashScreenAnimationDuration` to BOTH v31 styles.xml.**
+
+`values-v31/styles.xml` currently carries:
+```xml
+<style name="LaunchTheme" parent="@android:style/Theme.Light.NoTitleBar">
+    <item name="android:forceDarkAllowed">false</item>
+    <item name="android:windowFullscreen">false</item>
+    <item name="android:windowDrawsSystemBarBackgrounds">false</item>
+    <item name="android:windowLayoutInDisplayCutoutMode">shortEdges</item>
+    <item name="android:windowSplashScreenBackground">#0B0420</item>
+    <item name="android:windowSplashScreenAnimatedIcon">@drawable/android12splash</item>
+</style>
+```
+
+Use the Edit tool to add `<item name="android:windowSplashScreenAnimationDuration">800</item>`
+right after the `windowSplashScreenAnimatedIcon` line (matching the indent).
+
+Apply the IDENTICAL edit to `values-night-v31/styles.xml`.
+
+NOTE: Android caps `windowSplashScreenAnimationDuration` at 1000ms. 800ms is
+in-range per the Android-12 SplashScreen API docs
+(https://developer.android.com/develop/ui/views/launch/splash-screen#duration).
+The animated icon plays for this duration; once it completes, Android hands
+off to the Activity. Combined with Flutter cold-start (~600-800ms on AVD per
+07-12 measurement), the user-perceived splash window should land in the
+800-1200ms range (UX team target was 800ms — ~200ms reduction from current
+~1000ms+ engine cold-start, total window cut by ~600ms; ceiling 1000ms in the
+must_haves accommodates AVD measurement noise).
+
+Per the in-file flutter_native_splash.yaml comment, this XML file is one of
+the FOUR auto-generated by `flutter_native_splash:create` — BUT
+`flutter_native_splash` 2.4.7 does NOT manage `windowSplashScreenAnimationDuration`,
+so a manual addition is preserved across regens. If a future regen DOES wipe
+it (worth confirming once via diff), guard with a sed re-injection step in
+the regen wrapper — but at v0.7.0 ship, the hand-add is sufficient.
+
+**Step 2 — DO NOT add `androidx.core:core-splashscreen` Gradle dep** (the
+alternative programmatic `installSplashScreen().setKeepOnScreenCondition`
+path). Declarative wins because: (a) no Gradle churn, (b) no MainActivity
+edit, (c) matches the existing flutter_native_splash declarative model.
+
+**Step 3 — DO NOT touch `main.dart` or `FlutterNativeSplash.preserve()`** —
+the project does not use `preserve()`/`remove()` (grepped at plan time —
+zero hits in `lib/main.dart`). The Flutter side already auto-hides on
+first-frame; cutting the Android-side animation duration is the right lever.
+
+**Verification deferred to Wave 8a re-shoot** — the wall-clock measurement
+from launcher-tap to Home first-frame requires AVD cold-launch (covered in
+Wave 8a). The automated verify here is a structural grep that the duration
+landed; the empirical splash-hold ≤ 1000ms is a Wave 8a re-shoot
+acceptance criterion.
+
+**Per D-07-14 light-touch:** asset-config only, no AP-4 considerations.
+  </action>
+  <verify>
+    <automated>
+      bash -c '
+      set -euo pipefail
+      cd /home/parf/projects/work/prowler/prowler-client/flutter
+      # Gate 1: BOTH v31 styles.xml files carry the duration attribute set to 800.
+      grep -q "android:windowSplashScreenAnimationDuration\">800<" \
+        android/app/src/main/res/values-v31/styles.xml
+      grep -q "android:windowSplashScreenAnimationDuration\">800<" \
+        android/app/src/main/res/values-night-v31/styles.xml
+      # Gate 2: the value lands inside LaunchTheme, not NormalTheme.
+      # Confirm via awk that the line appears between <style name="LaunchTheme" and the closing </style>.
+      awk "/<style name=\"LaunchTheme\"/,/<\\/style>/" \
+        android/app/src/main/res/values-v31/styles.xml | grep -q "windowSplashScreenAnimationDuration"
+      awk "/<style name=\"LaunchTheme\"/,/<\\/style>/" \
+        android/app/src/main/res/values-night-v31/styles.xml | grep -q "windowSplashScreenAnimationDuration"
+      # Gate 3: 800 is within Android cap (0-1000ms inclusive). Documented assertion.
+      VAL=$(grep -oE "windowSplashScreenAnimationDuration\">[0-9]+<" \
+        android/app/src/main/res/values-v31/styles.xml | grep -oE "[0-9]+" | head -1)
+      [ "$VAL" -le 1000 ] && [ "$VAL" -ge 0 ]
+      echo "Task 2 (§2) gates PASS — empirical splash hold ≤ 1000ms verified in Wave 8a re-shoot"
+      '
+    </automated>
+  </verify>
+  <done>
+    `values-v31/styles.xml` AND `values-night-v31/styles.xml` LaunchTheme
+    carries `<item name="android:windowSplashScreenAnimationDuration">800</item>`.
+    Value within Android cap. Wall-clock splash-hold verification deferred to
+    Wave 8a re-shoot (cold-launch frames captured + measured).
+  </done>
+</task>
+
+<task type="auto">
+  <name>Task 3 (Wave 1c — §3 copy rewrites): 5 strings.dart edits per UX-REVIEW §3 table — drop `idle` meta consumer, drop em-dash placeholders, L1 EXIT `direct`, "Endpoints" → "servers" subtitle</name>
+  <files>
+    prowler-client/flutter/lib/src/l10n/strings.dart,
+    prowler-client/flutter/lib/src/screens/home/home_screen.dart
+  </files>
+  <action>
+**Per UX-REVIEW §3 table, the 5 rewrites map to 1 strings.dart edit + 4
+home_screen.dart edits** (because most "rewrites" are actually consumer-side
+conditional-rendering changes, NOT literal string-table edits — the literal
+`statusIdle = 'idle'` constant can stay in strings.dart but its Home-screen
+consumer should not render it; same for the em-dash chip values).
+
+**Step 1 — strings.dart edit (row 5):** change `serversSection` literal.
+
+  old_string: `  static const String serversSection = 'Endpoints. One per layer.';`
+  new_string: `  static const String serversSection = 'One server per layer.';`
+
+This is the only true literal rewrite per the §3 table (row 5).
+
+**Step 1.5 — strings.dart addition (B-4 prep — done here to keep the
+strings.dart commit atomic):** add the new no-config nudge string.
+
+  Insert AFTER the existing `errConsentCta` line (line 103), BEFORE `btnRetry`:
+  ```dart
+    // ---- No-config first-launch nudge (D-07-18) ----
+    static const String errNoConfigNudge = 'Paste a vless:// config to start.';
+  ```
+  This pre-positions the string for Wave 5 (B-4) without forcing Wave 5 to
+  re-edit strings.dart. Per the file's REQ-14 vocabulary discipline header
+  comment: `vless://` is the protocol literal, not forbidden vocab; it
+  appears already in `settingsConfigBody` ("Paste a vless:// URI to fill in
+  your endpoint.") so this string is consistent with established usage.
+
+**Step 2 — home_screen.dart edits (rows 1-4 of the UX-REVIEW §3 table).
+Lines 174-194 (the `_metaFor` + `_buildQuickRow` methods).**
+
+Row 1 (Dial meta `idle` removal): UX-REVIEW says "remove — the caption `Tap
+to prowl` already covers it". Currently `_buildDialMeta` non-connected branch
+calls `_metaFor(status)` which for idle returns `(Strings.statusIdle,
+ProwlerTokens.fog2)`. Fix: return an empty Text widget (zero-height
+SizedBox.shrink) for the idle state so no `idle` text renders. The dial
+caption ("Tap to prowl" from `_label(DialState.idle)`) is what the user
+sees.
+
+  Edit `_buildDialMeta` at line 129-172: when `status?.state == null` OR
+  `status?.state == pigeon.ConnectionState.idle`, return
+  `const SizedBox.shrink()` instead of building the Text widget. Keep the
+  connected branch + the connecting + error branches unchanged (those still
+  show handshake / tunnel-dropped meta).
+
+Row 2 (LAYER chip `— · idle` removal — `_buildQuickRow` line 197-202):
+currently when `activeMode == null` (idle), layerValue is `'— · idle'`. Per
+UX-REVIEW row 2: change to `'not connected'` OR hide chip values entirely
+until connected. Pick **hide the chips when idle** (UX-REVIEW's "or hide
+chip values entirely until connected" — cleanest, matches the dial-meta
+removal above). Edit: in `_buildQuickRow`, if `status == null` OR
+`status.state == pigeon.ConnectionState.idle` OR `status.state ==
+pigeon.ConnectionState.error`, return `const SizedBox.shrink()` instead of
+the Row of QuickChips. The chips reappear when state is `connecting` or
+`connected`.
+
+Row 3 (EXIT chip `—` removal — handled by row 2's hide-chips-when-idle).
+
+Row 4 (EXIT chip on L1 `—` + `exit · ms` units): when `activeMode ==
+Mode.direct` (L1 / no remote exit) AND `exitCountry == null`, show `'direct'`
+as the value (NOT em-dash); when `activeMode == Mode.bypass` (L2), continue
+to show no exit (existing logic). Edit `_buildQuickRow` line 203-205:
+```dart
+final String exitValue = switch (status?.activeMode) {
+  pigeon.Mode.bypass => Strings.quickBypassExitDash,
+  pigeon.Mode.direct => status?.exitCountry ?? 'direct',
+  pigeon.Mode.relay => status?.exitCountry ?? Strings.quickBypassExitDash,
+  null => Strings.quickBypassExitDash,
+};
+```
+(The `null` branch is unreachable after row 2's hide-when-idle, but kept
+for the exhaustive switch.)
+
+Row 4 also flags the `exit · ms` literal — but that B-2 fix (suppress
+empty values in the connected meta row) is in Task 4 (Wave 2). DO NOT touch
+the connected branch here; leave Task 4 to own the connected-row B-2 edit.
+
+**Critical: row 4's `direct` value is a USER-VISIBLE string but is NOT
+added to strings.dart** — UX-REVIEW intentionally suggested the lowercase
+inline literal `direct` (matching the lowercase voice). Document the
+deviation inline in home_screen.dart with a comment citing UX-REVIEW §3 row 4
+("currently `02e-home-dial-connected.png` reads literally `exit · ms`...
+Embarrassing in screenshots. This is blocker B-2"). The 1-word literal
+inline is the path of least friction; if a future Russian translation needs
+it, escalate to a Strings constant then.
+
+**REQ-14 lexicon check:** `direct` is the brand-allowed L1 layer name (per
+`layerL1Name = 'Direct'` line 52), here in lowercase to match status-line
+voice. No forbidden vocab.
+
+**Per D-07-14 light-touch:** Flutter-lib-only edits + asset-equivalent
+strings.dart row 5 rewrite.
+  </action>
+  <verify>
+    <automated>
+      bash -c '
+      set -euo pipefail
+      cd /home/parf/projects/work/prowler/prowler-client/flutter
+      # Gate 1: serversSection literal rewritten.
+      grep -q "serversSection = [\x27\x22]One server per layer.[\x27\x22]" lib/src/l10n/strings.dart
+      ! grep -q "[\x27\x22]Endpoints. One per layer.[\x27\x22]" lib/src/l10n/strings.dart
+      # Gate 2: errNoConfigNudge string added.
+      grep -q "errNoConfigNudge = [\x27\x22]Paste a vless:// config to start.[\x27\x22]" lib/src/l10n/strings.dart
+      # Gate 3: REQ-14 forbidden-vocab scan over the WHOLE strings.dart file (case-insensitive) — must still find zero hits.
+      # Strip comments before scanning to avoid self-matching the documentation that mentions the forbidden list.
+      ! grep -v "^\s*//" lib/src/l10n/strings.dart | grep -iE "(VPN|proxy|circumvention|censorship|firewall|government|freedom)"
+      # Gate 4: home_screen.dart `— · idle` quick-row literal no longer reachable on idle.
+      # Strong signal: the literal `null => [\x27\x22]— · idle[\x27\x22]` row in layerValue switch should be gone OR converted to SizedBox.shrink path.
+      ! grep -nE "[\x27\x22]— · idle[\x27\x22]" lib/src/screens/home/home_screen.dart
+      # Gate 5: home_screen.dart has a [\x27\x22]direct[\x27\x22] literal in the L1 exitValue branch.
+      grep -nE "[\x27\x22]direct[\x27\x22]" lib/src/screens/home/home_screen.dart
+      # Gate 6: flutter analyze clean.
+      flutter analyze lib/src/l10n/strings.dart lib/src/screens/home/home_screen.dart
+      echo "Task 3 (§3) gates PASS"
+      '
+    </automated>
+  </verify>
+  <done>
+    `strings.dart` carries the new `serversSection` literal AND the new
+    `errNoConfigNudge` constant; forbidden-vocab scan (excluding comments)
+    is zero. `home_screen.dart` no longer renders the `— · idle` quick-row
+    pair on idle, suppresses the dial-meta text on idle, and shows `direct`
+    for L1 EXIT when exitCountry is null. `flutter analyze` clean.
+  </done>
+</task>
+
+<task type="auto">
+  <name>Task 4 (Wave 2 — B-2 empty-value suppression): Fix the connected-state Home dial-meta row (`exit · ms` bug) — render only the non-empty parts of (exit prefix, country code, divider, latency ms)</name>
+  <files>prowler-client/flutter/lib/src/screens/home/home_screen.dart</files>
+  <action>
+**Root-cause confirmation** (from INVESTIGATION-260516-blockers.md adjacent
+to the UX-REVIEW §3 row 4 + B-2 entry): the bug is at
+`home_screen.dart` lines 134-160 — the connected branch of `_buildDialMeta`
+unconditionally renders `'exit '` prefix + code + ` · ` divider + `'$ms ms'`
+suffix. When the platform reports `Status(state: connected, exitCode: null,
+latencyMs: null)` (the L1 / no-remote-exit case before xray-core surfaces
+latency telemetry), the rendered Text.rich literally reads:
+```
+exit  · ⎵ms              (two consecutive spaces, bare " ms" with no leading number)
+```
+which is what UX-REVIEW screenshot `02e-home-dial-connected.png` captured.
+
+**Fix shape — conditional Text.rich children:**
+
+Edit `_buildDialMeta` at line 134-160 to build the TextSpan children list
+conditionally:
+
+```dart
+if (status?.state == pigeon.ConnectionState.connected) {
+  final String code = status?.exitCode ?? '';
+  final int? latency = status?.latencyMs;
+  const TextStyle base = TextStyle(
+    fontFamily: 'VT323',
+    fontSize: 18,
+    height: 1.4,
+    letterSpacing: 0.36,
+  );
+
+  // B-2 fix: build span list conditionally, only including each segment when
+  // its data is meaningful. Cases:
+  //   (a) code non-empty + latency non-null → `exit <code> · <latency> ms`  (full template)
+  //   (b) code non-empty + latency null     → `exit <code>`                 (no divider, no ms)
+  //   (c) code empty     + latency non-null → `<latency> ms`                (no exit prefix)
+  //   (d) code empty     + latency null     → SizedBox.shrink               (nothing to show)
+  // UX-REVIEW §3 row 4 + B-2 anti-regression: NEVER render literal `exit  · ` or bare ` ms`.
+
+  final bool hasCode = code.isNotEmpty;
+  final bool hasLatency = latency != null;
+  if (!hasCode && !hasLatency) {
+    return const SizedBox.shrink();
+  }
+
+  final List<TextSpan> children = <TextSpan>[];
+  if (hasCode) {
+    children.add(const TextSpan(
+      text: 'exit ',
+      style: TextStyle(color: ProwlerTokens.fog2),
+    ));
+    children.add(TextSpan(text: code));
+  }
+  if (hasCode && hasLatency) {
+    children.add(const TextSpan(
+      text: ' · ',
+      style: TextStyle(color: ProwlerTokens.fog2),
+    ));
+  }
+  if (hasLatency) {
+    children.add(TextSpan(text: '$latency ms'));
+  }
+  return Text.rich(
+    TextSpan(
+      style: base.copyWith(color: ProwlerTokens.cyan),
+      children: children,
+    ),
+  );
+}
+```
+
+The `_metaFor` switch on line 174-194 (legacy callers) already has the
+fallback `('exit $code · $ms ms', ...)` for the connected case at line 188-190;
+update its connected branch the same way for consistency (defensive — even
+though `_buildDialMeta` short-circuits before reaching `_metaFor` for
+connected state, the comment "for any other caller that may consume `_metaFor`
+in future" makes this an invariant worth preserving).
+
+Apply the same conditional logic to `_metaFor` line 188-190:
+```dart
+case pigeon.ConnectionState.connected:
+  final String code = s.exitCode ?? '';
+  final int? latency = s.latencyMs;
+  final StringBuffer buf = StringBuffer();
+  if (code.isNotEmpty) buf.write('exit $code');
+  if (code.isNotEmpty && latency != null) buf.write(' · ');
+  if (latency != null) buf.write('$latency ms');
+  return (buf.toString(), ProwlerTokens.cyan);
+```
+
+**Required widget-test addition** (Wave 2 owns this; no test scaffold exists
+for `_buildDialMeta` empty-value handling). Append to
+`prowler-client/flutter/test/widget/connect_dial_test.dart`:
+```dart
+testWidgets('connected with null exitCode + null latencyMs renders no meta '
+    '(B-2 anti-regression — never literal `exit  · ` or bare ` ms`)',
+    (WidgetTester tester) async {
+  await tester.pumpWidget(
+    ProviderScope(
+      overrides: [
+        connectionStatusProvider.overrideWith(
+          () => _FakeConnStatus(
+            pigeon.Status(
+              state: pigeon.ConnectionState.connected,
+              activeMode: pigeon.Mode.direct,
+              // exitCode + latencyMs intentionally omitted (== null)
+            ),
+          ),
+        ),
+      ],
+      child: const MaterialApp(
+        home: Scaffold(body: HomeScreen()),   // ← test mounts whole HomeScreen
+                                              //   to exercise _buildDialMeta
+      ),
+    ),
+  );
+  await tester.pump();
+  await tester.pump(const Duration(milliseconds: 50));
+  // NEVER any of these literal bugs:
+  expect(find.textContaining('exit  · '), findsNothing);
+  expect(find.textContaining(' ms'), findsNothing); // bare ` ms` with no leading digit
+  // Optional: assert no Text widget renders the bare divider literal.
+  expect(find.textContaining(' · '), findsNothing);
+});
+```
+(Import `HomeScreen` from `lib/src/screens/home/home_screen.dart`; the test
+file already imports `connection_state.dart` + `connect_dial.dart`.)
+
+**REQ-14 lexicon check:** new comment block mentions UX-REVIEW B-2 + §3
+row 4 — no forbidden vocab.
+
+**Per D-07-14 light-touch:** Flutter-lib-only edit + widget test.
+
+**Per CLAUDE.md "no continue statements":** the if-chain pattern matches the
+"prefer if-else chains over early returns" guideline (the early `if
+(!hasCode && !hasLatency) return SizedBox.shrink` is the single exception
+because it short-circuits the Text.rich allocation; this matches the existing
+file's early-return idiom for the loading/error cases).
+  </action>
+  <verify>
+    <automated>
+      bash -c '
+      set -euo pipefail
+      cd /home/parf/projects/work/prowler/prowler-client/flutter
+      # Gate 1: the buggy unconditional template literal is gone OR is only
+      # reachable inside the legacy unreachable _metaFor branch (defensive).
+      # The Text.rich children list-building pattern should appear in _buildDialMeta.
+      grep -q "children.add" lib/src/screens/home/home_screen.dart
+      grep -q "hasCode" lib/src/screens/home/home_screen.dart
+      grep -q "hasLatency" lib/src/screens/home/home_screen.dart
+      # Gate 2: no occurrence of the unconditional `$ms ms` literal that
+      # would render bare ` ms`. The new pattern uses `$latency ms` with a
+      # conditional guard.
+      ! grep -nE "[\x27\x22]\\\$ms ms[\x27\x22]" lib/src/screens/home/home_screen.dart
+      # Gate 3: B-2 widget test exists + the connect_dial_test suite still passes.
+      grep -q "B-2 anti-regression" test/widget/connect_dial_test.dart
+      flutter test test/widget/connect_dial_test.dart --reporter compact
+      # Gate 4: flutter analyze clean.
+      flutter analyze lib/src/screens/home/home_screen.dart test/widget/connect_dial_test.dart
+      echo "Task 4 (B-2) gates PASS"
+      '
+    </automated>
+  </verify>
+  <done>
+    `_buildDialMeta` connected branch builds Text.rich children list
+    conditionally (4 cases: code+latency, code-only, latency-only, neither);
+    never emits literal `exit  · ` or bare ` ms`; legacy `_metaFor` switch
+    updated for invariant consistency; new widget test asserts the
+    null-exitCode + null-latencyMs case renders no buggy literal. `flutter
+    analyze` + `flutter test` clean.
+  </done>
+</task>
+
+<task type="auto">
+  <name>Task 5 (Wave 3 — AP-4 EXCEPTION + B-3 platform): D-07-16 2-line Kotlin lift on ProwlerVpnService.kt (skip disconnected broadcast on start-failed) + D-07-17 Pigeon connectFailed enum add + regen + new AP-4-EXCEPTION-D-07-16 doc. **AP-4 EXCEPTION — cited per D-07-16; precedent: 5 prior exceptions in Phase 6 per 06-LEARNINGS.**</name>
+  <files>
+    prowler-client/android/app/src/main/java/com/prowler/client/vpn/ProwlerVpnService.kt,
+    prowler-client/flutter/pigeons/prowler_platform.dart,
+    prowler-client/flutter/lib/src/generated/prowler_platform.g.dart,
+    prowler-client/flutter/android/app/src/main/kotlin/com/prowler/client/generated/ProwlerPlatform.g.kt,
+    prowler-client/flutter/android/app/src/main/kotlin/com/prowler/client/ProwlerHostApiImpl.kt,
+    .planning/debug/AP4-EXCEPTION-D-07-16-START-FAILED-DISCONNECTED-SUPPRESSION.md
+  </files>
+  <action>
+**⚠ AP-4 BYTE-FREEZE EXCEPTION ⚠**
+Per **D-07-16** (locked decision in `07-CONTEXT.md ## v0.7.0 Gap Closure`):
+this task lifts the Phase-5 AP-4 byte-freeze on
+`prowler-client/android/app/src/main/java/com/prowler/client/vpn/ProwlerVpnService.kt`
+for a 2-line surgical edit. Precedent: 5 AP-4 exceptions already granted in
+Phase 6 (round-6 ProbeDiag, Bug-B structural, ROUND13-ARGV-ALIGN, ROUND15-
+PARITY-CLOSE, ROUND18-BDP-CONFIG — see `06-LEARNINGS.md` lines 124-156). This
+exception is structurally identical: small, reversible, scoped to one named
+behavior (skip the disconnected broadcast on start-failed), atomic-commit-able,
+documented in its own `.planning/debug/AP4-EXCEPTION-*.md` record.
+
+**Why a lift, not a Dart-side latch transformer alone:** per
+`INVESTIGATION-260516-blockers.md` Item 3 "SCOPE REDUCER option", the
+Dart-side StreamTransformer + StreamGroup.merge + new syntheticErrorStreamController
+chain is ~120 LOC across 4-5 files + 2 new widget tests; the 2-line Kotlin
+lift collapses this to ~30 LOC of Wave 4 Dart wiring + the AP-4 exception
+doc. User confirmation: "why is it frozen even? I think that is a
+misunderstanding" (per CONTEXT D-07-16 rationale).
+**rev-2 note (BLOCKER B1 fix):** Wave 4 (Task 6) ALSO adds a ~20 LOC
+Dart-side `errorLatchTransformer` as defense-in-depth + REGRESSION GATE.
+The Kotlin lift here is still the user-visible-bug fix; the Dart latch is
+the insurance.
+
+**rev-2 task split (per plan-checker WARNING W1):** this task contains
+TWO logical sub-tasks for executor focus. **Sub-task 5a** = AP-4 doc +
+Kotlin `stopLocked` lift in `ProwlerVpnService.kt` + cross-UID gate
+post-lift re-verify. **Sub-task 5b** = Pigeon enum extension + regen +
+`ProwlerHostApiImpl` synthesis wiring. The task split is for executor
+focus only — Sub-task 5b BUILDS ATOP Sub-task 5a (the cross-UID re-verify
+must pass before Sub-task 5b begins, because if the Kotlin lift broke
+the gate, Sub-task 5b would be undoing the lift, not extending it).
+**Single atomic commit bundles both sub-tasks** (commit shape in Step 5
+below). Do NOT split the commit.
+
+### Sub-task 5a — AP-4 doc + Kotlin lift + cross-UID re-verify
+
+**Step 1 — Author the AP-4 exception doc.** Use the Write tool at
+`.planning/debug/AP4-EXCEPTION-D-07-16-START-FAILED-DISCONNECTED-SUPPRESSION.md`.
+Read `.planning/debug/AP4-EXCEPTION-BUG-B-FIX.md` FIRST to mirror format
+exactly (precedent + structural template). Content shape:
+  - Title + date 2026-05-16 + grant authority (D-07-16 in 07-CONTEXT.md)
+  - Scope: ONE file, `prowler-client/android/app/src/main/java/com/prowler/client/vpn/ProwlerVpnService.kt`,
+    lines 300-302 (the `if (hadSession) { … }` block at the end of
+    `stopLocked(reason)`)
+  - Edit description: add `&& reason != "start-failed"` clause to the
+    `if (hadSession)` predicate so the trailing `disconnected("start-failed")`
+    broadcast is suppressed (the preceding `statusSink.error(...)` at line
+    257 carries the actionable error message and remains the only
+    user-visible status frame on the failure path)
+  - Why this preserves AP-4 intent: AP-4 protects Phase-5 routing/dispatch
+    behavior. The `disconnected("start-failed")` broadcast is a status-stream
+    UX artifact, NOT a routing/dispatch decision. The native cleanup path
+    (`runCatching { dependencies.native.stop() }`, `dependencies.byedpi.stop()`,
+    `tunResource?.close()`, `protectHandle` release) executes unchanged.
+    Cross-UID gate behavior unchanged (the gate observes byte-transfer +
+    protect-call counters, not the status-stream event sequence).
+  - Risk register: (a) downstream Kotlin consumers of `ACTION_STATUS_CHANGED`
+    that expect a `disconnected("start-failed")` broadcast after `error(...)`
+    will not see it — confirmed: zero such consumers (the only Dart consumer
+    is `lib/src/state/connection_state.dart` whose new behavior is to latch
+    the error frame); the Phase-5 :route-test cross-UID harness does not
+    consume the status stream. (b) Future regressions where a successful
+    teardown later inherits the `start-failed` reason string would also
+    suppress the disconnected broadcast — mitigated by the literal-equality
+    check `reason != "start-failed"` (other reasons unchanged).
+  - Reversibility: 2-character revert (`&& reason != "start-failed"` →
+    deletion); commit subject carries the exception ID so a future
+    `git log --grep` finds it.
+  - Test coverage substitutability:
+    (a) Wave 3 (this task) verify block runs `:route-test:connectedDebugAndroidTest`
+        on-device POST-lift; cross-UID gate counter assertions
+        (`bridgeProtectCallTotal=[1-9]`, `bridgeXrayDispatchLinkTotal=[1-9]`,
+        `bridgeDispatchLinkErrorTotal=0`, `L1.*escape_verified`) must all pass
+        — this empirically verifies the "gate observes byte-transfer + protect-call
+        counters, not the status-stream event sequence" claim. (rev-2 BLOCKER B2 fix.)
+    (b) Wave 4 (Task 6) widget test case A asserts `[connecting, error]`
+        latches `DialState.error` (bug-fix gate — proves the Kotlin lift works).
+    (c) Wave 4 (Task 6) widget test case B asserts `[connecting, error, idle]`
+        STILL latches `DialState.error` via the Dart-side errorLatchTransformer
+        (REGRESSION GATE — keeps the bug fixed even if the Kotlin lift reverts).
+        (rev-2 BLOCKER B1 fix.)
+  - References: D-07-16 in `.planning/phases/07-design-system-polish/07-CONTEXT.md`;
+    INVESTIGATION-260516-blockers.md Item 3; 06-LEARNINGS.md lines 124-156
+    (5 precedent exceptions); precedent template AP4-EXCEPTION-BUG-B-FIX.md.
+
+Minimum: 30 lines. Match the AP4-EXCEPTION-BUG-B-FIX.md heading structure +
+section ordering.
+
+**Step 2 — Apply the 2-line Kotlin edit on `ProwlerVpnService.kt`.**
+
+Locate lines 300-302 (the `stopLocked(reason)` private function's final
+block):
+```kotlin
+currentMode = MODE_NONE
+if (hadSession) {
+    dependencies.statusSink.disconnected(reason)
+}
+```
+
+Use the Edit tool. Apply the minimum-touch change — replace the
+`if (hadSession) {` predicate with the suppression guard.
+
+  old_string:
+```
+            currentMode = MODE_NONE
+            if (hadSession) {
+                dependencies.statusSink.disconnected(reason)
+            }
+```
+
+  new_string:
+```
+            currentMode = MODE_NONE
+            // AP-4 EXCEPTION (D-07-16, 2026-05-16): suppress the disconnected
+            // broadcast on the start-failed path so the preceding error(...)
+            // frame at line 257 isn't clobbered within 1 frame on the Dart
+            // onStatusChanged stream. See
+            // .planning/debug/AP4-EXCEPTION-D-07-16-START-FAILED-DISCONNECTED-SUPPRESSION.md
+            // for full rationale + risk register.
+            if (hadSession && reason != "start-failed") {
+                dependencies.statusSink.disconnected(reason)
+            }
+```
+
+(The indent here is 12 spaces — matches the inner-class scope. Verify
+indent via `awk 'NR==300{for(i=1;i<=length($0);i++)if(substr($0,i,1)!=" "){print "spaces=" i-1; exit}}'`
+before editing if the line numbers shift.)
+
+**Step 2.5 — Cross-UID gate post-lift re-verify (rev-2 BLOCKER B2 fix —
+INVARIANT before Sub-task 5b begins).** Run
+`./gradlew :route-test:connectedDebugAndroidTest -PtargetArchs=arm64-v8a`
+from `prowler-client/android/`. The verify block below codifies the exact
+assertions (`L1.*escape_verified`, `bridgeProtectCallTotal=[1-9]`,
+`bridgeXrayDispatchLinkTotal=[1-9]`, `bridgeDispatchLinkErrorTotal=0`) —
+if any fail, STOP Sub-task 5a here and investigate; do NOT proceed to
+Sub-task 5b. If all pass, the D-07-16 exception's "gate observes
+byte-transfer + protect-call counters, not the status-stream event
+sequence" claim is empirically verified, and Sub-task 5b can begin.
+
+### Sub-task 5b — Pigeon enum + regen + ProwlerHostApiImpl synthesis
+
+**Step 3 — Add `connectFailed` to Pigeon enum (D-07-17) + regen.**
+
+Edit `prowler-client/flutter/pigeons/prowler_platform.dart` lines 29-35:
+
+  old_string:
+```
+enum ConnectErrorCode {
+  networkUnavailable,
+  serverUnreachable,
+  coreCrashed,
+  consentDenied,
+  switchFailed,
+}
+```
+
+  new_string:
+```
+enum ConnectErrorCode {
+  networkUnavailable,
+  serverUnreachable,
+  coreCrashed,
+  consentDenied,
+  switchFailed,
+  // D-07-17 (2026-05-16): added for the B-3 silent-fail wiring fix. Emitted
+  // by Kotlin's ProwlerHostApiImpl.connect-catch (and/or ErrorEventListener
+  // synthesis path) when ProwlerNative.start() raises after xray-core's
+  // internal retry loop exhausts. Mapped Dart-side in error_banner.dart's
+  // _templateFor switch to (Strings.errConnectFailedHeading,
+  // Strings.errConnectFailedBody, [btnRetry, btnSwitchLayer]) — the exact
+  // strings UX team referenced (UX-REVIEW.md §5 Bug #1).
+  connectFailed,
+}
+```
+
+Regenerate codegen artifacts:
+```bash
+cd /home/parf/projects/work/prowler/prowler-client/flutter && \
+  dart run pigeon --input pigeons/prowler_platform.dart
+```
+
+This rewrites BOTH:
+  - `lib/src/generated/prowler_platform.g.dart` (Dart codegen)
+  - `android/app/src/main/kotlin/com/prowler/client/generated/ProwlerPlatform.g.kt` (Kotlin codegen)
+
+DO NOT hand-edit those .g files — they appear in `files_modified:` only
+because the regen step rewrites them. Confirm both files now expose the
+new enum case via:
+```bash
+grep -q "connectFailed" /home/parf/projects/work/prowler/prowler-client/flutter/lib/src/generated/prowler_platform.g.dart
+grep -q "connectFailed\|CONNECT_FAILED" /home/parf/projects/work/prowler/prowler-client/flutter/android/app/src/main/kotlin/com/prowler/client/generated/ProwlerPlatform.g.kt
+```
+
+**Step 4 — Wire the Kotlin-side synthesis path.**
+
+Read `prowler-client/flutter/android/app/src/main/kotlin/com/prowler/client/ProwlerHostApiImpl.kt`
++ `ErrorEventListener.kt` to determine the synthesis shape. The existing
+listener exposes a sink for emitting `ConnectError` events; the
+`ProwlerHostApiImpl.connect(...)` method should catch the `start()`
+failure (post-AP-4-lift, the error message is still surfaced via
+`statusSink.error(...)`) AND additionally push a
+`ConnectError(code = ConnectErrorCode.CONNECT_FAILED, detail = errMessage)`
+through the error listener's sink so the Dart `errorEventsProvider` (a
+StreamNotifier wrapping Pigeon's `onError()`) re-emits it.
+
+NOTE: this is the SECOND part of the Kotlin lift — strictly speaking, only
+the 2-line edit in `stopLocked` (Step 2) is the byte-frozen-source edit;
+`ProwlerHostApiImpl.kt` and `ErrorEventListener.kt` live under
+`prowler-client/flutter/android/app/src/main/kotlin/com/prowler/client/`
+which is the **FLUTTER project's Android host** (not Phase-5 frozen
+source per 07-CONTEXT.md `<code_context>` `### Reusable Assets` correction).
+Those files are NOT under AP-4. The AP-4 exception is ONLY for the
+`prowler-client/android/...` ProwlerVpnService.kt 2-line edit.
+
+Step 4 fallback shapes (executor inspects + picks):
+  (a) If `ErrorEventListener` exposes a `pushError(ConnectError)` method:
+      call it from `ProwlerHostApiImpl.connect`'s catch block on
+      `connect()`-failure with `ConnectErrorCode.CONNECT_FAILED`.
+  (b) If `ErrorEventListener` is a pure-passive EventChannel sink with
+      no injection method: add a `synthesizeError(ConnectError)` method
+      to the listener (the EventChannel handler exposes a `sink`
+      reference) and call from `ProwlerHostApiImpl`.
+
+Either way: the result is that on `start-failed`, the Dart side observes
+ONE `error` Status frame on `onStatusChanged` + ONE `ConnectError(code:
+connectFailed)` frame on `onError`. `ErrorBanner` renders.
+
+**Step 5 — Atomic commit shape (Sub-task 5a + 5b bundled into ONE commit
+per rev-2 WARNING W1 split intent).** This task produces ONE commit:
+```
+fix(07-13): B-3 connect-failure wiring — AP-4 EXCEPTION (D-07-16) +
+            ConnectErrorCode.connectFailed (D-07-17)
+            [rev-2 cross-UID gate post-lift verified — BLOCKER B2]
+
+Sub-task 5a — AP-4 lift + post-lift gate verify:
+* ProwlerVpnService.kt stopLocked: skip disconnected("start-failed")
+  broadcast so the preceding statusSink.error(...) frame is not clobbered
+  on the Dart onStatusChanged stream. AP-4 byte-freeze EXCEPTION per
+  D-07-16; rationale + risk register at
+  .planning/debug/AP4-EXCEPTION-D-07-16-START-FAILED-DISCONNECTED-SUPPRESSION.md.
+  Precedent: 5 prior Phase-6 AP-4 exceptions per 06-LEARNINGS.md.
+* :route-test:connectedDebugAndroidTest re-run post-lift; cross-UID gate
+  counter assertions all pass (rev-2 BLOCKER B2 verification).
+
+Sub-task 5b — Pigeon enum + Kotlin synthesis:
+* pigeons/prowler_platform.dart: add ConnectErrorCode.connectFailed
+  per D-07-17. Regenerate .g.dart + .g.kt. Kotlin
+  ProwlerHostApiImpl.connect catch-path synthesises ConnectError(
+  code = CONNECT_FAILED) so Dart errorEventsProvider surfaces it.
+
+Wave-4 (Task 6) wires error_banner._templateFor → errConnectFailed*
+strings + adds Dart-side errorLatchTransformer (rev-2 BLOCKER B1
+defense-in-depth) + adds widget test pair (Case A bug-fix gate +
+Case B regression gate).
+```
+
+Commit message MUST cite D-07-16 and D-07-17 in the subject and reference
+rev-2 BLOCKER B2 in the trailer.
+  </action>
+  <verify>
+    <automated>
+      bash -c '
+      set -euo pipefail
+      cd /home/parf/projects/work/prowler
+      # Gate 1: AP-4 exception doc exists + is ≥30 lines.
+      [ -f .planning/debug/AP4-EXCEPTION-D-07-16-START-FAILED-DISCONNECTED-SUPPRESSION.md ]
+      [ "$(wc -l < .planning/debug/AP4-EXCEPTION-D-07-16-START-FAILED-DISCONNECTED-SUPPRESSION.md)" -ge 30 ]
+      # Gate 2: doc cites D-07-16.
+      grep -q "D-07-16" .planning/debug/AP4-EXCEPTION-D-07-16-START-FAILED-DISCONNECTED-SUPPRESSION.md
+      # Gate 3: ProwlerVpnService.kt has the start-failed suppression guard.
+      grep -q "reason != \"start-failed\"" \
+        prowler-client/android/app/src/main/java/com/prowler/client/vpn/ProwlerVpnService.kt
+      # Gate 4: Pigeon source carries connectFailed enum value.
+      grep -q "connectFailed" prowler-client/flutter/pigeons/prowler_platform.dart
+      # Gate 5: codegen artifacts regenerated (both Dart and Kotlin).
+      grep -q "connectFailed" prowler-client/flutter/lib/src/generated/prowler_platform.g.dart
+      grep -qE "connectFailed|CONNECT_FAILED" \
+        prowler-client/flutter/android/app/src/main/kotlin/com/prowler/client/generated/ProwlerPlatform.g.kt
+      # Gate 6: Kotlin side synthesises the new code in the connect-catch path.
+      grep -qE "CONNECT_FAILED|ConnectErrorCode\\.connectFailed" \
+        prowler-client/flutter/android/app/src/main/kotlin/com/prowler/client/ProwlerHostApiImpl.kt
+      # Gate 7: Phase-5 cross-UID Kotlin still compiles (the byte-freeze module).
+      cd prowler-client/android && ./gradlew :app:compileDebugKotlin
+      cd /home/parf/projects/work/prowler/prowler-client/flutter && \
+        flutter analyze lib/src/generated/prowler_platform.g.dart
+      # ---- rev-2 BLOCKER B2: AP-4 cross-UID gate post-lift regression check ----
+      # The D-07-16 exception\x27s central claim is that the cross-UID gate
+      # observes byte-transfer + protect-call counters, NOT the status-stream
+      # event sequence. Compile-only verification (Gate 7) does NOT prove
+      # that claim — the gate must run on-device after the lift. This is the
+      # canonical post-AP-4-exception regression check (precedent: Phase 5
+      # 05-15 + 05-16 SUMMARYs re-ran this exact gate after backend changes;
+      # Phase 6 plans re-ran it after every byte-freeze exception).
+      #
+      # Runs on the currently-attached AVD or device (the route-test module
+      # auto-discovers `adb devices` and uses the first online entry).
+      cd /home/parf/projects/work/prowler/prowler-client/android && \
+        ./gradlew :route-test:connectedDebugAndroidTest -PtargetArchs=arm64-v8a 2>&1 \
+          | tee /tmp/route-test-postlift.log
+      grep -q "L1.*escape_verified" /tmp/route-test-postlift.log || { \
+        echo "FAIL (rev-2 BLOCKER B2): cross-UID L1 strict assertions regressed post-D-07-16 lift"; \
+        exit 1; }
+      grep -qE "bridgeProtectCallTotal=[1-9]" /tmp/route-test-postlift.log || { \
+        echo "FAIL (rev-2 BLOCKER B2): protect-call counter regressed post-lift"; \
+        exit 1; }
+      grep -qE "bridgeXrayDispatchLinkTotal=[1-9]" /tmp/route-test-postlift.log || { \
+        echo "FAIL (rev-2 BLOCKER B2): xray-dispatch-link counter regressed post-lift"; \
+        exit 1; }
+      grep -qE "bridgeDispatchLinkErrorTotal=0" /tmp/route-test-postlift.log || { \
+        echo "FAIL (rev-2 BLOCKER B2): dispatch-link errors surfaced post-lift"; \
+        exit 1; }
+      echo "rev-2 BLOCKER B2 cross-UID gate post-D-07-16-lift regression check PASS"
+      # ---- end rev-2 BLOCKER B2 cross-UID gate ----
+      echo "Task 5 (B-3 platform + AP-4 doc + rev-2 BLOCKER B2 cross-UID gate) gates PASS"
+      '
+    </automated>
+  </verify>
+  <done>
+    AP-4 exception doc exists at `.planning/debug/AP4-EXCEPTION-D-07-16-*.md`
+    with ≥30 lines + cites D-07-16. `ProwlerVpnService.kt:stopLocked` carries
+    the `reason != "start-failed"` suppression guard. Pigeon source adds
+    `connectFailed` + both .g.dart + .g.kt regenerated. Kotlin
+    `ProwlerHostApiImpl.connect` catch-path synthesises
+    `ConnectErrorCode.connectFailed`. Phase-5 cross-UID Kotlin module compiles
+    clean (`./gradlew :app:compileDebugKotlin`).
+    **rev-2 BLOCKER B2:** `:route-test:connectedDebugAndroidTest` re-run
+    post-D-07-16-lift confirms cross-UID gate stays green: `L1.*escape_verified`
+    + `bridgeProtectCallTotal=[1-9]` + `bridgeXrayDispatchLinkTotal=[1-9]` +
+    `bridgeDispatchLinkErrorTotal=0` all present in
+    `/tmp/route-test-postlift.log`. This empirically verifies the D-07-16
+    exception\x27s claim that "the gate observes byte-transfer + protect-call
+    counters, not the status-stream event sequence."
+    Atomic commit cites D-07-16 + D-07-17 in subject.
+  </done>
+</task>
+
+<task type="auto">
+  <name>Task 6 (Wave 4 — B-3 Dart + rev-2 BLOCKER B1 fix): Map ConnectErrorCode.connectFailed → errConnectFailed* in error_banner._templateFor; add Dart-side errorLatchTransformer in connection_state.dart (~20 LOC defense-in-depth per `INVESTIGATION-260516-blockers.md` Item 3 SCOPE REDUCER); add widget test case A (`[connecting, error]`) AND test case B (`[connecting, error, idle]` — THE regression gate for the D-07-16 AP-4 lift). Test case B passes even if the Kotlin lift reverts, because the Dart-side latch holds the dial in error.</name>
+  <files>
+    prowler-client/flutter/lib/src/widgets/error_banner.dart,
+    prowler-client/flutter/lib/src/state/connection_state.dart,
+    prowler-client/flutter/test/widget/error_banner_test.dart,
+    prowler-client/flutter/test/widget/connect_dial_test.dart
+  </files>
+  <action>
+**SEQUENCING — INVARIANT:** this task MUST run AFTER Task 5 (Pigeon regen).
+The `error_banner.dart._templateFor` switch is exhaustive (no `default:`
+case); adding the new case is a no-op until `pigeon.ConnectErrorCode.connectFailed`
+exists in `lib/src/generated/prowler_platform.g.dart`. Wave 3 → Wave 4 inside
+this plan; do NOT parallel-run.
+
+**Step 1 — Add the `connectFailed` case to `_templateFor`.**
+
+Edit `prowler-client/flutter/lib/src/widgets/error_banner.dart` lines 96-124
+(the exhaustive switch on `code`). Add a new case AFTER `switchFailed`
+(matching the enum source order):
+
+```dart
+      case pigeon.ConnectErrorCode.switchFailed:
+        return (Strings.errSwitchHeading, Strings.errSwitchBody, <Widget>[
+          _btn(Strings.btnRetry, () => _retry(ref)),
+        ]);
+      case pigeon.ConnectErrorCode.connectFailed:
+        // B-3 / D-07-17 — UX team's exact strings (UX-REVIEW.md §5 Bug #1):
+        //   `Connection failed.` / `We tried 3 times. Switch layer or check your network.`
+        // Actions: Retry + Switch layer (the two paths UX team enumerated;
+        // open-settings is third-priority and omitted to keep the banner
+        // tight). The Strings.errConnectFailedHeading + Strings.errConnectFailedBody
+        // constants have existed since Phase 6 (06-04 wired them but only
+        // for the legacy coreCrashed case which UX team reframed); D-07-17
+        // gives them their own ConnectErrorCode case so the lexicon match is
+        // semantic, not coincidental.
+        return (
+          Strings.errConnectFailedHeading,
+          Strings.errConnectFailedBody,
+          <Widget>[
+            _btn(Strings.btnRetry, () => _retry(ref)),
+            _btn(Strings.btnSwitchLayer, () => context.go('/layers')),
+          ],
+        );
+```
+
+**Step 2 — Append the B-3 widget test to `error_banner_test.dart`.**
+
+Append a test case asserting the new code triggers the expected template:
+```dart
+testWidgets('connectFailed code renders Connection failed. heading + body + '
+    'Retry & Switch layer actions (B-3 / D-07-17)',
+    (WidgetTester tester) async {
+  await _pumpAt(tester, pigeon.ConnectErrorCode.connectFailed);
+  await tester.pump();
+  expect(find.text(Strings.errConnectFailedHeading), findsOneWidget);
+  expect(find.text(Strings.errConnectFailedBody), findsOneWidget);
+  expect(find.text(Strings.btnRetry), findsOneWidget);
+  expect(find.text(Strings.btnSwitchLayer), findsOneWidget);
+});
+```
+
+Also verify the existing 6th anti-regression test (`coreCrashed banner
+heading is "Connection failed.", NOT "Tunnel dropped."`) still passes —
+the new connectFailed case shares the heading string but is a distinct enum
+case; the lexicon-anti-regression assertion holds.
+
+**Step 3 — Add the Dart-side `errorLatchTransformer` to
+`connection_state.dart` (~20 LOC defense-in-depth — rev-2 BLOCKER B1 fix).**
+
+Per `INVESTIGATION-260516-blockers.md` Item 3 SCOPE REDUCER discussion: the
+2-line Kotlin lift (D-07-16) is the user-visible-bug fix, but it is NOT a
+REGRESSION GATE on its own — a future maintainer who reverts the
+`reason != "start-failed"` predicate reintroduces the bug, and a naive
+widget test that just checks `dialError` appears with a pre-supplied
+`[connecting, error]` stream passes silently. The Dart-side latch is the
+"~30 LOC of insurance" the investigation called for — it observes the
+actual platform-emitted sequence and holds the error frame if a trailing
+`idle`/`disconnected` follows without an intervening `connected`.
+
+Read `prowler-client/flutter/lib/src/state/connection_state.dart` to locate
+the existing `ConnectionStatus` AsyncNotifier `build()` method that wraps
+`pigeon.ProwlerEventsApi.onStatusChanged`. The new transformer wraps that
+stream:
+
+```dart
+/// Defense-in-depth latch (rev-2 BLOCKER B1 fix; companion to D-07-16
+/// AP-4 Kotlin lift). When the platform emits `[connecting, error, idle]`
+/// without an intervening `connected`, hold the dial in error rather than
+/// letting `idle` clobber the error frame.
+///
+/// The D-07-16 Kotlin lift means the trailing `idle` shouldn't fire on
+/// the start-failed path — but if that lift is ever reverted (whether
+/// accidentally or by a future refactor that misses the predicate), this
+/// latch keeps the user-visible behavior correct. The latch is
+/// REGRESSION-GATED by widget-test case B in `connect_dial_test.dart`:
+/// even if the Kotlin lift reverts, case B still passes because the Dart
+/// latch holds.
+///
+/// Per `INVESTIGATION-260516-blockers.md` Item 3, the SCOPE REDUCER
+/// originally costed this at ~30 LOC of insurance; the actual
+/// implementation lands around 20 LOC (the state machine has 4 transitions
+/// the latch cares about — connected → reset, connecting → arm, error →
+/// latch, idle-after-armed-error → suppress).
+StreamTransformer<pigeon.Status, pigeon.Status> errorLatchTransformer() {
+  bool latched = false;
+  return StreamTransformer<pigeon.Status, pigeon.Status>.fromHandlers(
+    handleData: (pigeon.Status event, EventSink<pigeon.Status> sink) {
+      // A real `connected` frame resets the latch — we are healthy again.
+      if (event.state == pigeon.ConnectionState.connected) {
+        latched = false;
+        sink.add(event);
+        return;
+      }
+      // An `error` frame arms the latch — we MUST hold this state until
+      // a future `connected` resets it. Forward the error to the sink.
+      if (event.state == pigeon.ConnectionState.error) {
+        latched = true;
+        sink.add(event);
+        return;
+      }
+      // An `idle`/`disconnected` frame AFTER a latched error is the bug
+      // shape — suppress it. Per D-07-16's Kotlin lift this shouldn't
+      // arrive, but the latch is defense-in-depth.
+      if (latched && event.state == pigeon.ConnectionState.idle) {
+        return;  // suppress; do NOT add to sink
+      }
+      // Any other frame (idle pre-error, connecting, etc.) — forward.
+      sink.add(event);
+    },
+  );
+}
+```
+
+Wire the transformer into the existing `ConnectionStatus.build()` stream
+chain — find the line where `onStatusChanged` is consumed and pipe through
+`.transform(errorLatchTransformer())` BEFORE the stream returns. Likely
+shape (read the actual file to confirm method names):
+
+```dart
+@override
+Stream<pigeon.Status> build() {
+  return pigeon.ProwlerEventsApi.onStatusChanged()   // platform stream
+      .transform(errorLatchTransformer());            // <-- rev-2 latch
+}
+```
+
+(If `ConnectionStatus` is an `AsyncNotifier` rather than a `StreamNotifier`,
+adapt by transforming the platform stream inside whatever subscribe pattern
+the notifier uses — read the file's current shape and match.)
+
+**Step 4 — Append BOTH widget test cases to `connect_dial_test.dart`.**
+
+Add the multi-frame `_FakeConnStatusSeq` test-double once (shared by both
+cases), then add two `testWidgets` cases. Case A is the existing test
+shape the plan-checker called "naive"; case B is the regression gate.
+
+```dart
+/// Test double for [ConnectionStatus] that emits a sequence of statuses
+/// then halts. Used for the B-3 regression test pair.
+///
+/// **rev-3 INFO#1 fix:** the build() override pipes the raw frame
+/// sequence through `.transform(errorLatchTransformer())` so test case B
+/// genuinely exercises the latch. Without this pipe, case B would pass
+/// for the wrong reason (the harness would just emit [connecting, error,
+/// idle] and the most-recent-frame mapping would yield idle — but the
+/// pumpAndSettle final-state expectation of error is still met because
+/// the dial widget snapshots the most recent ASYNC frame, not the most
+/// recent stream value; the result would silently pass even if the latch
+/// were removed). Wiring through the actual transformer makes the test
+/// fail-LOUD if errorLatchTransformer is removed/broken.
+class _FakeConnStatusSeq extends ConnectionStatus {
+  _FakeConnStatusSeq(this._fakeStatuses);
+  final List<pigeon.Status> _fakeStatuses;
+  @override
+  Stream<pigeon.Status> build() =>
+      Stream<pigeon.Status>.fromIterable(_fakeStatuses)
+          .transform(errorLatchTransformer());
+}
+
+testWidgets('Case A — connecting → error latches DialState.error '
+    '(B-3 / D-07-16 — bug-fix gate, asserts the post-lift Kotlin behaviour)',
+    (WidgetTester tester) async {
+  await tester.pumpWidget(
+    ProviderScope(
+      overrides: <Override>[
+        connectionStatusProvider.overrideWith(
+          () => _FakeConnStatusSeq(<pigeon.Status>[
+            pigeon.Status(
+              state: pigeon.ConnectionState.connecting,
+              activeMode: pigeon.Mode.direct,
+            ),
+            pigeon.Status(
+              state: pigeon.ConnectionState.error,
+              activeMode: pigeon.Mode.direct,
+              errorMessage: 'xray-core exhausted retry budget',
+            ),
+            // NO trailing idle/disconnected frame — D-07-16 Kotlin lift
+            // suppresses it. This is the post-lift platform output shape.
+          ]),
+        ),
+      ],
+      child: const MaterialApp(home: Scaffold(body: ConnectDial())),
+    ),
+  );
+  await tester.pumpAndSettle();
+  expect(find.text(Strings.dialError), findsOneWidget);
+  expect(find.text(Strings.dialIdle), findsNothing);
+});
+
+testWidgets('Case B — connecting → error → idle STILL latches '
+    'DialState.error (B-3 / rev-2 BLOCKER B1 REGRESSION GATE — '
+    'asserts the Dart-side latch holds even if the D-07-16 Kotlin lift '
+    'reverts to the pre-lift behaviour)',
+    (WidgetTester tester) async {
+  await tester.pumpWidget(
+    ProviderScope(
+      overrides: <Override>[
+        connectionStatusProvider.overrideWith(
+          () => _FakeConnStatusSeq(<pigeon.Status>[
+            pigeon.Status(
+              state: pigeon.ConnectionState.connecting,
+              activeMode: pigeon.Mode.direct,
+            ),
+            pigeon.Status(
+              state: pigeon.ConnectionState.error,
+              activeMode: pigeon.Mode.direct,
+              errorMessage: 'xray-core exhausted retry budget',
+            ),
+            // SIMULATES the pre-lift Kotlin behaviour: a trailing `idle`
+            // arrives after `error`. The Dart-side errorLatchTransformer
+            // (added in Step 3) MUST suppress this `idle` so the dial
+            // stays latched on error.
+            //
+            // If a future regression reverts the D-07-16 lift, the
+            // platform stream looks like THIS sequence; this case asserts
+            // the Dart latch holds the line.
+            pigeon.Status(
+              state: pigeon.ConnectionState.idle,
+              activeMode: null,
+            ),
+          ]),
+        ),
+      ],
+      child: const MaterialApp(home: Scaffold(body: ConnectDial())),
+    ),
+  );
+  await tester.pumpAndSettle();
+  // After the stream drains, dial MUST still show error label.
+  // If this assertion ever fires, either the Dart latch regressed OR
+  // the test wiring no longer goes through ConnectionStatus.build().
+  expect(find.text(Strings.dialError), findsOneWidget);
+  expect(find.text(Strings.dialIdle), findsNothing);
+});
+```
+
+(Import `Strings` from `lib/src/l10n/strings.dart`. Import the actual
+`ConnectionStatus` class — its provider override pattern matches the
+existing `_FakeConnStatus` test double on lines 21-30 of the same file.)
+
+NOTE the test case B assertion semantics (rev-3 INFO#1 fix applied):
+`_FakeConnStatusSeq.build()` now PIPES the raw 3-frame sequence
+through `.transform(errorLatchTransformer())` (see the class
+definition above). This means test case B genuinely exercises the
+Dart latch — if `errorLatchTransformer()` is removed from the
+codebase, removed from `connection_state.dart`'s `build()`, or its
+internal state-machine bug regresses (e.g. the `latched` flag stops
+guarding the idle suppression), the test will FAIL on the
+`expect(find.text(Strings.dialError), findsOneWidget)` line because
+the trailing `idle` frame will reach the dial widget unfiltered.
+
+Without the `.transform(...)` pipe, test case B would still pass
+for the wrong reason (the dial widget snapshots the latest async
+frame; the harness emits `[connecting, error, idle]` and the latest
+is idle — but Flutter's `AsyncValue<Status>` to `DialState` mapping
+would still resolve the dial to idle, so a naïve test wouldn't catch
+the latch regression). The pipe is what makes case B a TRUE
+regression gate.
+
+This pairing is the differential signal: case A asserts the post-
+D-07-16-lift platform output (`[connecting, error]`) latches
+DialState.error — proves the Kotlin lift works. Case B asserts
+that even if the Kotlin lift reverts (so platform reverts to
+`[connecting, error, idle]`), the Dart-side latch STILL holds the
+dial in error — proves the defense-in-depth insurance fires. Both
+tests are real regression gates: one for the Kotlin bug-fix, one
+for the Dart safety net.
+
+**Step 5 — Run the full widget suite to confirm zero regression** (especially
+the existing 5 ConnectDial state tests + the 8 ErrorBanner tests + the
+2 new test cases A and B):
+```bash
+cd /home/parf/projects/work/prowler/prowler-client/flutter && \
+  flutter test test/widget/ --reporter compact
+```
+
+**REQ-14 lexicon check:** the connectFailed case returns existing `Strings.*`
+constants that already passed the 07-08 neutral-vocab scan. No new
+user-visible literals.
+
+**Per D-07-14 light-touch:** Flutter-lib-only edit + 2 widget test additions.
+
+**Atomic commit shape:**
+```
+feat(07-13): B-3 ErrorBanner wiring + Dart-side latch + regression-gated tests (D-07-16/17 + rev-2 BLOCKER B1)
+
+* error_banner._templateFor: map ConnectErrorCode.connectFailed →
+  Strings.errConnectFailedHeading + Strings.errConnectFailedBody + Retry +
+  Switch layer actions (UX team\x27s exact strings per UX-REVIEW.md §5 Bug #1).
+
+* connection_state.dart: add errorLatchTransformer (~20 LOC defense-in-depth
+  per INVESTIGATION-260516-blockers.md Item 3 SCOPE REDUCER — \"~30 LOC of
+  insurance\"). Wired into ConnectionStatus.build() via .transform(...). The
+  Kotlin D-07-16 lift remains the user-visible bug fix; this latch is the
+  REGRESSION GATE — if the Kotlin lift ever reverts, the Dart latch keeps
+  the dial latched on error.
+
+* error_banner_test: assert connectFailed template renders correctly.
+
+* connect_dial_test: TWO new test cases pair-up the gate:
+  - Case A: [connecting, error] → dial latches error (bug-fix gate).
+  - Case B: [connecting, error, idle] → dial STILL latches error (the
+    REGRESSION GATE; differentiates latch-present from latch-absent
+    deterministically, even with the Kotlin lift in place).
+```
+  </action>
+  <verify>
+    <automated>
+      bash -c '
+      set -euo pipefail
+      cd /home/parf/projects/work/prowler/prowler-client/flutter
+      # Gate 1: new connectFailed case lands in error_banner._templateFor.
+      grep -q "case pigeon.ConnectErrorCode.connectFailed" lib/src/widgets/error_banner.dart
+      # Gate 2: new template-mapping widget test exists.
+      grep -q "B-3 / D-07-17" test/widget/error_banner_test.dart
+      # Gate 3 (rev-2 BLOCKER B1): Dart-side errorLatchTransformer exists in connection_state.dart.
+      grep -q "errorLatchTransformer" lib/src/state/connection_state.dart
+      # Gate 3b: latch is actually wired into ConnectionStatus.build() — look for the
+      # .transform(errorLatchTransformer()) call (or equivalent pipe-through).
+      grep -qE "\.transform\(\s*errorLatchTransformer\(\)" lib/src/state/connection_state.dart
+      # Gate 4 (rev-2 BLOCKER B1): test-case A (`[connecting, error]`) exists.
+      grep -q "Case A — connecting → error" test/widget/connect_dial_test.dart
+      # Gate 5 (rev-2 BLOCKER B1): test-case B (`[connecting, error, idle]`) — THE regression gate.
+      grep -q "Case B — connecting → error → idle" test/widget/connect_dial_test.dart
+      grep -q "REGRESSION GATE" test/widget/connect_dial_test.dart
+      grep -q "_FakeConnStatusSeq" test/widget/connect_dial_test.dart
+      # Gate 6: full widget test suite passes (no regression; both new test cases included).
+      flutter test test/widget/ --reporter compact
+      # Gate 7: flutter analyze clean on all touched files + test files.
+      flutter analyze lib/src/widgets/error_banner.dart \
+        lib/src/state/connection_state.dart \
+        test/widget/error_banner_test.dart test/widget/connect_dial_test.dart
+      echo "Task 6 (B-3 Dart + rev-2 BLOCKER B1 fix) gates PASS"
+      '
+    </automated>
+  </verify>
+  <done>
+    `error_banner._templateFor` switch has a new `connectFailed` case
+    returning the errConnectFailed* strings + Retry/Switch-layer actions.
+    `connection_state.dart` carries a new `errorLatchTransformer` (~20 LOC
+    defense-in-depth) wired into `ConnectionStatus.build()` via
+    `.transform(errorLatchTransformer())`. THREE new widget tests:
+      (a) error_banner — template mapping for `connectFailed` code;
+      (b) connect_dial Case A — `[connecting, error]` latches `DialState.error`
+          (post-D-07-16-lift bug-fix gate);
+      (c) connect_dial Case B — `[connecting, error, idle]` STILL latches
+          `DialState.error` (rev-2 BLOCKER B1 REGRESSION GATE — Dart latch
+          holds even if the Kotlin lift reverts).
+    Full widget suite + flutter analyze clean.
+  </done>
+</task>
+
+<task type="auto">
+  <name>Task 7 (Wave 5 — B-4): Capture validation issues in connect_dial.dart dial-tap handler; fire SnackBar(errNoConfigNudge) + context.go('/settings') on config-missing branch; new widget test asserts the empty-config path</name>
+  <files>
+    prowler-client/flutter/lib/src/widgets/connect_dial.dart,
+    prowler-client/flutter/test/widget/no_config_nudge_test.dart
+  </files>
+  <action>
+**Per D-07-18 (locked):** the no-config signal shape is
+`ScaffoldMessenger.showSnackBar` carrying `Strings.errNoConfigNudge`
+(`'Paste a vless:// config to start.'` — added to strings.dart in Task 3
+Step 1.5) + `context.go('/settings')` navigation. Matches UX team's
+verbatim request in UX-REVIEW.md §2 ¶4 ("should NOT just fail silently →
+it should bounce to Settings → Paste from clipboard with a one-line
+nudge").
+
+**Per INVESTIGATION-260516-blockers.md Item 1:** the gap is at
+`connect_dial.dart:186-191` — the dial-tap handler currently calls
+`await ref.read(connectionActionsProvider.notifier).connect(target)` and
+throws away the returned `List<String>`. The fix captures + branches on
+the validation outcome.
+
+**Step 1 — Edit `connect_dial.dart` lines 175-192** (the GestureDetector
+onTap handler). Add `go_router` import at top of file (if not already
+present) — current imports listed at lines 20-32; `go_router` is NOT
+imported (only `error_banner.dart` imports it). Add:
+```dart
+import 'package:go_router/go_router.dart';
+```
+
+Replace the empty-config-discarding branch:
+```dart
+} else {
+  // Idle/error → connect using the user's most recent layer
+  // choice (defaults to Mode.direct on first launch).
+  final pigeon.Mode target = ref.read(lastSelectedModeProvider);
+  await ref
+      .read(connectionActionsProvider.notifier)
+      .connect(target);
+}
+```
+
+With:
+```dart
+} else {
+  // Idle/error → connect using the user's most recent layer
+  // choice (defaults to Mode.direct on first launch).
+  final pigeon.Mode target = ref.read(lastSelectedModeProvider);
+  final List<String> issues = await ref
+      .read(connectionActionsProvider.notifier)
+      .connect(target);
+
+  // B-4 / D-07-18 (2026-05-16): per UX-REVIEW.md §2 ¶4 — "should NOT
+  // just fail silently → it should bounce to Settings → Paste from
+  // clipboard with a one-line nudge." Discriminate "config missing"
+  // (the L<N> slot is null — typical first-launch on a build with no
+  // baked defaults, or post-resetAll) from "config malformed" (port
+  // out of range, server addr non-empty but contains ':', etc.). The
+  // validation strings come from
+  // lib/src/services/prowler_config_validation.dart:26-49.
+  //
+  // For "config missing": SnackBar + bounce to /settings (the nudge).
+  // For "config malformed": don't bounce — those are typed in Settings
+  //   already; the existing ErrorBanner path surfaces malformed-config
+  //   PlatformException strings to the user.
+  final bool configMissing = issues
+      .any((String issue) => issue.contains('config missing for'));
+  if (configMissing && mounted) {
+    ScaffoldMessenger.of(context).showSnackBar(
+      const SnackBar(content: Text(Strings.errNoConfigNudge)),
+    );
+    context.go('/settings');
+  }
+}
+```
+
+Note: `mounted` is on `ConsumerState`, which `_ConnectDialState` extends —
+the `mounted` check guards against the rare race where the dial widget is
+disposed between the async connect() and the SnackBar display.
+
+**Step 2 — Create `prowler-client/flutter/test/widget/no_config_nudge_test.dart`.**
+
+Use the Write tool. Pattern mirrors existing connect_dial_test.dart:
+```dart
+// Widget test for B-4 / D-07-18: empty-config dial-tap → SnackBar +
+// /settings navigation.
+//
+// Verifies the wiring per UX-REVIEW.md §2 ¶4 and INVESTIGATION-260516-blockers.md
+// Item 1: when ConnectionActions.connect(mode) returns issues
+// containing 'config missing for', the dial handler surfaces
+// Strings.errNoConfigNudge as a SnackBar and navigates to /settings.
+//
+// Provider-override pattern: stub ConfigRepository.build() to yield an
+// empty ProwlerConfig (no l1/l2/l3 slots) so validate(mode:) returns the
+// canonical 'L<N> config missing for <Mode> mode' string.
+
+import 'package:flutter/material.dart';
+import 'package:flutter_riverpod/flutter_riverpod.dart';
+import 'package:flutter_test/flutter_test.dart';
+import 'package:go_router/go_router.dart';
+
+import 'package:prowler/src/generated/prowler_platform.g.dart' as pigeon;
+import 'package:prowler/src/l10n/strings.dart';
+import 'package:prowler/src/models/app_config.dart';
+import 'package:prowler/src/state/config_repository.dart';
+import 'package:prowler/src/state/connection_state.dart';
+import 'package:prowler/src/widgets/connect_dial.dart';
+
+/// Test-double yielding an empty ProwlerConfig so validate(Mode.direct)
+/// returns 'L1 config missing for Direct mode'.
+class _EmptyConfigRepository extends ConfigRepository {
+  @override
+  Future<ProwlerConfig> build() async =>
+      const ProwlerConfig(l1: null, l2: null, l3: null);
+}
+
+/// Test-double for ConnectionStatus emitting idle.
+class _IdleConnStatus extends ConnectionStatus {
+  @override
+  Stream<pigeon.Status> build() => Stream<pigeon.Status>.value(
+        pigeon.Status(state: pigeon.ConnectionState.idle),
+      );
+}
+
+void main() {
+  testWidgets('Empty-config dial-tap surfaces SnackBar(errNoConfigNudge) '
+      '+ navigates to /settings (B-4 / D-07-18)',
+      (WidgetTester tester) async {
+    String? lastVisitedRoute;
+    final GoRouter router = GoRouter(
+      initialLocation: '/home',
+      routes: <RouteBase>[
+        GoRoute(
+          path: '/home',
+          builder: (BuildContext _, GoRouterState __) => const Scaffold(
+            body: ConnectDial(),
+          ),
+        ),
+        GoRoute(
+          path: '/settings',
+          builder: (BuildContext _, GoRouterState state) {
+            lastVisitedRoute = state.fullPath;
+            return const Scaffold(body: Center(child: Text('Settings stub')));
+          },
+        ),
+      ],
+    );
+
+    await tester.pumpWidget(
+      ProviderScope(
+        overrides: <Override>[
+          configRepositoryProvider.overrideWith(() => _EmptyConfigRepository()),
+          connectionStatusProvider.overrideWith(() => _IdleConnStatus()),
+        ],
+        child: MaterialApp.router(routerConfig: router),
+      ),
+    );
+    await tester.pumpAndSettle();
+
+    // Locate the dial GestureDetector and tap it.
+    await tester.tap(find.byType(ConnectDial));
+    await tester.pumpAndSettle();
+
+    // SnackBar with the nudge text appeared.
+    expect(find.text(Strings.errNoConfigNudge), findsOneWidget);
+    // Navigation went to /settings.
+    expect(lastVisitedRoute, equals('/settings'));
+  });
+}
+```
+
+(Adjust the `_EmptyConfigRepository` shape if `ConfigRepository.build()`
+returns a non-nullable `Future<ProwlerConfig>` with required slots — read
+the `lib/src/state/config_repository.dart` actual signature first and
+match. The intent is: feed a config where `validate(Mode.direct)` returns
+the `L1 config missing for Direct mode` string from
+`prowler_config_validation.dart` line 29.)
+
+**REQ-14 lexicon check:** `errNoConfigNudge` was vetted in Task 3 Step 1.5.
+
+**Per D-07-14 light-touch:** Flutter-lib-only.
+
+**Atomic commit shape:**
+```
+feat(07-13): B-4 no-config first-launch nudge (D-07-18)
+
+* connect_dial.dart dial-tap handler captures
+  ConnectionActions.connect(mode) return value; if any issue contains
+  'config missing for', shows SnackBar(Strings.errNoConfigNudge) +
+  navigates to /settings via context.go.
+
+* New widget test verifies the empty-config path: stubs
+  configRepositoryProvider to yield an empty ProwlerConfig, asserts
+  SnackBar surfaces + go_router navigates to /settings.
+
+Closes UX-REVIEW.md §2 ¶4. Resolves B-4 surfaced in
+INVESTIGATION-260516-blockers.md Item 1.
+```
+  </action>
+  <verify>
+    <automated>
+      bash -c '
+      set -euo pipefail
+      cd /home/parf/projects/work/prowler/prowler-client/flutter
+      # Gate 1: connect_dial.dart captures validation issues + branches on config-missing.
+      grep -q "configMissing" lib/src/widgets/connect_dial.dart
+      grep -q "config missing for" lib/src/widgets/connect_dial.dart
+      # Gate 2: connect_dial.dart navigates to /settings + uses errNoConfigNudge.
+      grep -q "context.go([\x27\x22]/settings[\x27\x22])" lib/src/widgets/connect_dial.dart
+      grep -q "errNoConfigNudge" lib/src/widgets/connect_dial.dart
+      # Gate 3: go_router import added.
+      grep -q "package:go_router/go_router.dart" lib/src/widgets/connect_dial.dart
+      # Gate 4: new widget test file exists + is ≥40 lines.
+      [ -f test/widget/no_config_nudge_test.dart ]
+      [ "$(wc -l < test/widget/no_config_nudge_test.dart)" -ge 40 ]
+      # Gate 5: test runs + passes.
+      flutter test test/widget/no_config_nudge_test.dart --reporter compact
+      # Gate 6: existing connect_dial_test.dart still passes.
+      flutter test test/widget/connect_dial_test.dart --reporter compact
+      # Gate 7: flutter analyze clean.
+      flutter analyze lib/src/widgets/connect_dial.dart test/widget/no_config_nudge_test.dart
+      echo "Task 7 (B-4) gates PASS"
+      '
+    </automated>
+  </verify>
+  <done>
+    `connect_dial.dart` dial-tap handler captures
+    `ConnectionActions.connect(mode)` issues and branches on
+    `config missing for` to fire SnackBar(`errNoConfigNudge`) +
+    `context.go('/settings')`. New widget test
+    `no_config_nudge_test.dart` ≥40 lines, passes, asserts both the
+    SnackBar surfacing AND the go_router navigation. `flutter analyze`
+    clean. Existing widget suite has zero regression.
+  </done>
+</task>
+
+<task type="auto">
+  <name>Task 8 (Wave 6 — §4a a11y): A-1 dial Semantics with state-interpolated label + A-2 info/copy IconButton Semantics + A-3 Servers Reset 48dp touch target. New a11y_semantics_test.dart asserts each.</name>
+  <files>
+    prowler-client/flutter/lib/src/widgets/connect_dial.dart,
+    prowler-client/flutter/lib/src/screens/home/home_screen.dart,
+    prowler-client/flutter/lib/src/screens/logs/logs_screen.dart,
+    prowler-client/flutter/lib/src/widgets/prowl_input.dart,
+    prowler-client/flutter/test/widget/a11y_semantics_test.dart
+  </files>
+  <action>
+**A-1 — Dial Semantics state interpolation.**
+
+Edit `connect_dial.dart` line 172-175. Current:
+```dart
+return Semantics(
+  label: _label(state),
+  button: true,
+```
+Change to:
+```dart
+return Semantics(
+  // A-1 (UX-REVIEW.md §4a): TalkBack reads the dial as a labelled control,
+  // with the current state interpolated so the user hears
+  // "Connect to VPN. Currently Tap to prowl." (idle),
+  // "Connect to VPN. Currently Connecting…." (connecting),
+  // "Connect to VPN. Currently Tunnel up." (connected),
+  // "Connect to VPN. Currently Tap to retry." (error).
+  //
+  // Why include "VPN" in the SEMANTIC label even though REQ-14 forbids it
+  // in user-visible UI: TalkBack labels are functional, not branding. The
+  // user needs to know the control's purpose; "Connect" alone is ambiguous
+  // (connect what?). Per UX-REVIEW §4a A-1 exact phrasing.
+  label: 'Connect to VPN. Currently ${_label(state)}.',
+  button: true,
+```
+
+NOTE the REQ-14 lexicon tension: `VPN` appears in this Semantics label. The
+UX team explicitly specified this string in §4a A-1, and Semantics labels
+are NOT in the REQ-14 forbidden-vocab scan scope (REQ-14 / D-06-23 protect
+USER-VISIBLE UI text; assistive-tech labels are a separate audience and the
+functional clarity wins). Document this carve-out inline (the comment block
+above) so a future REQ-14 enforcer doesn't grep-blow-up.
+
+**A-2 — Info / copy IconButton Semantics labels.**
+
+Edit `home_screen.dart` line 89-103 (info IconButton):
+```dart
+right: IconButton(
+  icon: const Icon(
+    LucideIcons.info,
+    size: 20,
+    color: ProwlerTokens.fog,
+  ),
+  // A-2 (UX-REVIEW.md §4a): explicit tooltip + Semantics label for
+  // TalkBack. The SVG-mask icon button doesn't auto-derive semantics.
+  tooltip: 'About Prowler',
+  onPressed: () => showAboutProwlerSheet(context),
+),
+```
+
+(`IconButton.tooltip` feeds Semantics.label automatically per the
+Material widget contract — verified via the IconButton source comment.
+But for belt-and-suspenders, wrap in a `Semantics` widget if a Flutter
+audit shows tooltip-only doesn't suffice on the target API level. Decide
+by inspecting the test output in Step 4.)
+
+Edit `logs_screen.dart` line 99-108. Current copy IconButton already has
+`tooltip: 'Copy logs to clipboard'` (line 106). Verify it surfaces through
+Semantics by inspecting Semantics.label in the a11y test (Step 4). If
+the test asserts `findsOneWidget` on `Semantics(label: 'Copy logs to
+clipboard')` and fails, ADD an explicit `Semantics(label: 'Copy logs to
+clipboard', child: IconButton(...))` wrap. Otherwise the tooltip suffices.
+
+**A-3 — Servers Reset 48dp touch target.**
+
+Read `prowler-client/flutter/lib/src/widgets/prowl_input.dart` first to
+locate the existing per-field reset icon. The widget exposes
+`onResetPressed: VoidCallback?` (used by ServersScreen) and renders the
+icon when `canReset` is true. The current icon is likely a small
+IconButton with default `iconSize: 24` and the Material defaults make the
+total tap area smaller than 48dp.
+
+**Fix shape (apply within prowl_input.dart at the reset icon render
+site):** wrap the reset icon in either:
+  (a) `IconButton(iconSize: 20, padding: const EdgeInsets.all(14), …)`
+      so total touch target = 20 + 2*14 = 48dp.
+  (b) `SizedBox(width: 48, height: 48, child: <existing icon button>)`
+      if the existing widget is a bare InkResponse with no padding control.
+
+Pick whichever produces the cleanest diff against the current widget's
+shape. Validate via Flutter's `tester.getSize(find.byKey(...))` in the
+a11y test (Step 4 below) that the actual on-screen touch target is ≥48dp.
+
+NOTE the fix lives at the **ProwlInput widget level**, NOT at the
+Servers-screen call sites. This is per CLAUDE.md "extension over
+duplication" — every ProwlInput consumer inherits the touch-target
+compliance, including Settings screen consumers.
+
+**Step 4 — New a11y_semantics_test.dart.**
+
+Use the Write tool to create
+`prowler-client/flutter/test/widget/a11y_semantics_test.dart`:
+
+```dart
+// A11y semantics regression test for §4a A-1, A-2, A-3 (UX-REVIEW.md).
+//
+// Verifies:
+//   * A-1: ConnectDial Semantics.label interpolates the dial state.
+//   * A-2: Home info IconButton + Logs copy IconButton expose Semantics.
+//   * A-3: Per-field reset icon in ProwlInput has ≥48dp touch target.
+
+import 'package:flutter/material.dart';
+import 'package:flutter_riverpod/flutter_riverpod.dart';
+import 'package:flutter_test/flutter_test.dart';
+
+import 'package:prowler/src/generated/prowler_platform.g.dart' as pigeon;
+import 'package:prowler/src/screens/home/home_screen.dart';
+import 'package:prowler/src/screens/logs/logs_screen.dart';
+import 'package:prowler/src/state/connection_state.dart';
+// Adjust provider import to match the actual logs buffer provider
+// declared in logs_screen.dart (or its companion provider file).
+import 'package:prowler/src/state/logs_buffer_provider.dart';
+import 'package:prowler/src/widgets/connect_dial.dart';
+import 'package:prowler/src/widgets/prowl_input.dart';
+
+class _FakeIdleStatus extends ConnectionStatus {
+  @override
+  Stream<pigeon.Status> build() => Stream<pigeon.Status>.value(
+        pigeon.Status(state: pigeon.ConnectionState.idle),
+      );
+}
+
+void main() {
+  testWidgets('A-1: ConnectDial Semantics.label interpolates dial state',
+      (WidgetTester tester) async {
+    await tester.pumpWidget(
+      ProviderScope(
+        overrides: <Override>[
+          connectionStatusProvider.overrideWith(() => _FakeIdleStatus()),
+        ],
+        child: const MaterialApp(
+          home: Scaffold(body: ConnectDial()),
+        ),
+      ),
+    );
+    await tester.pump();
+    await tester.pump(const Duration(milliseconds: 50));
+
+    final SemanticsHandle handle = tester.ensureSemantics();
+    expect(
+      find.bySemanticsLabel('Connect to VPN. Currently Tap to prowl.'),
+      findsOneWidget,
+    );
+    handle.dispose();
+  });
+
+  testWidgets('A-3: ProwlInput reset icon has ≥48dp touch target',
+      (WidgetTester tester) async {
+    await tester.pumpWidget(
+      const MaterialApp(
+        home: Scaffold(
+          body: ProwlInput(
+            label: 'Server address',
+            value: 'edited.example.com',
+            // canReset must be true to render the reset icon.
+            canReset: true,
+            // Sentinel; ProwlInput requires onResetPressed when canReset is true.
+            // (Confirm via the actual ProwlInput contract; adjust if needed.)
+          ),
+        ),
+      ),
+    );
+    await tester.pump();
+
+    // Locate the reset icon button by its semantic role or by a key the
+    // widget exposes. Adjust the finder to match prowl_input.dart's actual
+    // widget tree (likely IconButton with a tooltip "Reset to default" or
+    // similar; inspect the widget first).
+    final Finder resetIcon = find.byTooltip('Reset to default');
+    // If the tooltip doesn't exist, fall back to find.byIcon(LucideIcons.rotateCcw)
+    // or find.byKey(const Key('prowl_input_reset')); plan-time placeholder.
+    expect(resetIcon, findsOneWidget);
+    final Size size = tester.getSize(resetIcon);
+    expect(size.width, greaterThanOrEqualTo(48.0));
+    expect(size.height, greaterThanOrEqualTo(48.0));
+  });
+
+  // ---- A-2 locked test cases (rev-2 WARNING W2 fix) ----
+  // Flutter's IconButton sets Semantics.label automatically from its
+  // `tooltip` parameter — see the IconButton source contract
+  // (`tooltip` is forwarded to a `Tooltip(message: tooltip, …)` wrap,
+  // and `Tooltip` injects the message string into `Semantics.label` via
+  // `Semantics(label: message, child: …)`). This means
+  // `find.bySemanticsLabel('About Prowler')` works WITHOUT an explicit
+  // `Semantics(label: …)` wrap as long as the tooltip is set on the
+  // IconButton itself. No "deferred to executor" decision needed.
+  //
+  // Pre-write both A-2 test cases here. If either fires, the tooltip is
+  // missing OR the tooltip was rewritten without a synchronized test
+  // update — both are regression signals worth catching at CI time.
+
+  testWidgets('A-2: Home info IconButton exposes Semantics.label '
+      'from its tooltip (rev-2 WARNING W2 locked test)',
+      (WidgetTester tester) async {
+    await tester.pumpWidget(
+      ProviderScope(
+        overrides: <Override>[
+          connectionStatusProvider.overrideWith(() => _FakeIdleStatus()),
+        ],
+        child: const MaterialApp(
+          home: Scaffold(body: HomeScreen()),   // mounts the TopBar IconButton
+        ),
+      ),
+    );
+    await tester.pump();
+    await tester.pump(const Duration(milliseconds: 50));
+
+    final SemanticsHandle handle = tester.ensureSemantics();
+    expect(
+      find.bySemanticsLabel('About Prowler'),
+      findsOneWidget,
+      reason: 'Home TopBar info IconButton must expose Semantics.label '
+              '\x27About Prowler\x27 via its tooltip parameter '
+              '(IconButton.tooltip → Tooltip → Semantics.label, automatic).',
+    );
+    handle.dispose();
+  });
+
+  testWidgets('A-2: Logs copy IconButton exposes Semantics.label '
+      'from its tooltip (rev-2 WARNING W2 locked test)',
+      (WidgetTester tester) async {
+    // LogsScreen consumes `logsAsyncBufferProvider` (or equivalent — read
+    // logs_screen.dart for the actual provider name). Override it to yield
+    // a single-line LogLine list so the IconButton is enabled.
+    await tester.pumpWidget(
+      ProviderScope(
+        overrides: <Override>[
+          // Stub the logs buffer so the copy IconButton is enabled
+          // (onPressed != null). Adjust provider name to match
+          // lib/src/screens/logs/logs_screen.dart line 97-99 actual.
+          logsBufferProvider.overrideWith(
+            (Ref ref) => Future<List<pigeon.LogLine>>.value(
+              <pigeon.LogLine>[pigeon.LogLine(message: 'stub', timestampMs: 0)],
+            ),
+          ),
+        ],
+        child: const MaterialApp(home: Scaffold(body: LogsScreen())),
+      ),
+    );
+    await tester.pumpAndSettle();
+
+    final SemanticsHandle handle = tester.ensureSemantics();
+    expect(
+      find.bySemanticsLabel('Copy logs to clipboard'),
+      findsOneWidget,
+      reason: 'Logs copy IconButton must expose Semantics.label \x27Copy logs '
+              'to clipboard\x27 via its tooltip parameter (already present '
+              'per logs_screen.dart line 106; this test guards against future '
+              'tooltip removal).',
+    );
+    handle.dispose();
+  });
+}
+```
+
+(Adjust finders/contracts as the actual widget exposes — the test scaffold
+above is the structural target; executor refines based on what
+`prowl_input.dart`'s reset-icon contract surfaces.)
+
+**REQ-14 lexicon check:** the dial Semantics.label intentionally carries
+`VPN` per UX team's exact A-1 phrasing. Documented carve-out inline; not a
+forbidden-vocab regression because Semantics labels are an
+assistive-technology audience separate from REQ-14's user-visible UI
+scope.
+
+**Per D-07-14 light-touch:** Flutter-lib-only.
+
+**Atomic commit shape:**
+```
+feat(07-13): §4a a11y must-fixes — A-1 dial Semantics + A-2 IconButton
+             labels + A-3 ProwlInput 48dp reset touch target
+
+* ConnectDial Semantics.label interpolates the current dial state per
+  UX-REVIEW.md §4a A-1; REQ-14 VPN-lexicon carve-out documented inline
+  (Semantics labels are a-tech audience, not user-visible UI scope).
+
+* Home info IconButton + Logs copy IconButton expose tooltip + (optional)
+  explicit Semantics wrap per A-2.
+
+* ProwlInput reset icon wrapped to ≥48dp touch target per A-3 (Material
+  minimum). Fix at widget level so every ProwlInput consumer inherits.
+
+* New a11y_semantics_test.dart asserts A-1 label interpolation, A-2
+  Home info + Logs copy IconButton Semantics.label (sourced from
+  IconButton.tooltip per Flutter source contract — rev-2 WARNING W2
+  locked test cases), and A-3 ProwlInput touch-target ≥48dp.
+```
+  </action>
+  <verify>
+    <automated>
+      bash -c '
+      set -euo pipefail
+      cd /home/parf/projects/work/prowler/prowler-client/flutter
+      # Gate 1: A-1 dial Semantics label interpolates state.
+      grep -q "Connect to VPN. Currently " lib/src/widgets/connect_dial.dart
+      # Gate 2: A-2 info IconButton has tooltip.
+      grep -q "tooltip: [\x27\x22]About Prowler[\x27\x22]" lib/src/screens/home/home_screen.dart
+      # Gate 3: A-2 copy IconButton already had tooltip (preserved).
+      grep -q "tooltip: [\x27\x22]Copy logs to clipboard[\x27\x22]" lib/src/screens/logs/logs_screen.dart
+      # Gate 3a (rev-2 WARNING W2): locked A-2 Semantics-label tests assert findsOneWidget.
+      grep -q "bySemanticsLabel([\x27\x22]About Prowler[\x27\x22])" test/widget/a11y_semantics_test.dart
+      grep -q "bySemanticsLabel([\x27\x22]Copy logs to clipboard[\x27\x22])" test/widget/a11y_semantics_test.dart
+      # Gate 4: A-3 — ProwlInput reset icon path was touched (look for new padding/size markers).
+      grep -qE "(EdgeInsets.all\\(14\\)|SizedBox\\(width: 48, height: 48|iconSize: 20)" lib/src/widgets/prowl_input.dart
+      # Gate 5: new a11y test file exists + passes.
+      [ -f test/widget/a11y_semantics_test.dart ]
+      [ "$(wc -l < test/widget/a11y_semantics_test.dart)" -ge 30 ]
+      flutter test test/widget/a11y_semantics_test.dart --reporter compact
+      # Gate 6: full widget suite still passes (no regression).
+      flutter test test/widget/ --reporter compact
+      # Gate 7: flutter analyze clean.
+      flutter analyze lib/src/widgets/connect_dial.dart lib/src/screens/home/home_screen.dart \
+        lib/src/screens/logs/logs_screen.dart lib/src/widgets/prowl_input.dart \
+        test/widget/a11y_semantics_test.dart
+      echo "Task 8 (§4a a11y) gates PASS"
+      '
+    </automated>
+  </verify>
+  <done>
+    A-1: ConnectDial Semantics.label interpolates `Connect to VPN.
+    Currently ${state}.` with VPN-lexicon carve-out documented inline.
+    A-2: Home info IconButton + Logs copy IconButton carry tooltip;
+    `find.bySemanticsLabel(\x27About Prowler\x27)` and
+    `find.bySemanticsLabel(\x27Copy logs to clipboard\x27)` BOTH
+    `findsOneWidget` (rev-2 WARNING W2: locked tests, no executor
+    decision deferred — Flutter IconButton.tooltip forwards through
+    Tooltip.Semantics.label automatically). A-3: ProwlInput reset icon
+    wrapped to ≥48dp touch target. New `a11y_semantics_test.dart`
+    contains FOUR testWidgets cases (A-1 + 2× A-2 + A-3). `flutter test`
+    + `flutter analyze` clean.
+  </done>
+</task>
+
+<task type="auto">
+  <name>Task 9 (Wave 7a — B-1 PING composition): Compose copy-paste-ready PING.md for design-system team requesting redline v3 amendment for horizon-sliver halo composition reset</name>
+  <files>.planning/phases/07-design-system-polish/designer-delivery-5-redline-v3-ping/PING.md</files>
+  <action>
+**Per D-07-15 (locked):** B-1 fix path is spec-amendment-FIRST, then
+implementation. The implementation BLOCKS on the design-system team
+returning a redline v3 amendment. This task composes the PING body.
+The next task (Task 10) is the autonomous:false checkpoint where user ships
+the ping + waits for the response.
+
+Create the directory + file via the Write tool.
+
+**Content (target ≥60 lines, copy-paste-ready markdown).** Use the Write
+tool at
+`.planning/phases/07-design-system-polish/designer-delivery-5-redline-v3-ping/PING.md`.
+
+```markdown
+# Redline v3 amendment request — horizon-sliver halo composition
+
+**To:** Design-system team
+**From:** Prowler engineering
+**Date:** 2026-05-16
+**Context:** Phase 7 v0.7.0 ship gate; UX team's conditional sign-off
+
+## What we shipped
+
+The HorizonSliver widget per HORIZON-SLIVER-REDLINE.html (redline v2):
+- Sliver: 160dp tall
+- Horizon line: y=112dp
+- Sun: ⌀360dp radial gradient (pink → amber → yellow), centered on the horizon
+- Sun opacity: 0.35 baseline → 0.42 pulse peak (6s ambient loop)
+- Floor lines: 7 receding-perspective at 0.55–0.22 alpha
+- Implementation: `prowler-client/flutter/lib/src/widgets/horizon_sliver.dart`
+
+Per-component compliance with the v2 redline was verified by the Phase 7
+audit (07-DESIGN-FIDELITY-AUDIT.md, H-1 closed) and the 07-04
+horizon_sliver_test widget suite (100/100 pass).
+
+## What UX team flagged (UX-REVIEW.md §7 Blocker B-1)
+
+Reviewing the live Home screen render
+(`designer-delivery-4-ux-team-review/screenshots/02-home-screen.png`), the
+UX team observed:
+
+> Horizon-sliver halo on Home eats 30% of viewport. Scale it down per
+> design-system spec.
+
+The per-component geometry is on-spec — the issue is **compositional**.
+On the Home screen the sliver's pink dominance compounds with two adjacent
+sources:
+1. The ConnectDial cat-silhouette pink drop-shadow halo (~120dp, radius
+   12dp BoxShadow, pink @ alpha 0.4) at `connect_dial.dart:229-233`
+2. The dark-midnight background (`#0B0420`) which boosts the perceived
+   contrast of every pink element
+
+The combined "pink load" on Home is ~30% viewport per UX team's measurement
+— above the design-system's intended Home-screen contrast hierarchy
+(dial = primary; sliver = ambient backdrop).
+
+## What we need from design-system
+
+A **redline v3 amendment** to HORIZON-SLIVER-REDLINE.html that resets the
+sliver's contribution to the Home composition. Three potential dimensions
+to amend (your call which combination):
+
+**Dimension A — Sun opacity floor + peak.** Current v2: `0.35` baseline →
+`0.42` peak. Investigation suggests a ~50% perceptual reduction (e.g.
+`0.20` → `0.28`) preserves the breathing motion while ceding chroma to the
+dial. ~2 LOC change (`_pulseOpacityMin` + `_pulseOpacityMax` const updates).
+
+**Dimension B — Sun diameter.** Current v2: ⌀360dp. Reducing to ⌀240dp
+shrinks the half-disc area by ~56% with no opacity change. ~1 LOC change
+(`_sunDiameter` const update).
+
+**Dimension C — Sliver geometry.** Current v2: 160dp tall, horizon at
+y=112dp. Reducing to 120dp tall (horizon at y=84dp) reclaims ~25% viewport.
+~2 LOC change (`_sliverHeight` + `_horizonY` proportional updates).
+
+We can implement ANY combination (A only / A+B / A+B+C / etc.) — but we
+need the amendment to come from you so the spec→impl chain stays clean.
+Per Phase 7's process rule (D-07-15, locked): impl deviates only after
+the spec lands.
+
+## What we are NOT asking
+
+- We're NOT asking design-system to redesign the sliver from scratch — the
+  v2 redline is conceptually correct, only the magnitudes need a reset for
+  the Home-screen composition.
+- We're NOT asking to change the ConnectDial halo (`connect_dial.dart:229-233`)
+  in the same amendment — the dial halo is its own spec'd element and a
+  Home-composition fix that touches both feels scope-creepy. If the
+  sliver-only amendment doesn't resolve the 30% viewport pink load, we
+  re-engage on the dial halo separately.
+
+## What we ask back
+
+Either:
+1. An amended `HORIZON-SLIVER-REDLINE-v3.html` (or inline-updated v2 with a
+   "v3 amendment" delta section) carrying the new const values for
+   whichever dimension(s) you choose.
+2. A short note that the v2 geometry is canonical and the Home composition
+   should be reworked elsewhere (in which case we re-engage with a follow-up
+   ping covering the dial halo + bg darkening levers).
+
+**Target turnaround:** v0.7.0 ship target is end-of-week 2026-05-22; PING
+sent 2026-05-16 (Friday) — a Monday or Tuesday response keeps us on
+schedule.
+
+## Files to reference
+
+- `prowler-client/docs/design-system/HORIZON-SLIVER-REDLINE.html` (v2
+  canonical redline)
+- `prowler-client/flutter/lib/src/widgets/horizon_sliver.dart` (current
+  on-spec implementation; lines 44-55 hold the const values that the
+  amendment would update)
+- `designer-delivery-4-ux-team-review/screenshots/02-home-screen.png`
+  (the screenshot UX team reviewed)
+- `designer-delivery-4-ux-team-review/UX-REVIEW.md` §7 (Blocker B-1)
+- `INVESTIGATION-260516-blockers.md` Item 2 (engineering investigation +
+  proposed fix levers)
+
+Reply with redline v3 (or v2-amendment delta) when ready.
+
+— Prowler engineering
+```
+
+**No code changes in this task.** Pure markdown composition.
+  </action>
+  <verify>
+    <automated>
+      bash -c '
+      set -euo pipefail
+      cd /home/parf/projects/work/prowler
+      # Gate 1: PING.md exists + is ≥60 lines.
+      [ -f .planning/phases/07-design-system-polish/designer-delivery-5-redline-v3-ping/PING.md ]
+      [ "$(wc -l < .planning/phases/07-design-system-polish/designer-delivery-5-redline-v3-ping/PING.md)" -ge 60 ]
+      # Gate 2: PING references HORIZON-SLIVER-REDLINE.
+      grep -q "HORIZON-SLIVER-REDLINE" .planning/phases/07-design-system-polish/designer-delivery-5-redline-v3-ping/PING.md
+      # Gate 3: PING references B-1 + the three proposed amendment dimensions A/B/C.
+      grep -q "Blocker B-1\|Bug-1\|B-1" .planning/phases/07-design-system-polish/designer-delivery-5-redline-v3-ping/PING.md
+      grep -q "Dimension A\|Dimension B\|Dimension C" .planning/phases/07-design-system-polish/designer-delivery-5-redline-v3-ping/PING.md
+      echo "Task 9 (B-1 PING composition) gates PASS"
+      '
+    </automated>
+  </verify>
+  <done>
+    `.planning/phases/07-design-system-polish/designer-delivery-5-redline-v3-ping/PING.md`
+    exists, ≥60 lines, references HORIZON-SLIVER-REDLINE, B-1, and the
+    three proposed amendment dimensions. Copy-paste-ready for user to ship
+    to design-system team.
+  </done>
+</task>
+
+<task type="checkpoint:human-action" gate="blocking">
+  <name>Task 10 (Wave 7b — autonomous:false — async-blocker handoff): User reviews PING.md, ships to design-system team, awaits redline v3 amendment, then re-dispatches a follow-up plan to implement against amendment</name>
+  <files>.planning/phases/07-design-system-polish/designer-delivery-5-redline-v3-ping/PING.md</files>
+  <action>
+**This is the B-1 async-blocker handoff.** Per D-07-15 (locked):
+implementation BLOCKS on design-system team's redline v3 amendment. The
+v0.7.0 ship can proceed for the other 7 items WITHOUT B-1 (see Wave 8a
+"tactical close"); Phase 7 FULL close (Wave 8b) blocks on B-1
+amendment + implementation landing.
+
+**Operator action:**
+
+1. **Review** the PING body at
+   `.planning/phases/07-design-system-polish/designer-delivery-5-redline-v3-ping/PING.md`
+   (composed in Task 9). Edit voice/tone if needed; the content is
+   technically locked but the relationship voice is yours.
+
+2. **Ship** the PING to the design-system team via your preferred channel
+   (Figma comment / Slack / email / etc.). The PING body is markdown so it
+   pastes cleanly into any rich-text channel.
+
+3. **Continue with v0.7.0 ship in parallel.** Do not block on the
+   amendment — Waves 1-6 + Task 9's PING composition all land BEFORE this
+   checkpoint. Wave 8a's "tactical close" (UX team v4.1 re-shoot covering
+   the 7 non-B-1 items) can proceed; the v0.7.0 build is releasable for
+   those 7 items.
+
+4. **When design-system responds** with redline v3 (or v2-amendment delta):
+   - Save the amendment artifact (HTML or markdown delta) into
+     `.planning/phases/07-design-system-polish/designer-delivery-5-redline-v3-ping/`
+     alongside this PING.md (e.g. `HORIZON-SLIVER-REDLINE-v3.html` or
+     `REDLINE-V3-AMENDMENT.md`).
+   - Dispatch a follow-up `/gsd-plan-phase 07 --gaps` invocation to plan
+     B-1 implementation against the amendment. Likely shape: ~2-4 const
+     changes in `horizon_sliver.dart` (the dimensions A/B/C levers from
+     PING.md) + a re-run of the 07-04 horizon_sliver_test suite + a Wave
+     8b v4.2 re-shoot of the Home screen for UX team's full sign-off.
+
+5. **If design-system declines** the sliver-only amendment (per PING
+   "What we ask back" branch 2): re-engage with a follow-up ping covering
+   the dial halo + bg darkening levers; plan B-1 against THAT amendment
+   instead.
+
+**Resume signal:** type `tactical-ship` to proceed to Wave 8a (the 7-item
+tactical close) without waiting for B-1; OR type `await-amendment` if you
+prefer to hold ALL v0.7.0 work until design-system responds (NOT
+recommended per D-07-15 — the other 7 items unblock Phase 8 Windows per
+UX-REVIEW §7).
+
+Decision rationale to capture in your reply: if you go `tactical-ship`,
+Phase 7 will close in TWO waves — Wave 8a (now-ish, 7-of-8 items signed
+off) and Wave 8b (post-B-1, full close + ROADMAP/STATE flip). If you go
+`await-amendment`, Phase 7 closes once in Wave 8b only.
+  </action>
+  <verify>
+    <automated>
+      bash -c '
+      # Operator-side gate — the PING is staged; user does the human-only
+      # action (sending to design-system team and awaiting response).
+      [ -f /home/parf/projects/work/prowler/.planning/phases/07-design-system-polish/designer-delivery-5-redline-v3-ping/PING.md ] || { echo "MISSING PING.md"; exit 1; }
+      echo "Task 10 (B-1 async-blocker handoff) PING staged — awaiting operator decision (tactical-ship vs await-amendment)"
+      '
+    </automated>
+  </verify>
+  <done>
+    Operator has reviewed + shipped the PING.md to the design-system team
+    AND replied with `tactical-ship` (proceed to Wave 8a without B-1) or
+    `await-amendment` (hold all close-time work until B-1 lands).
+  </done>
+</task>
+
+<task type="checkpoint:human-verify" gate="blocking">
+  <name>Task 11 (Wave 8a — tactical close — v4.1 re-shoot UX team confirmation): Re-shoot v4.1 bundle covering only screens affected by Waves 1-6 (02-home, 02e-home-dial-connected, 02d-home-dial-error triggered via B-3, 04-/04b-/04c-servers), UX team confirms 7-of-8 blockers resolved</name>
+  <files>
+    .planning/phases/07-design-system-polish/designer-delivery-6-ux-team-v4.1-reshoot/
+  </files>
+  <action>
+**Wave 8a fires AFTER Waves 1-6 land + Wave 7 PING is shipped (Task 10
+resume=`tactical-ship`).** Wave 8a does NOT block on B-1; that's Wave 8b.
+
+**Step 1 — Build v0.7.0 multi-ABI APK.** Bump pubspec `version:` to
+`0.7.0+11` (semver minor bump per the 11 plans + 8 items closure); run
+`flutter pub get` to propagate to local.properties (per 07-12 lesson at
+Step 1.5); rebuild via `tools/build-release-apk.sh`. Output:
+`~/prowler-debug-v0.7.0-multiabi.apk`. Capture SHA.
+
+```bash
+cd /home/parf/projects/work/prowler/prowler-client/flutter && \
+  sed -i 's/^version: .*/version: 0.7.0+11/' pubspec.yaml && \
+  flutter pub get
+cd /home/parf/projects/work/prowler && \
+  ./tools/build-release-apk.sh
+sha256sum ~/prowler-debug-v0.7.0-multiabi.apk
+```
+
+**Step 2 — Install on emulator-5554 + cold-launch re-shoot.**
+
+```bash
+adb -s emulator-5554 uninstall com.prowler.client 2>/dev/null || true
+adb -s emulator-5554 install -r ~/prowler-debug-v0.7.0-multiabi.apk
+mkdir -p /home/parf/projects/work/prowler/.planning/phases/07-design-system-polish/designer-delivery-6-ux-team-v4.1-reshoot
+```
+
+**Step 3 — Capture the v4.1 bundle (only the screens affected by Waves 1-6).**
+
+Per UX-REVIEW.md §6 "Untriggered states" + the v0.7.0 item-to-screen
+mapping:
+
+| Screen capture                  | UX item it proves                                          |
+|---------------------------------|------------------------------------------------------------|
+| 02-home-screen.png              | §1 (no Home title), §2 splash hold (cold-launch frames)    |
+| 02e-home-dial-connected.png     | B-2 (empty-value suppression), §3 row 4 (`direct` value)   |
+| 02d-home-dial-error.png         | B-3 (silently triggered via a bogus-config flow)           |
+| 04-servers-screen.png           | §3 row 5 (`One server per layer.` subtitle)                |
+| 04b-servers-expanded.png        | A-3 (Reset 48dp touch target — visible on expanded panels) |
+| 04c-servers-collapsed.png       | (regression — collapsed view unchanged from v4)            |
+| cold-launch frames 00..08       | §2 splash hold ≤ 1000ms wall-time validation               |
+
+Capture each via:
+```bash
+adb -s emulator-5554 shell screencap -p /sdcard/02-home-screen.png && \
+  adb -s emulator-5554 pull /sdcard/02-home-screen.png \
+    /home/parf/projects/work/prowler/.planning/phases/07-design-system-polish/designer-delivery-6-ux-team-v4.1-reshoot/02-home-screen.png
+```
+(Repeat for each.)
+
+To trigger 02d-home-dial-error: temporarily seed an invalid config (e.g.
+`l1.serverAddr = "192.0.2.1"` — TEST-NET-1, never routable), tap dial,
+wait for xray retry exhaustion, capture the error-banner-present frame.
+Per Wave 4 widget test, the error frame now latches; capture is
+reproducible.
+
+**Teardown after 02d capture (rev-3 INFO#2 fix — required to prevent bogus
+config bleeding into 02e capture or post-task AVD state).** Once the 02d
+screencap pulls, restore the baked-default L1 config:
+
+```bash
+# Restore baked-default L1 config (post-02d capture — rev-3 INFO#2)
+# The overrides.json file under the app's internal storage is the lever
+# config_repository.dart reads first; deleting it forces re-read of the
+# baked defaults from assets/config-defaults.json.
+adb -s emulator-5554 shell run-as com.prowler.client \
+  rm files/prowler/overrides.json 2>&1 | tail -1
+# Cold-restart so the in-memory ConfigRepository picks up the deletion.
+adb -s emulator-5554 shell am force-stop com.prowler.client
+adb -s emulator-5554 shell am start \
+  -n com.prowler.client/com.prowler.client.MainActivity
+# Confirm the restore: dial should idle, config screen should show the
+# baked vless:// values (not the TEST-NET-1 192.0.2.1 placeholder).
+echo "Config restored to baked defaults (overrides.json removed; app cold-restarted)"
+```
+
+If `run-as` fails with permission denied (e.g. release build, non-debuggable
+APK), fall back to `adb shell pm clear com.prowler.client` (nuclear option:
+wipes app data entirely; user must re-grant VPN consent on next launch).
+The Wave 8a APK is built debug-multiabi per Step 1, so `run-as` succeeds.
+
+To trigger 02e-home-dial-connected with null exitCode + null latencyMs
+(the B-2 regression-test case): if the baked default config connects with
+populated exitCode/latency, the B-2 fix's no-bug case won't reproduce —
+instead capture a vanilla connected frame (exitCode + latency POPULATED)
+to demonstrate the row reads cleanly (`exit US · 87 ms` or similar), not
+literally `exit · ms`.
+
+**Step 4 — Visual Read-tool sanity inspection (per memory
+`feedback_validate_artifacts_before_human_handoff`).**
+
+Open each captured PNG via the Read tool and confirm:
+- 02-home: no "Home" title visible, PROWLER eyebrow + info icon present
+- 02e-home-dial-connected: meta row has values (no literal `exit · ms`),
+  EXIT chip shows `direct` or country code (not `—`)
+- 02d-home-dial-error: ErrorBanner visible carrying `Connection failed.`
+  + `We tried 3 times. Switch layer or check your network.`
+- 04-servers: subtitle reads `One server per layer.`
+- 04b-servers-expanded: each Reset arrow visibly ≥48dp tap area
+
+If any capture fails the visual sanity check, the fix didn't land in
+the build — stop and re-run the offending Wave 1-6 task.
+
+**Step 4b — Splash hold empirical measurement (rev-2 WARNING W4 — B-2
+verify gate, falsifiable per UX-REVIEW.md §2 ≤ 1000ms ceiling).**
+
+Pre-written script (run from the host shell with AVD attached). The
+Android-12 SplashScreen API logs a `Displayed com.prowler.client/...:
++<N>ms` line on Activity-ready; that's the wall-clock from launcher-tap
+to first-frame. The script clears logcat, force-stops the app, cold-
+launches the MainActivity, then parses the Displayed line and compares
+against the 1000ms ceiling.
+
+```bash
+# Splash hold measurement (B-2 verify gate — rev-2 WARNING W4 falsifiable)
+adb -s emulator-5554 shell logcat -c
+adb -s emulator-5554 shell am force-stop com.prowler.client
+adb -s emulator-5554 shell am start -n com.prowler.client/com.prowler.client.MainActivity
+sleep 5
+ms=$(adb -s emulator-5554 shell logcat -d | \
+       grep -oE 'Displayed com.prowler.client/.*: \+[0-9]+ms' | \
+       head -1 | grep -oE '[0-9]+' | head -1)
+if [ -z "$ms" ]; then
+  echo "FAIL (rev-2 WARNING W4): no Displayed line found in logcat — Activity may not have launched cleanly"
+  exit 1
+fi
+if [ "$ms" -gt 1000 ]; then
+  echo "FAIL (rev-2 WARNING W4): splash hold ${ms}ms exceeds 1000ms ceiling (UX-REVIEW.md §2)"
+  exit 1
+fi
+echo "PASS (rev-2 WARNING W4): splash hold ${ms}ms (≤ 1000ms target — aspiration 800ms per Task 2 windowSplashScreenAnimationDuration)"
+# Capture the measured ms for the RESHOOT-SUMMARY.md splash-hold line (Step 5).
+echo "$ms" > /tmp/splash-hold-ms.txt
+```
+
+The measured value lands in `/tmp/splash-hold-ms.txt` for Step 5 to
+embed in `RESHOOT-SUMMARY.md`. If the value > 1000ms, stop and
+investigate (likely Task 2's `windowSplashScreenAnimationDuration: 800`
+didn't merge to the APK; rebuild + retry).
+
+**Step 5 — Compose the UX-team-v4.1-reshoot summary letter.**
+
+Use the Write tool at
+`.planning/phases/07-design-system-polish/designer-delivery-6-ux-team-v4.1-reshoot/RESHOOT-SUMMARY.md`
+with sections:
+- Build SHA + version
+- Item-by-item closure: B-2, B-3, §1, §2, §3, §4a (A-1/A-2/A-3) + B-4
+  (each links to the screencap that proves resolution)
+- Outstanding: B-1 (awaiting redline v3 amendment per D-07-15 + PING in
+  designer-delivery-5)
+- Splash hold measurement (rev-2 WARNING W4): cold-launch
+  `Displayed com.prowler.client/...: +<N>ms` from logcat ≤ 1000ms. Embed
+  the actual measured value from `/tmp/splash-hold-ms.txt` (written by
+  Step 4b) into the summary so the UX team sees the empirical number,
+  not just a "passed" assertion. Format suggestion:
+  `Splash hold: <N>ms (target 800ms, ceiling 1000ms — PASS)`.
+- Ask: UX team unconditional sign-off on the 7 items closed; B-1 carried
+  as remaining v0.7.0 blocker pending design-system response
+
+**Step 6 — Ship the bundle to UX team via the same channel as v4** (the
+designer-delivery-4-ux-team-review was the precedent; replicate it).
+
+**Operator gate:** confirm UX team has signed off on the 7-of-8 items.
+
+If UX team unconditional → proceed to Wave 8b ONLY AFTER B-1 lands; if
+the conditional-sign-off on the 7 items is the operator's tolerance for
+tactical-close-without-Phase-7-flipping, that's also acceptable; OR if
+B-1 amendment lands in parallel (per Wave 7 handoff), Wave 8b can fire
+immediately after Wave 8a's UX-team confirmation.
+
+If UX team flags new issues on v4.1 → those are NEW gaps, NOT this
+plan's responsibility; dispatch a follow-up gap-closure plan
+`/gsd-plan-phase 07 --gaps`.
+
+**Resume signal:** type `7-of-8 confirmed, awaiting B-1` (default — Wave 8b
+fires after B-1 lands) OR `unconditional sign-off, B-1 deferred to v0.7.1`
+(operator scopes B-1 out of Phase 7 close — requires updating D-07-15 in
+CONTEXT.md to reflect the scope cut).
+  </action>
+  <verify>
+    <automated>
+      bash -c '
+      set -euo pipefail
+      cd /home/parf/projects/work/prowler
+      # Gate 1: v0.7.0 APK exists.
+      ls -la ~/prowler-debug-v0.7.0-multiabi.apk
+      # Gate 1b (rev-2 WARNING W4): splash hold measurement landed and passed.
+      [ -f /tmp/splash-hold-ms.txt ] || { echo "FAIL: splash hold not measured (Step 4b script missing)"; exit 1; }
+      splash_ms=$(cat /tmp/splash-hold-ms.txt)
+      [ "$splash_ms" -le 1000 ] || { echo "FAIL: splash hold ${splash_ms}ms > 1000ms ceiling"; exit 1; }
+      echo "Wave 8a splash hold = ${splash_ms}ms (≤ 1000ms — PASS)"
+
+      # Gate 2: re-shoot bundle directory carries the 6 expected captures + the summary letter.
+      DIR=.planning/phases/07-design-system-polish/designer-delivery-6-ux-team-v4.1-reshoot
+      [ -f "$DIR/02-home-screen.png" ]
+      [ -f "$DIR/02e-home-dial-connected.png" ]
+      [ -f "$DIR/02d-home-dial-error.png" ]
+      [ -f "$DIR/04-servers-screen.png" ]
+      [ -f "$DIR/04b-servers-expanded.png" ]
+      [ -f "$DIR/RESHOOT-SUMMARY.md" ]
+      # Gate 3: pubspec bumped to 0.7.0+11.
+      grep -q "^version: 0.7.0+11$" prowler-client/flutter/pubspec.yaml
+      grep -q "^flutter\.versionName=0.7.0$" prowler-client/flutter/android/local.properties
+      echo "Task 11 (Wave 8a tactical close gates PASS — awaiting UX team confirmation)"
+      '
+    </automated>
+  </verify>
+  <done>
+    v0.7.0+11 multi-ABI APK built + installed on emulator-5554. v4.1
+    re-shoot bundle captured into
+    `designer-delivery-6-ux-team-v4.1-reshoot/` with the 6 required
+    screencaps + cold-launch frames + RESHOOT-SUMMARY.md. UX team has
+    confirmed 7-of-8 items closed (B-1 carried per Wave 7 handoff).
+    Operator signals next path via `7-of-8 confirmed, awaiting B-1` or
+    `unconditional sign-off, B-1 deferred to v0.7.1`.
+  </done>
+</task>
+
+<task type="checkpoint:human-verify" gate="blocking">
+  <name>Task 12 (Wave 8b — full Phase 7 close): After B-1 amendment lands + B-1 implementation merges + v4.2 UX-team unconditional sign-off, write 07-07-SUMMARY.md + 07-13-SUMMARY.md, flip ROADMAP 07-07/07-12/07-13 to [x], update STATE.md progress 36→40 (full close; +1 W3 recount + 3 closures) — or 36→38 at tactical close (Wave 8a) if operator elects to ship before B-1 lands / percent advance. Phase 7 closes.</name>
+  <files>
+    .planning/phases/07-design-system-polish/07-07-SUMMARY.md,
+    .planning/phases/07-design-system-polish/07-13-SUMMARY.md,
+    .planning/ROADMAP.md,
+    .planning/STATE.md
+  </files>
+  <action>
+**Wave 8b fires AFTER:**
+1. Wave 7 produced redline v3 amendment (Task 10 handoff resolved).
+2. A follow-up plan implemented B-1 against the amendment (likely 2-4 const
+   changes in `horizon_sliver.dart` + horizon_sliver_test re-run).
+3. v0.7.0+12 (or whatever version the B-1 follow-up lands) rebuilt + UX
+   team v4.2 re-shoot covering the Home screen with B-1 fix applied.
+4. UX team UNCONDITIONAL sign-off received (no carry-overs).
+
+**Step 1 — Write 07-07-SUMMARY.md.**
+
+Plan 07-07 (Designer-asset integration) has been `[ ]` since 2026-05-15 (per
+the partial-deferred note on 07-12-PLAN.md). The v0.7.0 ship completes the
+designer-asset integration loop (cat launcher icon ✓, branded splash ✓,
+splash font-handoff ✓ via 07-12, mascot/caption decision ✓, android:label
+✓ — all already delivered; Task 12's role is to formally summary-up the
+close).
+
+Use Write tool at `.planning/phases/07-design-system-polish/07-07-SUMMARY.md`
+following `$HOME/.claude/get-shit-done/templates/summary.md`. Include:
+- 07-07 closure record (designer assets integrated per D-07-13 sign-off)
+- v0.7.0 build SHA + version
+- Links to designer-delivery-3 (launcher icon + splash) + designer-delivery-4-ux-team-review
+  (UX team conditional sign-off) + designer-delivery-5 (B-1 redline v3 ping) +
+  designer-delivery-6 (v4.1 re-shoot) + designer-delivery-7 (v4.2 re-shoot
+  post-B-1)
+- AP-4 exception cross-link (D-07-16 / .planning/debug/AP4-EXCEPTION-D-07-16-*.md)
+- Cross-references to 07-13-PLAN.md as the closure mechanism
+
+**Step 2 — Write 07-13-SUMMARY.md.**
+
+Use Write tool at `.planning/phases/07-design-system-polish/07-13-SUMMARY.md`.
+Include:
+- 8-item closure: B-1, B-2, B-3, §1, §2, §3, §4a (A-1/A-2/A-3), B-4
+- AP-4 exception (D-07-16) summary + risk-register retrospective (any
+  observed regressions post-merge? if none, document the null result)
+- Pigeon enum expansion (D-07-17): connectFailed enum case wired Kotlin→Dart
+  cleanly; zero downstream breakage in existing template-mapping tests
+- Test count (rev-2 WARNING W5 reframed — falsifiable via grep, not a
+  static "120→125" claim):
+  * Two new test files: `no_config_nudge_test.dart`,
+    `a11y_semantics_test.dart`.
+  * Nine new `testWidgets` cases across the suite:
+      1. Task 4 B-2 (connect_dial — connected with null exitCode + null
+         latencyMs renders no buggy literal)
+      2. Task 6 B-3 (error_banner — connectFailed template renders
+         Connection failed. heading + Retry + Switch layer)
+      3. Task 6 B-3 (connect_dial Case A — [connecting, error] latches
+         DialState.error)
+      4. Task 6 rev-2 BLOCKER B1 (connect_dial Case B —
+         [connecting, error, idle] STILL latches via Dart-side latch
+         REGRESSION GATE)
+      5. Task 7 B-4 (no_config_nudge — empty config dial-tap surfaces
+         SnackBar + /settings nav)
+      6. Task 8 A-1 (a11y — ConnectDial Semantics.label state
+         interpolation)
+      7. Task 8 A-2 Home (a11y — info IconButton bySemanticsLabel —
+         rev-2 W2 locked)
+      8. Task 8 A-2 Logs (a11y — copy IconButton bySemanticsLabel —
+         rev-2 W2 locked)
+      9. Task 8 A-3 (a11y — ProwlInput reset ≥48dp touch target)
+  * Verify: `grep -c testWidgets prowler-client/flutter/test/widget/*.dart`
+    pre-merge vs post-merge — delta must be exactly +9.
+  * Broader: `flutter test --reporter=compact` should pass ≥ (baseline + 9)
+    cases. The pre-merge baseline is currently ~120 cases per the prior
+    Phase 7 sweeps (recount via the same `flutter test` command before
+    starting Wave 1).
+- v0.7.0 ship date + tactical-close vs full-close timeline
+- Phase 7 LEARNINGS hand-off list (for `/gsd-extract-learnings 7`):
+  * AP-4 exception #6 — D-07-16 inline-decision (per D-07-14 light-touch)
+    contrasted with Phase 6 heavyweight exception docs
+  * Plan-author 2026-05-16 investigation produced fix shape that collapsed
+    B-3 from ~120 LOC to ~30 LOC; SCOPE REDUCER pattern documented
+  * UX-team CONDITIONAL sign-off as a phase-close gate (separate from
+    design-system-team sign-off — D-07-13 originally specified only the
+    latter; this run added the UX-team layer)
+
+**Step 3 — Flip ROADMAP.md plan list AND top-of-file phase checklist AND
+progress-table row (rev-3 WARNING W2 fix — THREE separate ROADMAP locations
+must change atomically, not just the plan list).**
+
+ROADMAP.md carries Phase 7 state in THREE distinct places — all three must
+flip in the same Edit pass for the file to be self-consistent:
+
+**(a) Top-of-file phases checklist** (line ~10-20, the high-level
+    `## Phases` section):
+    `- [ ] Phase 7: Design System Polish — REQ-14, REQ-15`
+  → `- [x] Phase 7: Design System Polish — REQ-14, REQ-15`
+
+**(b) Phase 7 plan list** (the per-plan checklist under `### Phase 7:`):
+  - Change `- [ ] 07-07-PLAN.md — ...` to
+    `- [x] 07-07-PLAN.md — ... (closed 2026-05-XX via 07-13-PLAN.md Wave 8b)`
+  - Change `- [ ] 07-12-PLAN.md — ...` (PARTIAL-DEFERRED note) to
+    `- [x] 07-12-PLAN.md — ... (closed 2026-05-XX via 07-13-PLAN.md Wave 8b)`
+  - Append new row: `- [x] 07-13-PLAN.md — v0.7.0 gap closure: 8 items (B-1/B-2/B-3/§1/§2/§3/§4a/B-4) + AP-4 exception D-07-16; closes Phase 7 (Wave 8b 2026-05-XX)`
+  - Update Plans count: `**Plans:** 13 plans` (was 12)
+
+**(c) Progress-table row** (the `## Progress` table near the file end):
+  - Change `Phase 7: Design System Polish | In Progress | 2026-05-14`
+  → `Phase 7: Design System Polish | Complete | 2026-05-XX`
+    (replace `In Progress` with `Complete` AND replace the start-date with
+    the close-date — the table column convention is
+    `Phase | Status | Date` where Date is start-OR-close depending on Status).
+
+**Why three locations:** the top-of-file checklist (a) is the
+operator-facing high-level summary; the per-phase plan list (b) is the
+detailed close-record; the progress-table row (c) is the dashboard
+the cross-AI review tooling reads. If any of the three lag, the
+file is internally inconsistent and downstream consumers see stale
+data. Verify gate 5b (added below) asserts the progress-table row
+was updated alongside gate 5 (the top-of-file checklist) and gate 2
+(the per-plan list).
+
+**Step 4 — Update STATE.md progress block (rev-2 WARNING W3 — convention locked).**
+
+Per memory `project_gsd_sdk_state_helper_regression`: do NOT use
+`gsd-sdk state.*` helpers (they regress the progress block to stale
+values); Edit the YAML frontmatter directly.
+
+Current (per `awk '/^progress:/,/^---/'`):
+```yaml
+progress:
+  total_phases: 9
+  completed_phases: 6
+  total_plans: 39
+  completed_plans: 36
+  percent: 95
+```
+
+**rev-2 WARNING W3 — convention LOCKED:** STATE.md `total_plans` counts
+ONLY v2.0 in-scope phases. The plan-author confirms the count is:
+
+    Phase 4 = 4 plans
+  + Phase 5 = 16 plans
+  + Phase 6 = 7 plans
+  + Phase 7 = 13 plans   ← after 07-13 lands
+  = 40 total in-scope plans (v2.0 client-side work)
+
+The on-disk plan count is 49 (the 39-tally STATE shows reflects an older
+convention; the 49 includes pre-v2.0 plans + scope-deferred plans that
+were never executed). The 40 number is the LOCKED v2.0-scope tally and
+matches the user's spec. Phase 8 (Windows) + Phase 9 (Distribution) plans
+do NOT contribute to `total_plans` until those phases are planned;
+`total_phases: 9` reflects the roadmap structure, not the plan-count
+denominator.
+
+**Recount math (rev-3 explicit, addresses rev-2 WARNING W1 cross-location
+reconciliation):** STATE currently shows `completed_plans: 36`. That tally
+reflects the OLD convention where one P6 plan was excluded (the planner
+never auditied which one; for STATE-frontmatter hygiene the recount
+operation is what matters, not the identity of the excluded plan). The
+W3-locked v2.0-scope convention reincludes it as part of the 7-plan P6
+tally. So:
+
+    36 (current STATE)
+  +  1 (W3 recount of previously-excluded P6 plan)
+  +  3 (closures of 07-07, 07-12, 07-13 at this full-close moment)
+  = 40 (final completed_plans value at Wave 8b full close)
+
+**Tactical close (Wave 8a interim, if operator elects to ship the
+7-of-8 items without B-1):** the same +1 W3 recount applies, but
+only 07-13 partial-flips at that moment (07-07 + 07-12 stay [ ]
+until full close). So:
+
+    36 (current STATE)
+  +  1 (W3 recount)
+  +  1 (07-13 partial flip at tactical close)
+  = 38 (interim completed_plans at Wave 8a tactical close)
+
+The W3 recount is a STATE-frontmatter hygiene action — it has no
+user-visible product impact; it merely reconciles the on-disk
+completed-plans tally with the v2.0-scope convention so STATE
+accurately reflects what shipped vs. what's scope-deferred.
+
+Final values after FULL Phase 7 close (Wave 8b, B-1 amendment + impl + UX
+team v4.2 unconditional sign-off):
+
+```yaml
+progress:
+  total_phases: 9        # roadmap structure (unchanged)
+  completed_phases: 7    # Phase 7 closes (was 6)
+  total_plans: 40        # v2.0 in-scope: 4+16+7+13 = 40 (was 39)
+  completed_plans: 40    # all 40 v2.0-scope plans now done (was 36)
+  percent: 100           # 40/40 = 100% of v2.0 client-side work
+                         # convention: percent keys off in-scope completion,
+                         # NOT off the (9-phase) total_phases denominator.
+                         # Phase 8 + Phase 9 sit OUTSIDE v2.0 scope; their
+                         # planning is a separate v2.x cycle.
+```
+
+**Tactical close interim (Wave 8a only — 7-of-8 items closed, B-1 carried):**
+if the operator elects tactical close as the SHIP date (and B-1 lands as
+a v0.7.1 follow-up plan that opens a new 07-NN-PLAN before Wave 8b can
+fire), the interim values would be:
+
+```yaml
+progress:
+  total_phases: 9
+  completed_phases: 6    # Phase 7 NOT yet complete
+  total_plans: 40
+  completed_plans: 38    # +1 W3 recount (P6 plan previously excluded under OLD
+                         #    convention; STATE currently shows 36, the
+                         #    W3 recount brings it to 37 as the new baseline)
+                         # +1 for 07-13 partial-flip at tactical close
+                         # 07-07 + 07-12 stay [ ] until full close — actual completed-
+                         #   tally re-confirmed at tactical-close time
+  percent: 95            # 38/40 = 95% (matches rounded math)
+```
+
+The FULL close (Wave 8b) is the 100% gate; the tactical close (Wave 8a
+alone) keeps percent in the 95-97 range until B-1 lands.
+
+Per memory `project_gsd_sdk_state_helper_regression`: after editing
+STATE.md, RE-READ it (via `gsd-sdk query state.load` OR direct Read of the
+frontmatter) and confirm the values stuck.
+
+**Step 5 — Atomic commit shape.**
+
+```
+docs(07-13): close Phase 7 — 07-07 + 07-12 + 07-13 summary, ROADMAP, STATE
+
+* 07-07-SUMMARY.md: designer-asset integration close record (cat launcher
+  icon + branded splash + font handoff + android:label + UX-team sign-off
+  via 07-13-PLAN.md Wave 8b).
+
+* 07-13-SUMMARY.md: v0.7.0 gap closure record — 8 items (B-1/B-2/B-3/§1/
+  §2/§3/§4a/B-4) + AP-4 exception D-07-16 + Pigeon expansion D-07-17 +
+  scope-reducer pattern (D-07-16 lift collapsed B-3 from ~120 LOC to ~30 LOC).
+
+* ROADMAP.md Phase 7 plan list: 07-07, 07-12, 07-13 flip to [x]; plan
+  count 12 → 13; phase status → Complete 2026-05-XX.
+
+* STATE.md progress: completed_phases 6→7, total_plans 39→40,
+  completed_plans 36→40 (full close: +1 W3 recount + 3 closures for
+  07-07/07-12/07-13) OR 36→38 (tactical close: +1 W3 recount + 1 for
+  07-13 partial-flip; 07-07/07-12 stay [ ] until full close).
+  Pick the branch matching whichever Wave 8 path executes. Percent
+  updated per the close convention (100% full / 95% tactical).
+
+Closes Phase 7. Phase 8 (Windows) unblocks per UX-REVIEW.md §7 + D-07-13.
+
+Next: `/gsd-extract-learnings 7` → 07-LEARNINGS.md → `/gsd-plan-phase 8`.
+```
+
+**Operator gate:** confirm the four files are written + ROADMAP/STATE flip
+landed. Type `phase-7-closed` to greenlight the atomic commit.
+  </action>
+  <verify>
+    <automated>
+      bash -c '
+      set -euo pipefail
+      cd /home/parf/projects/work/prowler
+      # Gate 1: both new SUMMARY files exist + are ≥20/40 lines respectively.
+      [ -f .planning/phases/07-design-system-polish/07-07-SUMMARY.md ]
+      [ "$(wc -l < .planning/phases/07-design-system-polish/07-07-SUMMARY.md)" -ge 20 ]
+      [ -f .planning/phases/07-design-system-polish/07-13-SUMMARY.md ]
+      [ "$(wc -l < .planning/phases/07-design-system-polish/07-13-SUMMARY.md)" -ge 40 ]
+      # Gate 2: ROADMAP Phase 7 plan list shows 07-07, 07-12, 07-13 all as [x].
+      grep -qE "^- \\[x\\] 07-07-PLAN" .planning/ROADMAP.md
+      grep -qE "^- \\[x\\] 07-12-PLAN" .planning/ROADMAP.md
+      grep -qE "^- \\[x\\] 07-13-PLAN" .planning/ROADMAP.md
+      # Gate 3: ROADMAP plan count updated to 13.
+      grep -q "13 plans" .planning/ROADMAP.md
+      # Gate 4: ROADMAP Phase 7 row in progress table flipped to Complete.
+      grep -qE "Phase 7.*Complete" .planning/ROADMAP.md
+      # Gate 5 (rev-2 WARNING W3 locked convention): STATE.md progress block
+      # reflects the FULL close — completed_phases: 7, total_plans: 40,
+      # completed_plans: 40, percent: 100 (v2.0 in-scope: 4+16+7+13=40).
+      awk "/^progress:/,/^---/" .planning/STATE.md > /tmp/progress.txt
+      grep -q "completed_phases: 7" /tmp/progress.txt
+      grep -q "total_plans: 40" /tmp/progress.txt
+      grep -q "completed_plans: 40" /tmp/progress.txt
+      grep -q "percent: 100" /tmp/progress.txt
+      # Gate 6: ROADMAP overall Phases checklist Phase 7 line flipped to [x].
+      grep -qE "^- \\[x\\] Phase 7" .planning/ROADMAP.md
+      # Gate 6b (rev-3 WARNING W2 fix — progress-table row flip asserted):
+      # The ## Progress table near file-end carries the phase Status column;
+      # Status must read `Complete` and the date must be 2026-05-XX format.
+      # If Gate 6 passes but 6b fails, the operator updated only the top-of-
+      # file checklist and NOT the progress-table — file is internally
+      # inconsistent.
+      grep -qE "Phase 7.*Complete.*2026-05-" .planning/ROADMAP.md || { \
+        echo "FAIL (rev-3 WARNING W2): progress-table row not flipped to Complete; \
+             only top-of-file checklist updated — ROADMAP internally inconsistent"; \
+        exit 1; }
+      echo "Task 12 (Wave 8b full Phase 7 close) gates PASS — awaiting operator phase-7-closed signal"
+      '
+    </automated>
+  </verify>
+  <done>
+    `07-07-SUMMARY.md` + `07-13-SUMMARY.md` written and committed.
+    ROADMAP.md Phase 7 plan list shows 07-07/07-12/07-13 all `[x]`,
+    plan count = 13, phase status = Complete. STATE.md progress block
+    reflects `completed_phases: 7 / total_plans: 40 / completed_plans: 40
+    / percent: 100` per the rev-2 WARNING W3 locked convention (v2.0
+    in-scope phases only: 4+16+7+13=40). Memory-verified post-edit per
+    `project_gsd_sdk_state_helper_regression`. Operator has typed
+    `phase-7-closed`. Phase 7 closed; Phase 8 unblocked.
+  </done>
+</task>
+
+</tasks>
+
+<threat_model>
+## Trust Boundaries
+
+| Boundary | Description |
+|----------|-------------|
+| Kotlin VPN service → Dart UI | The `ProwlerVpnService.kt` status broadcast crosses into the Pigeon `onStatusChanged` stream. The D-07-16 AP-4 lift suppresses the `disconnected("start-failed")` broadcast — Dart now sees only the error frame on this path. Trust assumption: no other Kotlin consumer of `ACTION_STATUS_CHANGED` requires the trailing disconnected broadcast (verified at plan time — zero such consumers). |
+| Dart UI → Pigeon API | `ConnectionActions.connect()` (Dart) → `ProwlerHostApi.connect()` (Kotlin). Existing validation in `prowler_config_validation.dart` runs Dart-side BEFORE crossing Pigeon (SH3 defense). B-4 surfaces this validation to the UI instead of silently discarding the result. |
+| go_router context.go → settings screen | B-4 fires `context.go('/settings')` from the dial widget. Assumes the `/settings` route exists (verified: `lib/app.dart:60-64` declares it). |
+
+## STRIDE Threat Register
+
+| Threat ID | Category | Component | Disposition | Mitigation Plan |
+|-----------|----------|-----------|-------------|-----------------|
+| T-07-13-01 | Tampering | `ProwlerVpnService.kt:stopLocked` AP-4 lift | mitigate | The 2-char predicate `&& reason != "start-failed"` is the entirety of the lift; reverting is 2-char revert. Risk register at `.planning/debug/AP4-EXCEPTION-D-07-16-*.md` enumerates the regression vectors. Wave 4 widget test (`connect_dial_test: connecting → error latches DialState.error`) is the regression gate. |
+| T-07-13-02 | Information disclosure | A-1 Semantics label includes "VPN" | accept | Semantics labels are assistive-tech-audience, not REQ-14 user-visible UI scope. Documented inline carve-out in connect_dial.dart. UX team explicitly specified this phrasing. |
+| T-07-13-03 | Denial of service | B-3 connectFailed enum + Kotlin synthesis | mitigate | The new enum case is exhaustive-switched in `error_banner._templateFor`; missing case = compile-time error (Dart enum exhaustiveness). Pigeon regen is part of Wave 3's atomic commit so .g files always agree with the source enum. |
+| T-07-13-04 | Repudiation | AP-4 exception with no formal doc | mitigate | Per D-07-14 light-touch, AP-4 exceptions in Phase 7 are inline-noted (commit subject cites D-07-16). For this specific lift, a formal `.planning/debug/AP4-EXCEPTION-D-07-16-*.md` is ALSO written per the 5 prior precedents in 06-LEARNINGS — defense-in-depth on auditability. |
+| T-07-13-05 | Elevation of privilege | B-4 SnackBar + nav from dial-tap | accept | The dial-tap handler runs in the user's interactive session; the only new capability is `context.go('/settings')` (already-reachable route) and `ScaffoldMessenger.showSnackBar` (standard Flutter UX). No privilege escalation surface. |
+| T-07-13-06 | Information disclosure | B-1 PING.md mentions specific endpoint constants | accept | The PING is shared with the design-system team (trusted internal audience); the constants (`_pulseOpacityMin`, `_sunDiameter` etc.) are visible in the open `lib/src/widgets/horizon_sliver.dart` source. No secret exposure. |
+</threat_model>
+
+<verification>
+**Phase-level acceptance (UX-team-conditional-sign-off closure):**
+
+Goal-backward checklist mapping each task to UX-letter closure:
+
+| Task | UX-REVIEW item closed              | Verification command                                                          |
+|------|------------------------------------|-------------------------------------------------------------------------------|
+| 1    | §1 (drop Home title)               | `! grep -q "title:.*Home" home_screen.dart` + v4.1 re-shoot 02-home visual    |
+| 2    | §2 (splash hold ≤ 1000ms)          | grep `windowSplashScreenAnimationDuration` = 800 + v4.1 cold-launch timing    |
+| 3    | §3 (5 copy rewrites)               | grep `serversSection = 'One server per layer.'` + `— · idle` absent           |
+| 4    | B-2 (empty-value suppression)      | widget test asserts no `exit  · ` / ` ms` literal + v4.1 02e-home visual      |
+| 5+6  | B-3 (silent-fail wiring + AP-4 ex) | Kotlin + Pigeon + Dart all wired; widget test connecting→error latches        |
+| 7    | B-4 (no-config nudge)              | widget test asserts SnackBar + /settings navigation                           |
+| 8    | §4a (A-1, A-2, A-3 a11y)           | a11y_semantics_test asserts each + ProwlInput touch-target ≥ 48dp             |
+| 9    | B-1 (PING composition)             | PING.md ≥ 60 lines + references HORIZON-SLIVER-REDLINE + dimensions A/B/C    |
+| 10   | B-1 (async-blocker handoff)        | operator dispatches PING + signals tactical-ship or await-amendment           |
+| 11   | UX-team v4.1 tactical confirmation | 7-of-8 captures + RESHOOT-SUMMARY.md + UX-team replies                        |
+| 12   | Phase 7 full close                 | 07-07 + 07-13 SUMMARYs + ROADMAP/STATE flip + operator `phase-7-closed`       |
+
+**Cross-task invariants:**
+
+- AP-4 byte-freeze: ONE exception (D-07-16), formally documented at
+  `.planning/debug/AP4-EXCEPTION-D-07-16-START-FAILED-DISCONNECTED-SUPPRESSION.md`,
+  cited in Task 5's commit subject. Phase-5 cross-UID Kotlin module still
+  compiles clean post-edit (`./gradlew :app:compileDebugKotlin`).
+
+- REQ-14 lexicon: `strings.dart` user-visible literals scan (excluding
+  comments) shows zero forbidden vocab (`grep -v "^\s*//" lib/src/l10n/strings.dart
+  | grep -iE "(VPN|proxy|circumvention|censorship|firewall|government|freedom)"`).
+  ONE carve-out: A-1 Semantics label contains "VPN" — documented inline,
+  audience-scoped to assistive technology.
+
+- Test count delta (rev-2 WARNING W5 reframed — falsifiable via grep):
+  widget `testWidgets` count grows by exactly +9 (not the original +5
+  claim — rev-2 BLOCKER B1 added Case B regression-gate test, rev-2 W2
+  locked A-2 Home + A-2 Logs tests). Verify shape:
+  `grep -c testWidgets prowler-client/flutter/test/widget/*.dart`
+  delta = +9. Broader `flutter test --reporter=compact` pass-count ≥
+  baseline + 9 (baseline ≈ 120 from prior Phase 7 sweeps; recount
+  pre-Wave-1 via the same command and pin in the SUMMARY).
+
+- Codegen consistency: pigeons/prowler_platform.dart, lib/src/generated/
+  prowler_platform.g.dart, android/app/.../generated/ProwlerPlatform.g.kt
+  all carry `connectFailed` enum value (Pigeon regen invariant).
+
+- v0.7.0 APK: pubspec.yaml `version: 0.7.0+11`, local.properties
+  `flutter.versionName=0.7.0`, multi-ABI APK at
+  `~/prowler-debug-v0.7.0-multiabi.apk`, fresh SHA ≠ v0.6.5 SHA.
+
+- ROADMAP/STATE close: Phase 7 row → Complete; 07-07/07-12/07-13 all `[x]`;
+  STATE.md progress reflects close (per memory `project_gsd_sdk_state_helper_regression`
+  manual Edit, not gsd-sdk state.* helpers).
+
+**Empirical splash-hold validation** (Wave 8a):
+- Capture launcher-tap → Home-first-frame wall-clock from `adb shell logcat
+  | grep "Activity.*Displayed"` (Android logs the Displayed event with
+  elapsed-since-launch ms). Target ≤ 1000ms (must-haves ceiling); aspiration
+  800ms.
+
+**B-1 verification** (Wave 8b, post-amendment):
+- Once redline v3 amendment lands + B-1 follow-up plan implements the
+  amended const values, re-run horizon_sliver_test (existing 07-04 widget
+  test suite) + visual v4.2 re-shoot of 02-home covering the reduced sliver
+  contribution.
+</verification>
+
+<success_criteria>
+- UX team's CONDITIONAL sign-off (UX-REVIEW.md) flips to UNCONDITIONAL after
+  v4.1 (tactical, 7-of-8 items) AND v4.2 (full, post-B-1) re-shoots.
+- Phase 7 closes (FULL via Wave 8b — post-B-1): ROADMAP 07-07/07-12/07-13
+  = `[x]`; STATE.md `completed_phases: 7 / total_plans: 40 /
+  completed_plans: 40 / percent: 100` per the rev-2 WARNING W3 locked
+  convention (v2.0 in-scope: 4+16+7+13=40). Phase 7 Status = Complete.
+- v0.7.0 multi-ABI APK ships with all 8 v0.7.0 items resolved (B-1 lands
+  in the post-amendment build; the other 7 in v0.7.0+11; SHA fresh).
+- AP-4 byte-freeze: ONE exception (D-07-16), formally documented per the
+  5 prior Phase-6 precedents; Phase-5 cross-UID gate still green
+  (`./gradlew :app:compileDebugKotlin` + the Phase-5 :route-test cross-UID
+  module unchanged).
+- Pigeon expansion (D-07-17): connectFailed enum landed cleanly across
+  source + both codegen targets + Kotlin synthesis + Dart template mapping.
+  Zero downstream breakage in existing template-mapping tests.
+- Test coverage (rev-2 WARNING W5 reframed — falsifiable, not static):
+  widget `testWidgets` count grows by exactly +9 (rev-2-adjusted from the
+  original +5 claim — BLOCKER B1 added Case B regression-gate, W2 locked
+  A-2 Home + A-2 Logs tests). 2 new test files
+  (`no_config_nudge_test.dart`, `a11y_semantics_test.dart`) + 4 new
+  cases inside `connect_dial_test.dart` / `error_banner_test.dart`
+  (B-2 + B-3 template + B-3 Case A + B-3 Case B). Broader
+  `flutter test --reporter=compact` should pass ≥ baseline + 9 cases.
+- Phase 8 (Windows) unblocked per UX-REVIEW.md §7 + D-07-13 (UX team
+  hint: "Phase 8 can start as soon as B-1, B-2, B-3 land").
+- 07-LEARNINGS.md hand-off list captured in 07-13-SUMMARY.md for
+  `/gsd-extract-learnings 7`: AP-4-exception-as-light-touch contrast with
+  Phase 6 ceremony; SCOPE-REDUCER pattern (Kotlin lift collapsing Dart
+  surface); UX-team-as-distinct-stakeholder-from-design-team.
+</success_criteria>
+
+<output>
+After all 12 tasks land + operator types `phase-7-closed` in Task 12, two
+SUMMARY files exist:
+
+1. `.planning/phases/07-design-system-polish/07-07-SUMMARY.md` — designer-
+   asset integration close record (07-07 plan closure)
+2. `.planning/phases/07-design-system-polish/07-13-SUMMARY.md` — this plan's
+   close record (per
+   `$HOME/.claude/get-shit-done/templates/summary.md`)
+
+The 07-13-SUMMARY.md should carry:
+- 8-item closure (B-1/B-2/B-3 + §1/§2/§3/§4a + B-4) with task-to-item map
+- AP-4 exception D-07-16 risk-register retrospective (any post-merge
+  regressions observed? if none, document the null result)
+- D-07-17 Pigeon enum expansion → zero downstream breakage notation
+- Test count delta (rev-2 WARNING W5 reframed): widget `testWidgets`
+  count +9 (verify via `grep -c testWidgets test/widget/*.dart`
+  pre-merge vs post-merge; broader `flutter test --reporter=compact`
+  passes ≥ baseline + 9). 2 new test files + 4 new cases in existing
+  files; rev-2 BLOCKER B1 added Case B + rev-2 W2 locked A-2 pair.
+- Splash-hold empirical measurement (cold-launch frame_02 timing from
+  `adb shell logcat | grep "Activity.*Displayed"`)
+- Cross-references: UX-REVIEW.md, INVESTIGATION-260516-blockers.md,
+  CONTEXT D-07-15/16/17/18, AP-4 exception doc, v0.7.0 APK SHA
+- Hand-off list for `/gsd-extract-learnings 7`: AP-4-light-touch contrast
+  with Phase 6 ceremony, SCOPE-REDUCER pattern (Kotlin lift → Dart
+  simplification), UX-team-vs-design-team-as-distinct-stakeholders
+
+Update ROADMAP.md Phase 7 plan list:
+  - [x] 07-07-PLAN.md — Designer-asset integration (closed 2026-05-XX via 07-13-PLAN.md Wave 8b)
+  - [x] 07-12-PLAN.md — Splash wordmark clip closure (closed 2026-05-XX via 07-13-PLAN.md Wave 8b)
+  - [x] 07-13-PLAN.md — v0.7.0 gap closure: 8 items (B-1/B-2/B-3/§1/§2/§3/§4a/B-4) + AP-4 exception D-07-16; closes Phase 7 (Wave 8b 2026-05-XX)
+
+And the Plans count: `**Plans:** 13 plans` (was 12).
+
+And the overall Phases checklist: `- [x] Phase 7: Design System Polish ...`
+
+Update STATE.md progress (Edit-only per memory
+`project_gsd_sdk_state_helper_regression`):
+  total_phases: 9          (unchanged — roadmap structure)
+  completed_phases: 7      (was 6 — Phase 7 closes)
+  total_plans: 40          (was 39; +1 for 07-13 — rev-2 W3: v2.0 in-scope
+                            tally = 4+16+7+13 = 40)
+  completed_plans: 40      (was 36; +1 W3 recount for the
+                            previously-excluded P6 plan + 3 closures for
+                            07-07 + 07-12 + 07-13 — see Task 12
+                            Step 4 for the full math)
+  percent: 100             (40/40 = 100% of v2.0 in-scope; percent keys
+                            off v2.0 scope completion, not off the
+                            9-phase total_phases denominator. Phase 8
+                            and Phase 9 are outside v2.0 scope and are
+                            planned in a separate v2.x cycle.)
+
+Verify STATE.md frontmatter stuck after Edit (per memory: gsd-sdk state.*
+helpers regress the block; manual Edit + Re-read confirms).
+
+Next operator step: `/gsd-extract-learnings 7` → `07-LEARNINGS.md` →
+`/gsd-plan-phase 8` (Windows platform).
+</output>