Use idiomatic Effect parsing and timeouts

[cursor]

What Changed

• Converted the Tailscale integration errors to Schema.TaggedErrorClass and replaced millisecond timeout constants with Duration values.
• Added a Tailscale timeout test using TestClock with the mocked ChildProcessSpawner.
• Reworked Windows process diagnostics JSON handling to decode via Schema.fromJsonString and per-record Schema validation instead of JSON.parse and ad-hoc record probing.

Why

These are small, focused Effect idiom improvements that make error data serializable, timeout behavior testable, and JSON boundary parsing schema-driven while preserving current behavior.

UI Changes

Not applicable.

Checklist

• This PR is small and focused
• I explained what changed and why
• I included before/after screenshots for any UI changes
• I included a video for animation/interaction changes

  

Note

Replace millisecond number constants with Duration values and add schema-based Windows process parsing

• Replaces numeric timeout constants with Duration values in both tailscale.ts and ProcessDiagnostics.ts, and updates all Effect.timeoutOption calls accordingly.
• Adds a WindowsProcessRecord schema to ProcessDiagnostics.ts with decodeWindowsProcessJson/decodeWindowsProcessRecord helpers; parseWindowsProcessRows now uses schema decoding and is exported.
• Converts TailscaleCommandError, TailscaleStatusParseError, and TailscaleUnavailableError from Data.TaggedError to Schema.TaggedErrorClass with typed field schemas.
• Risk: probeTailscaleHttpsEndpoint callers must now pass timeout: Duration.Duration instead of timeoutMs: number; passing timeoutMs is silently ignored and the default timeout applies.

^{Macroscope summarized d6bbc5a.}