Simplify subscription management - usually no manual cleanup needed (GC handles it)

Author: escamoteur

code_samples/lib/command_it/command_chaining_cleanup.dart

@@ -31,53 +31,6 @@ class CleanupManager {
 }
 // #endregion cleanup_basic
 
-// #region cleanup_multiple
-class MultiPipeManager {
-  late final inputCommand = Command.createSync<String, String>(
-    (s) => s,
-    initialValue: '',
-  );
-
-  late final saveCommand = Command.createAsyncNoResult<String>(
-    (s) async => api.saveContent(s),
-  );
-
-  late final logCommand = Command.createSync<String, void>(
-    (s) => print('Logged: $s'),
-    initialValue: null,
-  );
-
-  late final analyticsCommand = Command.createSync<String, void>(
-    (s) => print('Analytics: $s'),
-    initialValue: null,
-  );
-
-  // Multiple subscriptions
-  final List<ListenableSubscription> _subscriptions = [];
-
-  MultiPipeManager() {
-    _subscriptions.addAll([
-      inputCommand.pipeToCommand(saveCommand),
-      inputCommand.pipeToCommand(logCommand),
-      inputCommand.pipeToCommand(analyticsCommand),
-    ]);
-  }
-
-  void dispose() {
-    // Cancel all subscriptions
-    for (final sub in _subscriptions) {
-      sub.cancel();
-    }
-    _subscriptions.clear();
-
-    inputCommand.dispose();
-    saveCommand.dispose();
-    logCommand.dispose();
-    analyticsCommand.dispose();
-  }
-}
-// #endregion cleanup_multiple
-
 void main() {
   // Examples compile but don't run
 }

docs/documentation/command_it/command_chaining.md

@@ -127,15 +127,17 @@ The real power comes from combining `pipeToCommand` with [listen_it operators](/
 
 ## Subscription Management
 
-`pipeToCommand` returns a `ListenableSubscription`. Always store and cancel it to prevent memory leaks.
+`pipeToCommand` returns a `ListenableSubscription`. However, **you usually don't need to manage it manually**.
 
-### Basic Cleanup
+::: tip Automatic Cleanup
+When commands and pipes are in the same object (manager/service class), the subscription is automatically garbage collected when the containing object becomes unreachable. No manual cleanup needed!
 
-<<< @/../code_samples/lib/command_it/command_chaining_cleanup.dart#cleanup_basic
+See [listen_it Memory Management](/documentation/listen_it/best_practices#understanding-chain-garbage-collection) for details.
+:::
 
-### Multiple Subscriptions
+For cases where you do need manual control (e.g., dynamically created pipes with operators):
 
-<<< @/../code_samples/lib/command_it/command_chaining_cleanup.dart#cleanup_multiple
+<<< @/../code_samples/lib/command_it/command_chaining_cleanup.dart#cleanup_basic
 
 ## Warning: Circular Pipes
 

docs/es/documentation/command_it/command_chaining.md

@@ -127,15 +127,17 @@ El verdadero poder viene de combinar `pipeToCommand` con [operadores de listen_i
 
 ## Gestión de Suscripciones
 
-`pipeToCommand` retorna un `ListenableSubscription`. Siempre guárdalo y cancélalo para prevenir memory leaks.
+`pipeToCommand` retorna un `ListenableSubscription`. Sin embargo, **usualmente no necesitas gestionarlo manualmente**.
 
-### Limpieza Básica
+::: tip Limpieza Automática
+Cuando los commands y pipes están en el mismo objeto (clase manager/servicio), la suscripción es automáticamente recolectada por el garbage collector cuando el objeto contenedor se vuelve inalcanzable. ¡No se necesita limpieza manual!
 
-<<< @/../code_samples/lib/command_it/command_chaining_cleanup.dart#cleanup_basic
+Ver [Gestión de Memoria de listen_it](/es/documentation/listen_it/best_practices#understanding-chain-garbage-collection) para detalles.
+:::
 
-### Múltiples Suscripciones
+Para casos donde necesitas control manual (ej., pipes creados dinámicamente con operadores):
 
-<<< @/../code_samples/lib/command_it/command_chaining_cleanup.dart#cleanup_multiple
+<<< @/../code_samples/lib/command_it/command_chaining_cleanup.dart#cleanup_basic
 
 ## Advertencia: Pipes Circulares