feat(studio): operator QoL — flow runnability, audit grouping, batch approvals, welcome celebration (v0.42.0)

Four UX threads stitched into one commit. Each pulls Studio
toward Stefan's "zero-learning-curve" goal — the feedback
that earned its own memory entry.

1. Flow-Runnability-Indikator
   ─────────────────────────
   The Flows tab now fetches `listFlows` and `listModules`
   in parallel. Each card compares the flow's
   `requiredCapabilities` against the installed-modules'
   capability set; rows with missing modules show a "Needs:
   text.extract@^0" red pill row beneath the path and have
   their Run button greyed out + tooltip
   "Install the missing modules first." Operators stop
   hitting Run → cryptic hub error → frustration.

2. Welcome-Checklist Celebration
   ─────────────────────────────
   Once all four checklist signals flip to done, an
   `_AllDoneCelebration` card replaces the bare
   "All four steps complete" + Hide button. Three concrete
   next-threads with action buttons: "Read the audit log",
   "Set up the daily Today story" (opens the Flows / Today
   doc inline via `_DocReaderSheet`), and "Build your own
   module" (opens the architecture doc). Operator who just
   got set up sees what to do next instead of an empty
   "what now?" feeling.

3. Audit-Page Time-Bucket Headers + Flow-Run Detail
   ────────────────────────────────────────────────
   The flat event list grows tiny "TODAY / YESTERDAY /
   EARLIER THIS WEEK / OLDER" section headers — bucket is
   computed in the operator's local timezone so an event at
   23:55 yesterday in Berlin doesn't end up in "today"
   because UTC happened to spill into a new day.
   Plus: the event-detail dialog gains a "View flow run"
   action when the picked event has a `flow_execution`. It
   opens a drill-down that lists every event in the
   already-fetched 100-event window sharing the same
   execution id, sorted ascending — the operator reads the
   run from step.started top to flow.completed bottom.

4. Approvals-Batch-Aktionen
   ────────────────────────
   Each pending approval card grows a checkbox. When ≥1
   selected, a floating action bar appears at the bottom
   with "N selected · Select all · Clear · Reject all ·
   Approve all". The parent loops sequentially through the
   per-record SDK calls so a partial failure produces
   "X done, Y failed" instead of a confusing all-or-nothing
   rollback. Reject prompts for a reason once and applies
   to the whole picked set.

13 new ARB keys cover the strings the four features
needed. Studio's tests stay green.

Signed-off-by: flemming-it <stefan.a.flemming@googlemail.com>

lib/l10n/app_localizations_en.dart

@@ -1074,6 +1074,111 @@ class AppLocalizationsEn extends AppLocalizations {
     return 'Could not read \"$path\": $error';
   }
 
+  @override
+  String get flowsMissingModulesLabel => 'Needs:';
+
+  @override
+  String get flowsRunDisabledTooltip => 'Install the missing modules first.';
+
+  @override
+  String get welcomeChecklistAllSetTitle => 'You\'re set up.';
+
+  @override
+  String get welcomeChecklistAllSetBody => 'Three threads to pull on next:';
+
+  @override
+  String get welcomeChecklistNextAuditTitle => 'Read the audit log';
+
+  @override
+  String get welcomeChecklistNextAuditBody =>
+      'Every install, flow run, and approval lives in the hash-chained log. Open the Audit tab to see what your hub has been up to.';
+
+  @override
+  String get welcomeChecklistNextAuditButton => 'Open Audit';
+
+  @override
+  String get welcomeChecklistNextTodayTitle => 'Set up the daily Today story';
+
+  @override
+  String get welcomeChecklistNextTodayBody =>
+      'Run tools/today/propose.sh on a cron and the editorial card on the store auto-fills with operator-curated narratives.';
+
+  @override
+  String get welcomeChecklistNextTodayButton => 'Open Today docs';
+
+  @override
+  String get welcomeChecklistNextModuleTitle => 'Build your own module';
+
+  @override
+  String get welcomeChecklistNextModuleBody =>
+      'Generate a Rust+WASM scaffold with `fai new module <name>`. The module-sdk handles the WIT plumbing; you write a typed invoke.';
+
+  @override
+  String get welcomeChecklistNextModuleButton => 'Read the docs';
+
+  @override
+  String get auditGroupToday => 'TODAY';
+
+  @override
+  String get auditGroupYesterday => 'YESTERDAY';
+
+  @override
+  String get auditGroupThisWeek => 'EARLIER THIS WEEK';
+
+  @override
+  String get auditGroupOlder => 'OLDER';
+
+  @override
+  String get auditEventViewFlowRun => 'View flow run';
+
+  @override
+  String auditFlowRunDialogTitle(String flow) {
+    return 'Flow run · $flow';
+  }
+
+  @override
+  String auditFlowRunDialogSubtitle(int n, String execution) {
+    String _temp0 = intl.Intl.pluralLogic(
+      n,
+      locale: localeName,
+      other: 'events',
+      one: 'event',
+    );
+    return '$n $_temp0 for execution $execution';
+  }
+
+  @override
+  String get approvalsSelectAll => 'Select all';
+
+  @override
+  String get approvalsClearSelection => 'Clear';
+
+  @override
+  String approvalsBatchSelected(int n) {
+    return '$n selected';
+  }
+
+  @override
+  String get approvalsBatchApprove => 'Approve all';
+
+  @override
+  String get approvalsBatchReject => 'Reject all';
+
+  @override
+  String approvalsBatchApproveDoneToast(int n) {
+    return '$n approvals approved.';
+  }
+
+  @override
+  String approvalsBatchRejectDoneToast(int n) {
+    return '$n approvals rejected.';
+  }
+
+  @override
+  String approvalsBatchPartialFailure(int ok, int failed) {
+    return '$ok done, $failed failed.';
+  }
+
   @override
   String get flowsRunButton => 'Run';