jac-sv-microservices

Use `sv import from <module> { ... }` in the consumer server module. The Jac compiler generates HTTP client stubs, so calling `add(1, 2)` issues a POST to the provider's `/function/add` endpoint while the source reads like a normal import.

Discovery follows a chain: registered test clients, programmatic `sv_client.register(module, url)`, 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`. Non-pub functions and walkers are not callable across the service boundary; the stub compiles fine but the call fails at runtime with an Unauthorized error.

Yes. Importing a `walker:pub` via sv import means constructing it spawns and executes it remotely. `Greet(name="x")` POSTs to `/walker/Greet` on the provider and returns the finished instance with reports populated.

The gateway's per-service `rpc_timeout` defaults to 10 seconds. For LLM-backed workers, set `rpc_timeout = 120.0` or higher under `[scale.microservices.services.NAME]` in jac.toml so long generations are not cut off.

obj types (recursively hydrated), enums, primitives, lists, dicts, None, and live streaming generators cross the wire. Node/edge anchors, closures, and file handles do not; pass `jid(node)` strings and re-resolve with `jobj` on the other side.