feat: introduce multi-layer cache pipeline spec for enhanced caching strategy

- Added a comprehensive specification for a multi-layer cache pipeline that supports memory and file caching with fallback mechanisms.
- Defined goals, architectural decisions, and API contracts for cache layers and policies.
- Included detailed implementation plans and test strategies to ensure robust caching behavior.

feat: propose operation-based mutations transaction model

- Introduced a new transaction model for `MutationMixins` to handle optimistic and concurrent writes.
- Defined API contracts for transaction operations and an internal transaction engine.
- Established conflict resolution strategies and execution algorithms to ensure deterministic behavior.

feat: add repo state persistence and bootstrap sync spec

- Proposed a specification for durable repo state hydration and background synchronization.
- Defined policies for snapshot management, hydration modes, and error handling.
- Introduced a persistence service and bootstrap coordinator to manage repo state effectively.

feat: create shared storage, serialization, and schema strategy foundation spec

- Established shared contracts for storage keys, serialization codecs, and schema mismatch handling.
- Defined a schema fingerprinting model to ensure consistency across caching and persistence layers.
- Provided integration rules for consumer specs to utilize shared contracts without duplication.

Author: mcquenji

lib/src/domain/services/analytics_service.dart

@@ -84,7 +84,6 @@ import 'package:grumpy/grumpy.dart';
 /// - [TelemetryContext] — for span execution context
 ///
 abstract class AnalyticsService extends Service {
-
   /// Returns the DI-registered implementation of [AnalyticsService].
   ///
   /// Shorthand for [Service.get].
@@ -94,6 +93,7 @@ abstract class AnalyticsService extends Service {
 
   /// Internal constructor for subclasses.
   AnalyticsService.internal();
+
   /// Identifies a user within the analytics system.
   ///
   /// Should be called once the user is known (e.g., after login or signup).