docs: cross-reference invoke callback group in actions.md

Author: fgmacedo

docs/actions.md

@@ -160,6 +160,22 @@ It's also possible to use an event name as action.
 
 ```
 
+### Invoke actions
+
+States can also declare **invoke** callbacks — background work that is spawned when the
+state is entered and cancelled when it is exited. Like `enter` and `exit`, invoke supports
+all three binding patterns:
+
+- **Naming convention:** `on_invoke_<state_id>()`
+- **Inline parameter:** `State(invoke=callable)`
+- **Decorator:** `@state.invoke`
+
+```{seealso}
+Invoke handlers run outside the main processing loop (in threads or executors) and have
+their own completion and error events. See {ref}`invoke` for the full execution model,
+cancellation semantics, and advanced patterns like `IInvoke` and `invoke_group`.
+```
+
 ## Transition actions
 
 For each {ref}`events`, you can register `before`, `on`, and `after` callbacks.
@@ -374,6 +390,10 @@ Actions registered on the same group don't have order guaranties and are execute
     - `on_enter_state()`, `on_enter_<state.id>()`
     - `destination`
     - Callbacks declared in the destination state.
+*   - Invoke
+    - `on_invoke_state()`, `on_invoke_<state.id>()`
+    - `destination`
+    - Background work spawned after entering the state. See {ref}`invoke`.
 *   - After
     - `after_<event>()`, `after_transition()`
     - `destination`

docs/invoke.md

@@ -28,6 +28,10 @@ Invoke is a first-class callback group, just like `enter` and `exit`. This means
 convention naming (`on_invoke_<state>`), decorators (`@state.invoke`), inline callables,
 and the full {ref}`SignatureAdapter <actions>` dependency injection all work out of the box.
 
+See the {ref}`actions` page for how invoke fits into the overall
+callback {ref}`Ordering` and the available
+{ref}`dependency injection <dynamic-dispatch>` parameters.
+
 ## Quick start
 
 The simplest invoke is a plain callable passed to the `invoke` parameter. Here we read a
@@ -73,7 +77,8 @@ keyword argument in callbacks on the target state.
 
 ## Naming conventions
 
-Like `on_enter_<state>` and `on_exit_<state>`, invoke supports naming conventions:
+Like `on_enter_<state>` and `on_exit_<state>`, invoke supports naming conventions
+(see {ref}`State actions` for the general pattern):
 
 - `on_invoke_state` — generic, called for every state with invoke
 - `on_invoke_<state_id>` — specific to a state
@@ -108,7 +113,8 @@ True
 
 ## Decorator syntax
 
-Use the `@state.invoke` decorator:
+Use the `@state.invoke` decorator (same pattern as `@state.enter` and `@state.exit` —
+see {ref}`Bind state actions using decorator syntax`):
 
 ```py
 >>> config_file = Path(tempfile.mktemp(suffix=".txt"))