Enforce MacosNative app config validation with pattern matching

[Miyamura80]

Summary

Refactored the MacosNative app configuration validation to use exhaustive pattern matching instead of runtime checks, making invalid configurations impossible to construct.

Key Changes

• Modified the validate_app_config function to pattern match on MacosNative { bundle_id: None, app_path: None } directly
• Removed the conditional if bundle_id.is_none() && app_path.is_none() check
• Now the validation error is returned unconditionally when both fields are None, as this is the only case the pattern matches

Implementation Details

This change leverages Rust's pattern matching to make the validation more explicit and type-safe. By matching on the specific case where both bundle_id and app_path are None, the code makes it clear that this is an invalid configuration state. The error is now returned directly rather than being conditional, improving code clarity and reducing the possibility of logic errors.

https://claude.ai/code/session_01JeA7bssA8UsoiQXhRBxGnV

---

Summary by cubic

Refactors MacosNative app config validation to match on the exact invalid state (both bundle_id and app_path are None) and return the error directly. Removes the inner conditional, keeps behavior the same (still requires at least one value), and satisfies clippy::collapsible_match.

^{Written for commit 23a4732. Summary will update on new commits.}

[qodo-code-review]

ⓘ You've reached your Qodo monthly free-tier limit. Reviews pause until next month — upgrade your plan to continue now, or link your paid account if you already have one.

[cubic-dev-ai]

No issues found across 1 file

Confidence score: 5/5

• Automated review surfaced no issues in the provided summaries.
• No files require special attention.

_{Tip: cubic could auto-approve low-risk PRs like this, if it thinks it's safe to merge. Learn more}