[fjtrujy]

Summary

• Add an opt-in host-only resetcheck command without changing the existing reset command or PS2Link wire protocol.
• Require a successful EE/IOP host: round trip before sending a single UDP reset; fail closed when the EE is unreachable.
• Observe an offline/online round-trip transition within a bounded timeout (default 10 seconds), without claiming this proves a reset.
• Run each probe in a separate host client process to avoid changing existing socket and thread lifecycles.

Why

Legacy ps2client reset exits successfully as soon as the UDP send succeeds. During EE level-2 exception hangs, the IOP cannot get the EE command thread to execute the reset, yet the host still reports success.

Validation

• Clean native build with -Wall -Wextra -Werror.
• make check: simulated outage/recovery, no outage, permanent outage, unreachable EE with zero reset packets, and invalid syntax.
• Windows smoke tests and Makefile integration included; CI validates native Windows builds.

Compatibility and limitations

• No PS2Link ELF or IRX update is required; uses existing protocol.
• A fast reset can evade outage sampling. Unrelated network loss/recovery can resemble reboot. The command reports only the observed round-trip state, not a verified EE reset.
• This does not provide out-of-band recovery for a stuck EE.
• Hardware reset is never performed by automated tests.