refactor!: replace pack! macros with derive-based pipeline types

Remove the `pack!`, `pack_err!`, `pack_structural!`, and
`pack_err_structural!` macros, replacing all pipeline type definitions
with `#[derive(Grouped)]` and `#[derive(Grouped, Wrap)]` attributes.
This changes the generated struct shape from named-field structs with an
`inner` field to tuple structs accessed via `.0`, and removes the
auto-generated `name` and `info` fields from error types.

1 files changed, 4 insertions, 6 deletions

diff --git a/docs/pages/2-define-a-dispatcher.md b/docs/pages/2-define-a-dispatcher.md
index efd744d..5aafb19 100644
--- a/docs/pages/2-define-a-dispatcher.md
+++ b/docs/pages/2-define-a-dispatcher.md
@@ -48,17 +48,15 @@ You might be curious about what's inside `EntryGreet`. It's essentially a struct
 
 ```rust
 // Illustration of code generated by the dispatcher! macro
-pub struct EntryGreet {
-    pub inner: Vec<String>,
-}
+pub struct EntryGreet(pub Vec<String>);
 ```
  
-When the user types `greet Alice Bob` on the command line, `EntryGreet.inner` becomes `vec!["Alice", "Bob"]`.
+When the user types `greet Alice Bob` on the command line, `EntryGreet`'s `.0` becomes `vec!["Alice", "Bob"]`.
 
 > [!IMPORTANT]
-> Entry's `inner` only contains **the remaining args after matching**.
+> Entry's `.0` only contains **the remaining args after matching**.
 >
-> Take `remote add origin` as an example: `remote` and `add` are used for matching the command path, only `origin` goes into `EntryRemoteAdd.inner`.
+> Take `remote add origin` as an example: `remote` and `add` are used for matching the command path, only `origin` goes into `EntryRemoteAdd.0`.
 
 ## Advanced: Implicit Declaration