refactored and condensed technical documentation and comments across the codebase to improve readability

lib/push/push_actions.dart

@@ -146,16 +146,13 @@ class PushActions {
     }
   }
 
-  /// Ends the reply interaction. The card itself is already gone — the
-  /// action's native `cancelNotification` removed it the moment the reply
-  /// fired (a Dart-side cancel instead does NOT work everywhere: MIUI/HyperOS
-  /// ignores app cancels while an inline reply is pending). What remains:
-  /// success clears the stacked history so the next push starts fresh (plus a
-  /// redundant defensive cancel); failure re-renders silently, which the
-  /// renderer's active-probe turns into a no-op when the card is really gone
-  /// — the failure surface is the error card posted by the caller.
-  /// Injectable seams so tests can observe the flow without platform
-  /// channels.
+  /// Ends the reply interaction. The card is already gone — the action's
+  /// native `cancelNotification` removed it when the reply fired (a Dart-side
+  /// cancel is unreliable: MIUI/HyperOS ignores app cancels while an inline
+  /// reply is pending). Success clears the stacked history (plus a defensive
+  /// cancel); failure re-renders silently, a no-op when the card is really
+  /// gone — the real failure surface is the error card posted by the caller.
+  /// Injectable seams let tests observe the flow without platform channels.
   static Future<void> finishReply({
     required String chatToken,
     required bool sent,