Update copilot-instructions: API design rules from PR #305 review

[rmarinho]

Summary

Add three rules to .github/copilot-instructions.md learned from PR #305 (AdbRunner reverse port forwarding) review feedback by @jonathanpeppers:

1. Strongly-typed APIs over strings — use record/enum pairs (e.g. AdbPortSpec(AdbProtocol.Tcp, 5000)) instead of raw strings like "tcp:5000"
2. Avoid convenience overloads — don't add string, int, and typed overloads for the same method. Pick one.
3. Include stdout in error diagnostics — pass both stdout and stderr to ProcessUtils.ThrowIfFailed when available

These patterns keep the API surface small, type-safe, and debuggable.

[Copilot]

Pull request overview

Updates the repository’s Copilot guidance to capture API design patterns learned during the PR #305 review, helping keep new Android-tools APIs small, type-safe, and easier to debug.

Changes:

• Add guidance to prefer strongly-typed API parameters (record/enum) over string “spec” parameters.
• Add guidance to avoid “convenience overload” proliferation (string/int/typed variants).
• Add guidance to include stdout (when captured) in ProcessUtils.ThrowIfFailed diagnostics.

---

You can also share your feedback on Copilot code review. Take the survey.

[rmarinho]

Summary

Add three rules to .github/copilot-instructions.md learned from PR #305 (AdbRunner reverse port forwarding) review feedback by @jonathanpeppers:

1. Strongly-typed APIs over strings — use record/enum pairs (e.g. AdbPortSpec(AdbProtocol.Tcp, 5000)) instead of raw strings like "tcp:5000"
2. Avoid convenience overloads — don't add string, int, and typed overloads for the same method. Pick one.
3. Include stdout in error diagnostics — pass both stdout and stderr to ProcessUtils.ThrowIfFailed when available

These patterns keep the API surface small, type-safe, and debuggable.

[Copilot]

Pull request overview

Updates the repository’s Copilot guidance to capture API design patterns learned during the PR #305 review, helping keep new Android-tools APIs small, type-safe, and easier to debug.

Changes:

• Add guidance to prefer strongly-typed API parameters (record/enum) over string “spec” parameters.
• Add guidance to avoid “convenience overload” proliferation (string/int/typed variants).
• Add guidance to include stdout (when captured) in ProcessUtils.ThrowIfFailed diagnostics.

---

You can also share your feedback on Copilot code review. Take the survey.

[rmarinho]

Summary

Add three rules to .github/copilot-instructions.md learned from PR #305 (AdbRunner reverse port forwarding) review feedback by @jonathanpeppers:

1. Strongly-typed APIs over strings — use record/enum pairs (e.g. AdbPortSpec(AdbProtocol.Tcp, 5000)) instead of raw strings like "tcp:5000"
2. Avoid convenience overloads — don't add string, int, and typed overloads for the same method. Pick one.
3. Include stdout in error diagnostics — pass both stdout and stderr to ProcessUtils.ThrowIfFailed when available

These patterns keep the API surface small, type-safe, and debuggable.

[Copilot]

Pull request overview

Updates the repository’s Copilot guidance to capture API design patterns learned during the PR #305 review, helping keep new Android-tools APIs small, type-safe, and easier to debug.

Changes:

• Add guidance to prefer strongly-typed API parameters (record/enum) over string “spec” parameters.
• Add guidance to avoid “convenience overload” proliferation (string/int/typed variants).
• Add guidance to include stdout (when captured) in ProcessUtils.ThrowIfFailed diagnostics.

---

You can also share your feedback on Copilot code review. Take the survey.

[rmarinho]

Summary

Add three rules to .github/copilot-instructions.md learned from PR #305 (AdbRunner reverse port forwarding) review feedback by @jonathanpeppers:

1. Strongly-typed APIs over strings — use record/enum pairs (e.g. AdbPortSpec(AdbProtocol.Tcp, 5000)) instead of raw strings like "tcp:5000"
2. Avoid convenience overloads — don't add string, int, and typed overloads for the same method. Pick one.
3. Include stdout in error diagnostics — pass both stdout and stderr to ProcessUtils.ThrowIfFailed when available

These patterns keep the API surface small, type-safe, and debuggable.

[Copilot]

Pull request overview

Updates the repository’s Copilot guidance to capture API design patterns learned during the PR #305 review, helping keep new Android-tools APIs small, type-safe, and easier to debug.

Changes:

• Add guidance to prefer strongly-typed API parameters (record/enum) over string “spec” parameters.
• Add guidance to avoid “convenience overload” proliferation (string/int/typed variants).
• Add guidance to include stdout (when captured) in ProcessUtils.ThrowIfFailed diagnostics.

---

