Initial commit: Grounded Flutter frontend

A to-do app that doesn't believe you — an enforcement layer rather than a
neutral ledger.

Architecture ported from Autoreceptives/Frontend/Receptive: stacked MVVM with
the mandatory 4-file screen pattern, one ParentViewModel owning the loading /
network / error overlays and the handleError decision tree, one AppDataManager
gateway, dio comms carrying the three identity headers, secure storage with
random-suffixed keys, and a single-chokepoint Navigator. Package root and Dart
package name are both Grounded; org is nya.

The enforcement engine, one unit per formula in utils/:

- DebtEngine      w(class) x severity(d) x decay(t), sublinear severity so old
                  misses cannot swamp the score; abandonment 2x with 30-day
                  decay immunity; late complete retains 30%
- StandingEngine  Good -> Warned -> Grounded -> Lockdown, derived not set;
                  Grounded replaces home with the overdue queue
- CapacityEngine  blocks over-scheduling against p50 of historically completed
                  minutes, with a learned per-category estimation multiplier
- IntegrityEngine session integrity, weekly volume, plyometric contact ceiling
                  and enforced recovery gaps
- ExcuseAnalyser  on-device excuse clustering plus the confrontation copy
- GuardrailEngine distress detection and rationed amnesty
- ToneEngine      all enforcement copy, so the tone cap lives in one place

CommitmentEvent is append-only and is the source of truth rather than the
status field, which is what makes honest history and excuse analysis possible.

Goals contain commitments via parentId, and a task can be run from a
full-screen runner that derives elapsed time from wall-clock so screen-off
cannot lose time. Backgrounding pauses the clock and is counted. The runner is
mirrored into an ongoing notification, with alarm-class full-screen intents
reserved for non-negotiables.

Design language, fonts, icon and native splash are in place; Mason bricks are
retargeted to this project and verified end-to-end.

flutter analyze lib/ reports no errors.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Mfu2gQLSFN21YRBcU2NrTt

frontend/lib/Grounded/configs/Navigator.dart

@@ -0,0 +1,61 @@
+import 'package:flutter/material.dart';
+import 'package:page_transition/page_transition.dart';
+
+import '../about/internal/application/NavigatorType.dart';
+
+/// Every transition in the app funnels through here. Destinations are widget
+/// instances, not named routes, and the single choke point is what lets a
+/// device-integrity check gate all routing.
+class GroundedNavigation {
+  void navigateToPage(NavigatorType type, dynamic path, BuildContext context) {
+    _runSec(context, type, path);
+  }
+
+  Future _runSec(BuildContext context, NavigatorType type, dynamic path) async {
+    switch (type) {
+      case NavigatorType.openFully:
+        Navigator.of(context).pushReplacement(
+            MaterialPageRoute(builder: (BuildContext context) => path));
+        break;
+      case NavigatorType.justOpen:
+        Navigator.push(
+            context,
+            PageTransition(
+                type: PageTransitionType.size,
+                alignment: Alignment.center,
+                child: path));
+        break;
+      case NavigatorType.replaceCurrent:
+        Navigator.pushReplacement(
+            context,
+            PageTransition(
+                type: PageTransitionType.scale,
+                alignment: Alignment.center,
+                curve: Curves.ease,
+                duration: const Duration(microseconds: 9000),
+                child: path));
+        break;
+      case NavigatorType.makeNewMain:
+        Navigator.pushAndRemoveUntil(
+            context,
+            PageTransition(
+                type: PageTransitionType.fade,
+                alignment: Alignment.center,
+                child: path),
+            ModalRoute.withName('/'));
+        break;
+    }
+  }
+
+  /// The reload-on-return channel: the child pops with a result and the parent
+  /// refreshes on it.
+  Future<dynamic> navigateToPageWithData(
+      dynamic path, BuildContext context) async {
+    return await Navigator.push(
+      context,
+      MaterialPageRoute(
+        builder: (context) => path,
+      ),
+    );
+  }
+}