chore: delete the Flutter client — #2710

Superseded by the M8 native Android rewrite. Last touched 2026-05-31,
no workflow has built it since flutter.yml was removed, and rule #22
says a replaced path goes rather than lingering as something a reader
has to work out the status of. 245 files, ~24.6k lines.

Config references go with it: the .gitignore block (and its now-empty
"# Flutter" header), the .dockerignore entry, and renovate's ignorePaths
entry, which was suppressing dependency scanning for a directory that
no longer exists.

ci-requirements.md said ci-flutter "will retire once that directory
goes". It has gone, so the doc now says so -- CI-Runner can drop the
image, and nothing in this repo needs a Flutter toolchain.

One thing is kept rather than deleted: shared/fabledsword.tokens.json.
It lived under flutter_client/shared/ but was never Flutter's property
-- it is the canonical statement of the palette, the only place the
dark, light and flat cohorts are written down together, and
FabledSwordTokens.kt names it as its source of truth. Losing it would
have been collateral damage, so it moves to the repo root with a README
saying what it is and that neither client generates from it. That
comment in FabledSwordTokens.kt is repointed here.

What deliberately does NOT change: `runs-on: flutter-ci` in android.yml
and release.yml. That is a runner LABEL, not a path -- the Android jobs
schedule on it while pulling ci-android:36, per the label/image split
ci-requirements.md documents. Removing it would break scheduling for a
cosmetic win, so the doc now spells that out beside the retirement note.

Left for #2710: 64 files whose comments still name flutter_client/
paths. Sweeping them here would have buried the deletion, and each
needs a judgement -- keep the substance and drop the dead path, delete
pure "ported from" bookkeeping, or leave design rationale that happens
to mention the Flutter build.

ci-requirements.md

@@ -15,11 +15,16 @@ git.fabledsword.com/bvandeusen/ci-android:36
 - `ci-go:1.26` — Go server tests (`.gitea/workflows/test-go.yml`), web SPA tests (`.gitea/workflows/test-web.yml`), and the release container build (`release.yml`'s `image-release` job).
 - `ci-android:36` — native Kotlin/Compose client: ktlint + detekt + unit tests + debug APK (`.gitea/workflows/android.yml`), and the signed release APK (`release.yml`'s `android-release` job).
 
-**`ci-flutter` is no longer consumed.** The M8 rewrite replaced the Flutter
-client with the native Android app and `flutter.yml` was removed; `ci-android`
-took its place. `flutter_client/` is still in the tree but nothing builds it.
-CI-Runner still publishes `ci-flutter` and will retire it once that directory
-goes — so if the Flutter client is ever revived, say so there first.
+**`ci-flutter` is no longer consumed, and `ci-flutter` can now be retired.**
+The M8 rewrite replaced the Flutter client with the native Android app and
+`flutter.yml` was removed; `ci-android` took its place. `flutter_client/`
+itself was deleted on 2026-08-16, which was the condition CI-Runner was
+waiting on before dropping the image — nothing in this repo needs a Flutter
+toolchain any more.
+
+Note this does **not** mean the `flutter-ci` runner *label* goes: the Android
+jobs still schedule on it while pulling `ci-android:36`, per the label/image
+split below. The label is a scheduling handle, not a toolchain assertion.
 
 ## Image deps used