feat(runner): add debug flag to cargo runner

[ZR233]

Add a new --debug flag to control debug behavior independently from --no-run. This separates the debugging functionality from the no-run option, allowing users to debug while still running the application. The --no-run flag now exits early without running the application, while --debug enables debug output and passes the debug flag to the underlying cargo command.

[Copilot]

Pull request overview

This PR separates debug functionality from the --no-run flag by introducing a dedicated --debug flag. Previously, the --no-run flag controlled both execution stopping and debug mode; now --no-run exits early without running the application, while --debug independently controls debug behavior for building and running.

• Added a new --debug command-line flag to cargo-osrun
• Modified --no-run to exit immediately without executing the application
• Updated app.debug assignment from args.no_run to args.debug

Reviewed changes

Copilot reviewed 2 out of 4 changed files in this pull request and generated 1 comment.

File	Description
ostool/src/bin/cargo-osrun.rs	Adds --debug flag, implements early exit for --no-run, and updates debug output formatting
ostool/src/build/cargo_builder.rs	Adds is_run() helper method and logic to pass debug flag to cargo command
ostool/Cargo.toml	Bumps version from 0.8.5 to 0.8.6
Cargo.lock	Updates version lock for ostool package to 0.8.6

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

The --debug flag is not a valid cargo command-line option. Cargo builds in debug mode by default and only accepts --release to build in release mode. The logic at lines 163-165 already handles this correctly by only adding --release when debug mode is disabled. Adding --debug here will cause cargo to fail with an "unrecognized option" error.

Suggested change

	if self.is_run() && self.ctx.debug {
	cmd.arg("--debug");
	}