jac-sv-microservices

Use `sv import from <module> { ... }` between two server modules. The compiler generates HTTP client stubs, so calling a remote function looks like a normal import while the call executes as a POST against the provider's URL.

Discovery follows a chain: registered test clients, programmatically registered URLs, the JAC_SV_<UPPERCASED_MODULE>_URL environment variable, then auto-spawn of the provider as a sibling process at jac start time.

The provider symbol is not declared pub. Only def:pub functions and walker:pub walkers are callable across the service boundary; plain or priv endpoints are JWT-gated and anonymous sv-to-sv hops carry no token.

Yes, importing a walker:pub via sv import spawns and executes it remotely on construction. The returned instance already has reports populated; there is no unexecuted remote walker, and browser clients cannot use this.

obj types (recursively hydrated), enums by name, primitives, lists, dicts, None, and live streaming generators cross the wire. Node anchors, closures, and file handles do not; pass jid strings and re-resolve with jobj instead.

Auto-spawn requires the provider .jac file and a jac.toml in the directory where jac start runs, binds siblings to 127.0.0.1 on ports 18000-18999, and fails fast after roughly 15 seconds of health-check waiting. Set JAC_SV_<MOD>_URL explicitly to bypass it.