Move includeLastResultInCommandResults details to command_results.md

Changes:
- Expanded command_results.md section with detailed explanation of when the flag applies (execution AND error states)
- Added common use cases (pull-to-refresh, stale-while-revalidate, error recovery, optimistic UI)
- Added "When to use" guidance with examples of good and bad scenarios
- Simplified command_types.md descriptions to be brief with links to detailed explanation
- Removed AI warning banner from command_results.md

Result: Detailed explanation lives in one canonical place (command_results.md) with brief summaries and links in command_types.md

Author: escamoteur

docs/documentation/command_it/command_results.md

@@ -1,9 +1,5 @@
 # Command Results
 
-::: warning AI-Generated Content Under Review
-This documentation was generated with AI assistance and is currently under review. While we strive for accuracy, there may be errors or inconsistencies. Please report any issues you find.
-:::
-
 Deep dive into `CommandResult` - the comprehensive state object that combines execution state, result data, errors, and parameters in a single observable property.
 
 ## Overview
@@ -88,7 +84,7 @@ Error:      { data: null, error: Exception(), isRunning: false }
 
 ### includeLastResultInCommandResults
 
-Set `includeLastResultInCommandResults: true` to keep showing old data:
+By default, `CommandResult.data` becomes `null` during command execution and when errors occur. Set `includeLastResultInCommandResults: true` to keep the last successful value visible in both states:
 
 ```dart
 Command.createAsync<String, List<Todo>>(
@@ -98,6 +94,11 @@ Command.createAsync<String, List<Todo>>(
 );
 ```
 
+**When this flag affects behavior:**
+
+1. **During execution** (`isRunning: true`) - Old data remains in `result.data` instead of becoming `null`
+2. **During error states** (`hasError: true`) - Old data remains in `result.data` instead of becoming `null`
+
 **Modified flow:**
 
 ```
@@ -113,7 +114,19 @@ Running:    { data: [old results], error: null, isRunning: true }  ← Still vis
 Error:      { data: [old results], error: Exception(), isRunning: false }  ← Still visible
 ```
 
-**Use case:** Pull-to-refresh, stale-while-revalidate pattern
+**Common use cases:**
+
+- **Pull-to-refresh** - Show stale data while loading fresh data
+- **Stale-while-revalidate** - Keep showing old content during updates
+- **Error recovery** - Display last known good data even when errors occur
+- **Optimistic UI** - Maintain UI stability during background refreshes
+
+**When to use:**
+- ✅ List/feed refresh scenarios where empty states look jarring
+- ✅ Search results that update incrementally
+- ✅ Data that's better stale than absent
+- ❌ Login/authentication where stale data is misleading
+- ❌ Critical data where showing old values during errors is unsafe
 
 ## Result Properties
 

docs/documentation/command_it/command_types.md

@@ -71,7 +71,7 @@ static Command<TParam, TResult> createAsync<TParam, TResult>(
 
 - **`ifRestrictedRunInstead`** - Alternative function called when command is restricted (e.g., show login dialog). See [Restrictions](/documentation/command_it/restrictions)
 
-- **`includeLastResultInCommandResults`** - When `true`, includes the last successful value in `CommandResult` during execution **and error states**. When `false` (default), `CommandResult.data` is `null` during execution and errors. Useful for refresh scenarios where you want old data to remain visible while loading new data or when errors occur
+- **`includeLastResultInCommandResults`** - When `true`, keeps the last successful value visible in `CommandResult.data` during execution and error states. Default is `false` (data becomes `null` during these states). See [Command Results - includeLastResultInCommandResults](/documentation/command_it/command_results#includelastresultincommandresults) for detailed explanation and use cases
 
 - **`errorFilter`/`errorFilterFn`** - Configure how errors are handled (local handler, global handler, or both). See [Error Handling](/documentation/command_it/error_handling) and [Error Filters](/documentation/command_it/error_filters)
 
@@ -174,7 +174,7 @@ Most factory functions share these parameters:
 
 - **`errorFilter`/`errorFilterFn`** - Configure error handling strategy. See [Error Handling](/documentation/command_it/error_handling) and [Error Filters](/documentation/command_it/error_filters).
 
-- **`includeLastResultInCommandResults`** - When `true`, keeps previous result visible during execution. Useful for "refresh" scenarios where old data should remain visible while loading new data.
+- **`includeLastResultInCommandResults`** - When `true`, keeps previous result visible during execution and error states. See [Command Results - includeLastResultInCommandResults](/documentation/command_it/command_results#includelastresultincommandresults) for detailed explanation.
 
 - **`notifyOnlyWhenValueChanges`** - When `true`, only notifies listeners if the value actually changes. Default is to notify on every execution.