You can also share your feedback on Copilot code review. Take the survey.

[rmarinho]

Summary

Add three rules to .github/copilot-instructions.md learned from PR #305 (AdbRunner reverse port forwarding) review feedback by @jonathanpeppers:

1. Strongly-typed APIs over strings — use record/enum pairs (e.g. AdbPortSpec(AdbProtocol.Tcp, 5000)) instead of raw strings like "tcp:5000"
2. Avoid convenience overloads — don't add string, int, and typed overloads for the same method. Pick one.
3. Include stdout in error diagnostics — pass both stdout and stderr to ProcessUtils.ThrowIfFailed when available

These patterns keep the API surface small, type-safe, and debuggable.

[Copilot]

Pull request overview

Updates the repository’s Copilot guidance to capture API design patterns learned during the PR #305 review, helping keep new Android-tools APIs small, type-safe, and easier to debug.

Changes:

• Add guidance to prefer strongly-typed API parameters (record/enum) over string “spec” parameters.
• Add guidance to avoid “convenience overload” proliferation (string/int/typed variants).
• Add guidance to include stdout (when captured) in ProcessUtils.ThrowIfFailed diagnostics.

---

You can also share your feedback on Copilot code review. Take the survey.

[rmarinho]

Summary

Add three rules to .github/copilot-instructions.md learned from PR #305 (AdbRunner reverse port forwarding) review feedback by @jonathanpeppers:

1. Strongly-typed APIs over strings — use record/enum pairs (e.g. AdbPortSpec(AdbProtocol.Tcp, 5000)) instead of raw strings like "tcp:5000"
2. Avoid convenience overloads — don't add string, int, and typed overloads for the same method. Pick one.
3. Include stdout in error diagnostics — pass both stdout and stderr to ProcessUtils.ThrowIfFailed when available

These patterns keep the API surface small, type-safe, and debuggable.

[Copilot]

Pull request overview

Updates the repository’s Copilot guidance to capture API design patterns learned during the PR #305 review, helping keep new Android-tools APIs small, type-safe, and easier to debug.

Changes:

• Add guidance to prefer strongly-typed API parameters (record/enum) over string “spec” parameters.
• Add guidance to avoid “convenience overload” proliferation (string/int/typed variants).
• Add guidance to include stdout (when captured) in ProcessUtils.ThrowIfFailed diagnostics.

---

You can also share your feedback on Copilot code review. Take the survey.

[rmarinho]

Summary

Add three rules to .github/copilot-instructions.md learned from PR #305 (AdbRunner reverse port forwarding) review feedback by @jonathanpeppers:

1. Strongly-typed APIs over strings — use record/enum pairs (e.g. AdbPortSpec(AdbProtocol.Tcp, 5000)) instead of raw strings like "tcp:5000"
2. Avoid convenience overloads — don't add string, int, and typed overloads for the same method. Pick one.
3. Include stdout in error diagnostics — pass both stdout and stderr to ProcessUtils.ThrowIfFailed when available

These patterns keep the API surface small, type-safe, and debuggable.

[Copilot]

Pull request overview

Updates the repository’s Copilot guidance to capture API design patterns learned during the PR #305 review, helping keep new Android-tools APIs small, type-safe, and easier to debug.

Changes:

• Add guidance to prefer strongly-typed API parameters (record/enum) over string “spec” parameters.
• Add guidance to avoid “convenience overload” proliferation (string/int/typed variants).
• Add guidance to include stdout (when captured) in ProcessUtils.ThrowIfFailed diagnostics.

---

You can also share your feedback on Copilot code review. Take the survey.

[rmarinho]

Summary

Add three rules to .github/copilot-instructions.md learned from PR #305 (AdbRunner reverse port forwarding) review feedback by @jonathanpeppers:

1. Strongly-typed APIs over strings — use record/enum pairs (e.g. AdbPortSpec(AdbProtocol.Tcp, 5000)) instead of raw strings like "tcp:5000"
2. Avoid convenience overloads — don't add string, int, and typed overloads for the same method. Pick one.
3. Include stdout in error diagnostics — pass both stdout and stderr to ProcessUtils.ThrowIfFailed when available

These patterns keep the API surface small, type-safe, and debuggable.

[Copilot]

Pull request overview

Updates the repository’s Copilot guidance to capture API design patterns learned during the PR #305 review, helping keep new Android-tools APIs small, type-safe, and easier to debug.

Changes:

• Add guidance to prefer strongly-typed API parameters (record/enum) over string “spec” parameters.
• Add guidance to avoid “convenience overload” proliferation (string/int/typed variants).
• Add guidance to include stdout (when captured) in ProcessUtils.ThrowIfFailed diagnostics.

---

You can also share your feedback on Copilot code review. Take the survey.