fix Deno serve registration ordering

[momics]

Summary

• preserve JS call order across Deno’s asynchronous serveStart bridge so immediate self-fetch observes the server just started
• order immediate stop and endpoint close behind registration, and drain tracked stop ops before lifecycle completion
• make the shared stale-handle assertion portable to Tauri’s scalar equality helper without weakening the check

Failures addressed

Exact-SHA Extended Tests on 193a6ff found:

• Deno: node can fetch its own node id while serving failed because fetch overtook native serve registration
• Tauri: the stale-handle stress assertion compared two distinct arrays under a scalar-only harness, so an empty error list falsely failed

Node passed that same run.

Validation

• full rebuilt Deno suite: 88/88, twice
• immediate Deno self-fetch stress: 25/25
• Deno serve/lifecycle focus with op sanitizers: 14/14
• Tauri guest tests: 86/86
• all workspace TypeScript typechecks
• Deno check and configured fmt check
• two independent lifecycle reviews: clean