[feat] enable-background-download

.fvmrc

@@ -1,3 +1,3 @@
 {
-  "flutter": "3.41.6"
+  "flutter": "3.47.2"
 }

ONBOARDING.md

@@ -115,7 +115,7 @@ The detailed docs live in `docs/`. Read them in this order if you're new:
 1. **[docs/content-rendering.md](docs/content-rendering.md)** — HTML rendering, the `sanitize()` workarounds, `flutter_html_table` filter in `main.dart`.
 1. **[docs/onboarding-flow.md](docs/onboarding-flow.md)** — the three onboarding pages and their persistence side-effects.
 1. **[docs/features.md](docs/features.md)** — pages, widgets, drawer, share menu, language switcher.
-1. **[docs/background-tasks.md](docs/background-tasks.md)** — `workmanager` isolate, the result-sync trick, why parts are commented out.
+1. **[docs/background-tasks.md](docs/background-tasks.md)** — `workmanager` isolate, the two-phase check/download flow, the settings matrix, and the result-sync trick.
 1. **[docs/localization.md](docs/localization.md)** — `.arb` workflow, `context.l10n` extension, in-app language vs. content language.
 1. **[docs/testing.md](docs/testing.md)** — unit/widget tests, fixtures, integration test, CI.
 1. **[docs/conventions.md](docs/conventions.md)** — coding conventions, lints, do/don't.
@@ -131,7 +131,7 @@ These are the load-bearing oddities — read these before changing code in their
 - **`LanguageDownloader`** (`lib/data/language_downloader.dart`) is the in-house module that downloads + unzips a language's HTML + PDF into a staging directory and swaps it into place atomically. Failed downloads never destroy prior offline content, concurrent `download()` calls are serialized (peak memory bounded by two zips), and a `.staging` leftover from a crashed run is cleaned up on the next attempt. It replaced the third-party `download_assets` package and is wired up in `main.dart` and the background isolate via `languageDownloaderProvider.overrideWithValue(...)`.
 - **`flutter_html` error filter.** `main.dart` installs a `FlutterError.onError` shim that swallows four specific assertions thrown by `flutter_html_table` 3.0.0. Read the long docstring there before touching it — the four assertion variants are documented in detail.
 - **HTML pre-processing.** `widgets/html_view.dart` calls `sanitize()` to fix bugs in `flutter_html` (e.g. percent table widths, fuzzy translations, stylized subtitles). Some workarounds are also in the HTML generator (`pywikitools`) upstream.
-- **Background task is half-disabled.** Big chunks of `BackgroundScheduler.schedule()` and `Workmanager().initialize` in `main.dart` are commented out, gated on a "version 0.9" milestone. Don't delete them — they are the working scaffolding for the next release.
+- **Background task is enabled and settings-driven.** `BackgroundScheduler.schedule()` registers a periodic `workmanager` task at the `CheckFrequency` interval (or cancels it when `never`), and `backgroundMain()` runs a two-phase flow: `backgroundCheck` then a settings-gated `backgroundDownload` (see the `AutomaticUpdates` × connectivity matrix in `docs/background-tasks.md`). Scheduling is owned by `BackgroundScheduler`, triggered from startup / onboarding step 3 / the check-frequency setting — `main.dart` only calls `Workmanager().initialize(backgroundTask)`.
 - **No package on pub.dev.** `pubspec.yaml` has `publish_to: 'none'`.
 - **License is AGPL** with an Apple App Store exception. See `LICENSE` and `COPYING.iOS`.
 - **`test` is pinned to ^1.29.0** because 1.30+ needs a newer `test_api` than `flutter_test` allows.
@@ -170,8 +170,8 @@ ______________________________________________________________________
 
 ## 8. Roadmap context (from README)
 
-- **0.9**: enable automatic background updates (scaffolding present but commented out).
+- **0.9**: enable automatic background updates — **done**: the periodic task is
+  scheduled from `CheckFrequency` and downloads per `AutomaticUpdates` (see
+  `docs/background-tasks.md`).
 - **1.0**: solid release.
 - iOS planned for 2024.
-
-If you see code with `TODO for version 0.9`, that's why.

analysis_options.yaml

@@ -7,6 +7,11 @@
 
 # The following line activates a set of recommended lints for Flutter apps,
 # packages, and plugins designed to encourage good coding practices.
+analyzer:
+  exclude:
+    - build/**
+    - android/**
+    - ios/**
 include: package:flutter_lints/flutter.yaml
 
 linter:

android/app/src/main/AndroidManifest.xml

@@ -6,6 +6,8 @@
     <uses-permission android:name="android.permission.READ_MEDIA_VIDEO" tools:node="remove" />
     <uses-permission android:name="android.permission.READ_MEDIA_AUDIO" tools:node="remove" />
     <uses-permission android:name="android.permission.INTERNET" />
+    <!-- connectivity_plus: query WiFi/mobile connection type for onlyOnWifi -->
+    <uses-permission android:name="android.permission.ACCESS_NETWORK_STATE" />
    <application
         android:label="4training.net"
         android:name="${applicationName}"

android/gradle.properties

@@ -1,5 +1,7 @@
 org.gradle.jvmargs=-Xmx1536M
 android.useAndroidX=true
 android.enableJetifier=false
+# This builtInKotlin flag was added automatically by Flutter migrator
 android.builtInKotlin=false
+# This newDsl flag was added automatically by Flutter migrator
 android.newDsl=false

docs/architecture.md

@@ -19,11 +19,14 @@ There is no app-owned backend; all content comes from public GitHub repos and th
 - **Background isolate**:
   - Spawned by `workmanager`. Runs `backgroundTask()` in `lib/background/background_task.dart`,
     builds its own `ProviderContainer`, checks each downloaded language for new GitHub commits,
-    persists results to `SharedPreferences`.
+    persists results to `SharedPreferences`, and — depending on the `AutomaticUpdates` setting and
+    connectivity — downloads the languages that have updates.
     The main isolate later detects the activity by reloading shared prefs (see `BackgroundResultNotifier.checkForActivity`).
 
-> **Note:** Currently the periodic registration of the background task is **commented out** (gated behind "version 0.9").
-> The task is wired up and tested in the integration test, but is not actually being scheduled at app launch.
+> **Note:** The periodic task is scheduled by `BackgroundScheduler.schedule()`
+> at the `CheckFrequency` interval (not scheduled when `never`), and its run is
+> gated by the `AutomaticUpdates` setting (check-only, or download on WiFi /
+> always). See `docs/background-tasks.md`.
 
 ## Layered overview