-}
-```
-
-## Tasks
-
-- [ ] Identify all usages of `pack!` / `pack_structural!` / `pack_err_structural!` across the codebase, examples, and docs
-- [ ] Migrate internal usages to `#[derive(Grouped)]`
-- [ ] Remove the macro definitions and their re-exports
-- [ ] Update the docs / helpdoc examples that reference `pack!`
-- [ ] Update downstream feature docs (`structural_renderer` etc.) where `pack_structural!` was involved
-- [ ] Verify all tests pass
-
-## 🕘 Progress
-
-- [ ] In Progress
-- [ ] Complete
-
-
- Written by @Weicao-CatilGrass
-
diff --git a/docs/dev/pages/issues/t0_remove-parser-feature.md b/docs/dev/pages/issues/t0_remove-parser-feature.md
deleted file mode 100644
index 5c1cffd..0000000
--- a/docs/dev/pages/issues/t0_remove-parser-feature.md
+++ /dev/null
@@ -1,36 +0,0 @@
-[T0] Remove the parser Feature
-
- Breaking: retire the legacy argument parsing in favor of picker
-
-
-> [!NOTE]
->
-> This is a **Breaking Change** planned for Mingling 0.5.0.
-
-## Background
-
-In 0.3.0, Mingling introduced the `picker` feature, which provides more powerful parameter parsing capabilities. At that point, the original `parser` feature became inadequate.
-
-The `parser` feature was a temporary argument parsing solution created in the early stages of the project. While it can handle basic argument parsing tasks, its functionality is incomplete and has many limitations (see the [Picker2 issue](_add-picker2) for the full list).
-
-## Plan
-
-Completely remove the `parser` feature in 0.5.0. This will directly affect downstream users of the `parser` feature — they must migrate to `picker` (or handle parsing manually).
-
-## Tasks
-
-- [ ] Identify all usages of the `parser` feature across the codebase, examples, and docs
-- [ ] Migrate internal usages (tests, examples, dev-dependencies) to `picker`
-- [ ] Remove the `parser` feature from `mingling` and its dependency (`size`)
-- [ ] Remove parser-related modules and public API
-- [ ] Update docs and helpdoc examples
-- [ ] Note the downstream migration path in the changelog
-
-## 🕘 Progress
-
-- [ ] In Progress
-- [ ] Complete
-
-
- Written by @Weicao-CatilGrass
-
diff --git a/docs/dev/pages/issues/t0_remove-with-dispatcher.md b/docs/dev/pages/issues/t0_remove-with-dispatcher.md
deleted file mode 100644
index 8779d74..0000000
--- a/docs/dev/pages/issues/t0_remove-with-dispatcher.md
+++ /dev/null
@@ -1,35 +0,0 @@
-[T0] Remove with_dispatcher and with_dispatchers
-
- Breaking: make Dispatcher registration compile-time collected in all modes
-
-
-> [!NOTE]
->
-> This is a **Breaking Change** planned for Mingling 0.5.0.
-
-## Background
-
-Mingling's commands must be registered through `with_dispatcher` in order to be usable when `dispatcher_tree` is disabled. This has always been a strange semantic: `chain`, `renderer`, `help`, `completion`, and `metadata` are all collected at compile time, so why is `Dispatcher` the exception?
-
-In fact, during usage of `dispatcher` from 0.1.0 to 0.4.0, no scenario has ever been encountered where **dynamic registration** was necessary. It is considered unnecessary.
-
-## Plan
-
-Make `Dispatcher` registration also compile-time collected in non-`dispatcher_tree` states starting from 0.5.0, and remove `with_dispatcher` / `with_dispatchers` (and the related `#[program_setup]` registration path if it becomes obsolete).
-
-## Tasks
-
-- [ ] Design how dispatchers are collected at compile time when `dispatcher_tree` is disabled (consistent with how `chain` / `renderer` / `completion` / `metadata` are collected)
-- [ ] Remove `with_dispatcher` and `with_dispatchers` from the `Program` API
-- [ ] Update `gen_program!` and the macros so registration happens automatically
-- [ ] Migrate examples, tests, and docs that call `with_dispatcher` / `with_dispatchers`
-- [ ] Verify both `dispatcher_tree`-enabled and disabled modes behave identically
-
-## 🕘 Progress
-
-- [ ] In Progress
-- [ ] Complete
-
-
- Written by @Weicao-CatilGrass
-
diff --git a/docs/dev/pages/issues/t1_modify-dispatcher-syntax.md b/docs/dev/pages/issues/t1_modify-dispatcher-syntax.md
deleted file mode 100644
index f1a9346..0000000
--- a/docs/dev/pages/issues/t1_modify-dispatcher-syntax.md
+++ /dev/null
@@ -1,44 +0,0 @@
-[T1] Modify the dispatcher! Syntax
-
- Breaking: drop the CMD* struct from the explicit form of dispatcher!
-
-
-> [!NOTE]
->
-> This is a **Breaking Change** planned for Mingling 0.5.0, and it depends on [Remove with_dispatcher and with_dispatchers](t0_remove-with-dispatcher).
-
-## Background
-
-Once `Dispatcher` registration is compile-time collected (see [Remove with_dispatcher and with_dispatchers](t0_remove-with-dispatcher)), the `CMD*` struct becomes unnecessary — it only existed to give `with_dispatcher` something to register.
-
-## Plan
-
-Simplify the `dispatcher!` syntax: the explicit form no longer creates a `CMD*` struct, so only the entry type needs to be given.
-
-```rust
-// Before
-dispatcher!("command", CMDCommand => EntryCommand);
-
-// After
-dispatcher!("command", EntryCommand);
-
-// NOTE: The implicit mode is not affected
-```
-
-## Tasks
-
-- [ ] Update `dispatcher!` to accept the simplified explicit form (`"name", EntryType`)
-- [ ] Decide whether the old `CMDType => EntryType` form should error with a helpful message or be removed outright
-- [ ] Remove the generated `CMD*` struct machinery
-- [ ] Update `#[command]` macro internals that depend on `CMD*`
-- [ ] Migrate examples, tests, and docs
-- [ ] Keep the implicit mode (`dispatcher!("name")`) working unchanged
-
-## 🕘 Progress
-
-- [ ] In Progress
-- [ ] Complete
-
-
- Written by @Weicao-CatilGrass
-
--
cgit