Successfully modified file: /home/Messier82/projects/service-book/docs/plan-smoke-tests.md (1 replacements). Here is the updated code:
...
1. Launch on `VehicleListScreen`. Verify the read-only status card is displayed.
2. From the test process, call `setBillingOverride(FORCE_PREMIUM)`.
3. `waitUntil` the status card is no longer displayed (timeout 5s — involves DataStore write + Flow combine + recomposition).
4. Tap the "Add Vehicle" FAB and verify it navigates to `AddEditVehicleScreen` (no upgrade sheet).
5. Press back; tap "Car A" → `VehicleDetailScreen`. Verify the status card is absent and the "Add Record" FAB is enabled.
**Verifies:** Reactive lift of read-only mode end-to-end through `BillingManagerImpl` → `AppGate` → ViewModels → UI on the real Compose pipeline. Catches stale-state bugs in the gate's `combine` pipeline that unit tests can miss when scope/dispatcher choices differ from production.

---

### S21: Crash Reporting Opt-in Persists (Sentry)
...
**Verifies:** Crash reporting preference persists across sessions via DataStore and correctly reflects in the UI. This protects the plumbing that determines if Sentry initializes on next launch.

---

## Scenarios Explicitly Out of Scope
### S21: Crash Reporting Opt-in Persists (Sentry)

**Precondition:** Vault configured.

**Flow:**
1. Navigate to `SettingsScreen`.
2. Find the "Help improve the app" toggle and turn it **ON**.
3. Exit the app (or recreate the Activity).
4. Navigate back to `SettingsScreen`.
5. Verify the toggle is still **ON**.
6. Turn the toggle **OFF**.
7. Exit the app (or recreate the Activity).
8. Navigate back to `SettingsScreen`.
9. Verify the toggle is still **OFF**.

**Verifies:** Crash reporting preference persists across sessions via DataStore and correctly reflects in the UI. This protects the plumbing that determines if Sentry initializes on next launch.

---

## Scenarios Explicitly Out of Scope

**Precondition:** App has navigated several screens deep (e.g., VehicleList -> VehicleDetail -> RecordDetail).

**Flow:**
1. Starting from `RecordDetailScreen`
2. Press the system back button or toolbar back arrow
... Applied fuzzy match at line 346-350.