jac-sv-endpoints

Define a `walker:pub` with `has` fields as the request body and use `report` for the response, or define a `def:pub` function whose typed return value becomes the wire format. Call walkers at `POST /walker/<name>` and functions at `POST /function/<name>`.

Use `def:pub` when the endpoint does not traverse the graph: status probes, single-node CRUD, list queries, and job kick-offs. Reserve `walker:pub` for endpoints that spawn, visit edges, accumulate results, and report once.

Apply `@restspec(method=HTTPMethod.GET, path="/users/{user_id}/orders")` to a walker or function. Parameters matching `{...}` in the path become path parameters, `UploadFile` fields become file uploads, and remaining fields become query or body parameters.

The endpoint name is missing from the entry module's import list. Adding a `def:pub` to an already-imported module still fails until the new name is explicitly imported in the entry module.

Import `UploadFile` from `http`, declare a `has file: UploadFile` field on the walker, and it is classified as a multipart file parameter. Use the ambient `store()` builtin to save the file to local disk or S3 backends.

The runtime assigns a fresh `_jac_id` to the walker instance and every freshly-constructed report object on each response, while persistent node jids stay stable. Strip `_jac_id` before hashing, caching, or diffing responses.