[WIP] Investigate Roku device discovery and connectivity issues

[Copilot]

• Add RokuEcpError class with error kind classification (unreachable | invalid-ecp | http-error) to roku.ts
• Update fetchDeviceInfo to throw typed RokuEcpError so callers can distinguish timeout/network failures from invalid ECP responses
• Add XML root-element validation to fetchApps (ensure <apps> root) for consistency with fetchDeviceInfo
• Show specific, kind-aware error messages in SettingsView.tsx handleAddDevice
• Fix scan-progress accumulation bug in App.tsx (multi-subnet progress counter was overwritten each subnet instead of accumulated)
• Add probe_port Tauri/Rust command in main.rs for TCP port-8060 reachability diagnostics
• Type-check after all changes

Original prompt

The user encountered the following error: 'Could not reach a Roku device at 192.168.1.83. Verify the IP and that port 8060 is reachable.' Please investigate the Roku device discovery and connectivity logic for situations where port 8060 is unreachable or the device does not respond. Validate appropriate error detection and user-facing feedback. Repository: lumenhelixsolutions/NUMO-Roku-Portal-v2. Branch: main.

The following is the prior conversation context from the user's chat exploration (may be truncated):

User: @copilot Accepted Confirmation: Confirm agent session

Assistant: Because I kept carrying forward the wrong repo context from earlier turns, and that was my mistake.

The correct repository is lumenhelixsolutions/NUMO-Roku-Portal-v2. I’ll use that going forward and stop targeting hailstone-v.2.

User: OK now generate me a correct session for my agent in the right repo

User: @copilot Accepted Confirmation: Confirm agent session

Assistant: I can’t generate the session from here right now.

If you want to continue in the correct repo, use:

• Repository: lumenhelixsolutions/NUMO-Roku-Portal-v2
• Branch: main

If you paste the new session prompt you want, I can help you word it correctly for that repo.

User: This one that you started in the wrong repo is what you should be finishing in the correct repo

Assistant: Acknowledged — I’ll treat that as the task to continue in the correct repo context:

• Repo: lumenhelixsolutions/NUMO-Roku-Portal-v2
• Branch: main
• Goal: finish the Roku discovery + Rust diagnostics fix in the right repository

If you want, I can next help you restate the task clearly so it won’t get routed to hailstone-v.2 again.

User: @copilot Accepted Confirmation: Confirm agent session

Assistant: I can’t start or finish that session from here right now.

The correct repo context is:

• lumenhelixsolutions/NUMO-Roku-Portal-v2
• branch main

And the task to continue is:

• Roku device discovery
• Rust diagnostics

If you want, I can help you write the exact agent prompt so it stays in the correct repo and doesn’t get routed to hailstone-v.2 again.

User: Fix Roku device discovery: ECP XML validation, deduplication, and scan state reset too

Assistant: Understood — I’ll treat this as the correct task for lumenhelixsolutions/NUMO-Roku-Portal-v2 on main.

Requested focus:

• ECP XML validation
• deduplication
• scan state reset

If you want, I can also help turn this into a tighter implementation checklist before you run it.

User: add:
Roku device discovery
Rust diagnostics

User: @copilot Accepted Confirmation: Confirm agent session

Assistant: Added to the task scope:

• Roku device discovery
• Rust diagnostics

So the current focus is now:

• ECP XML validation
• deduplication
• scan state reset
• Roku device discovery
• Rust diagnostics

User: @copilot Accepted Confirmation: Confirm agent session

Assistant: I can’t start a new agent session from here right now.

For the correct repo, use:

• lumenhelixsolutions/NUMO-Roku-Portal-v2
• branch main

And the task scope you asked for is:

• Roku device discovery
• Rust diagnostics

If you want, I can help you draft the exact session prompt so it stays in the right repo.

User: Could not reach a Roku device at 192.168.1.83. Verify the IP and that port 8060 is reachable.

Assistant: I've logged your issue:
"Could not reach a Roku device at 192.168.1.83. Verify the IP and that port 8060 is reachable."
I am now investigating the Roku device connectivity and port 8060 reachability logic in lumenhelixsolutions/NUMO-Roku-Portal-v2 on main.

User: @copilot Accepted Confirmation: Confirm agent session

Assistant: A new agent session is being started to investigate unreachable Roku devices and port 8060 error handling in lumenhelixsolutions/NUMO-Roku-Portal-v2.

You can track all details and progress in the agent session; let me know if you want the link or status updates.

This pull request was created from Copilot chat.