Route WSL Lavish sessions through Windows runtime

[Ikha14]

Summary

• reconstruct the eight accepted commits from Route WSL Lavish sessions through Windows runtime #2815 on a clean branch
• preserve WSL-to-Windows Lavish lifecycle routing and PowerShell 5.1 argv handling
• restore the prior valid process-event registration when legacy poll replacement publication fails

Tests

• bash tests/fm-lavish-route.test.sh
• bash tests/fm-lavish-windows-argv.test.sh
• bash tests/fm-procevent.test.sh
• bin/fm-lint.sh
• git diff --check

[greptile-apps]

Confidence Score: 3/5

The PR should not merge until server identity is validated before suppressing startup and registration upgrades preserve or roll back bindings atomically.

A fixed-port collision can prevent every routed WSL lifecycle operation from reaching the intended server, and a binding-restoration failure can leave an upgraded persistent poll active without an answer destination.

Files Needing Attention: bin/fm-lavish-windows.ps1, bin/fm-procevent-lavish.sh

_{Reviews (1): Last reviewed commit: "fix(lavish): restore legacy poll after f..." | Re-trigger Greptile}

[greptile-apps]

Foreign listener bypasses startup

If another Windows process is listening on 127.0.0.1:4388, Ensure-LavishServer accepts the TCP connection without verifying the listener and skips starting Lavish, causing routed open, poll, end, export, and share operations to fail against the wrong process.

[greptile-apps]

Binding failure loses rollback state

When replacement registration succeeds but restore_binding fails, this branch has already deleted the backup and exits with the routed poll registered but unbound, so completed captain answers cannot reach the keyed-answer intake and the previous registration cannot be restored.