refactor!: replace build.rs with compile-time macro build steps

BREAKING CHANGE: Replace the `build`/`builds` feature system with
compile-time macro-driven generation. `gen_program!()` now automatically
invokes `build_comp!()` and `build_pathf!()` when the `comp`/`pathf`
features are enabled, eliminating the need for `build.rs` and
`[build-dependencies]` blocks.

This removes the `build` feature, the `mingling::build` module, and all
related build-time API functions. Completion scripts are now written to
`{target_directory}/mingling/` instead of `target/release/`. The
`mingling_cli` uses `build_comp!("mling")` for its custom binary name.

1 files changed, 11 insertions, 8 deletions

diff --git a/docs/pages/advanced/1-completion.md b/docs/pages/advanced/1-completion.md
index 20bd59e..ca1f621 100644
--- a/docs/pages/advanced/1-completion.md
+++ b/docs/pages/advanced/1-completion.md
@@ -11,13 +11,6 @@ Mingling's completion is **fully dynamic** — no static completion files, sugge
 # Cargo.toml
 [dependencies.mingling]
 features = ["comp"]
- 
-[build-dependencies.mingling]
-features = [
-    "comp",
-    # Enable `build` for build-time support
-    "build"
-]
 ```
  
 ## How it works
@@ -72,8 +65,18 @@ suggest! {
 
 ## Generate completion scripts
 
-Call `build_comp_scripts` in `build.rs` to generate completion scripts (requires `builds` + `comp` features).
+When the `comp` feature is enabled, `gen_program!()` automatically invokes `build_comp!()` at compile time, which generates the completion scripts (named after `CARGO_PKG_NAME`) into `target/mingling/`.
+
+If your binary name differs from the crate name, call `build_comp!()` manually with the binary name:
 
+```rust
+// Features: ["comp"]
+@@@use mingling::macros::build_comp;
+@@@fn example() {
+build_comp!("mybin");
+@@@}
+```
+ 
 See [example-completion](https://mingling-rs.github.io/mingling/docs/example-viewer.html?name=example-completion).
 
 <p align="center" style="font-size: 0.85em; color: gray;">