[transports] Evaluate the discovery HTTP server #77

Summary

The TypeScript SDK includes a DiscoveryHttpServer implementation that binds a preferred port and can retry on subsequent ports when the preferred port is already in use.

The Python SDK currently has port-selection logic in the CLI, but it is not clear whether the TypeScript DiscoveryHttpServer functionality is required, already covered, or intentionally omitted.

This issue is for investigation and documentation rather than implementation.

Reference

TypeScript:

• ts:core/transports/discovery-http-server.ts
  • port
  • autoRetry
  • maxRetries

Python:

• nitrostack/cli/main.py
  • _resolve_runtime_ports
  • _normalize_port

Task

Find what consumes this server in the TypeScript stack (CLI, Studio), and whether Python's dev flow already covers it. Then either close this with the reasoning, or open an implementation issue with a scope.

Acceptance criteria

• Consumers of DiscoveryHttpServer in the TypeScript stack are identified and documented.
• The current Python behavior is documented using code references.
• A comparison between TypeScript and Python is included.
• The issue ends with a clear written conclusion.