Fix binary auto-discovery to prefer package-named binary over first match

[Copilot]

When a Rust package defines multiple binary targets, the bundler was selecting the first binary from cargo metadata instead of the one matching the package name, violating Cargo conventions.

Changes

• Binary selection logic (scripts/bundle.sh:130-145)
  • Extract all binary targets in single jq call
  • Prefer binary matching package name via grep -x
  • Fall back to first binary if no package-named match exists

Example

For a package with multiple binaries:

[package]
name = "my-app"

[[bin]]
name = "utility"
path = "src/utility.rs"

[[bin]]
name = "my-app"
path = "src/main.rs"

Before: Selected utility (first in metadata)
After: Selects my-app (matches package name)

Original prompt

You are choosing the wrong binary in auto discovery, you are just using the first target with kind bin you can find, however the default target should be the one that has the same name as the package.

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.