Register machine routes in one place

[SaladDay]

Machine routes were split between the API, server mux and Runtime gateway, with different HTTP error bodies and incomplete generated documentation. Register every /api/v1 route once in the API, inject the existing transport handlers, and return the shared error envelope from authentication, routing, WebSocket handshakes and native downloads. Publish the existing HTTP operations in the machine schema and correct the proxy documentation.

Preserve credential checks and their order, connection authority rechecks, canonical paths, standard method/HEAD behavior, prefix redirects, successful downloads, range/conditional requests and cache headers. The public and administration schemas remain unchanged. Remove the separate server/gateway registrations and forwarding handler. Undeclared extension methods use the common router’s 405 rejection before authentication or upgrade.

Validation: 745 database integration cases with no skips; 2,282 focused cases with four platform/external-environment skips; additional HTTP/auth/path/download/schema checks, module build/vet, generation freshness and 22 website checks. Rebase validation passed 81 focused cases and 16 generator cases. No native execution behavior changed or live model qualification was run.

Fresh independent review and focused follow-up review found no remaining issues. The official-client check now verifies initial Session activity against its queued Turn, preserving exact replay/retrieve checks without assuming two database inserts occur within one second. A complete run against the pinned SDK and real service passed.