io.github.serionist/omniverse-mcp

New tools for long work and many pictures, and two changed defaults. `run_script_job`, `get_job` and `cancel_job` run a script for minutes while Kit keeps rendering; `capture_sweep` takes many shots, each with its own camera, lens, variant selections and time, as one job, with a manifest that takes them again; `get_performance` measures the frame rate; `set_prim_attribute` sets one attribute of a prim. `new_scene` now makes a Z-up stage in metres, and `set_variant_selection` switches in Kit's session layer, which no save writes: see Breaking changes. Most of it is in the Kit extension: run `uvx omniverse-mcp==0.5.0 extension install` (the plugin's `/omniverse-mcp:setup` does it) and restart Kit.

### Breaking changes

- **`new_scene` makes a Z-up stage in metres, and takes `up_axis` and `meters_per_unit`, a change to the tool contract:** it made a Y-up stage in the Kit app's units, where Isaac Sim's own new stage, its robots, SimReady assets and most robotics scenes are Z-up in metres, so an agent that started a robot scene got a frame it hadn't asked for. `new_scene(up_axis="Y")` makes the Y-up stage again, and `meters_per_unit=0.01` one in centimetres; the answer gives the stage's `up_axis` and `meters_per_unit` as read back. In a Kit app whose own stages are in centimetres, such as USD Composer, the viewport's camera stays placed for centimetres: `set_camera` places it. The change is in the Kit extension: run `uvx omniverse-mcp extension install`, then restart Kit; an older extension makes a Y-up stage whatever was asked, and the answer warns (#159).
- **`set_variant_selection` switches in Kit's session layer by default, a change to the tool contract:** a selection there shows at once and no save writes it, so a check that steps through a scene's variants leaves every file as it found it; `save_scene` names the session selections it left out. To keep a selection in the stage's file, pass `layer="edit_target"`, where every switch went before; it is refused while the session layer holds a selection for that set, which would hide it. `variant_name=""` now clears the layer's selection, so the files' own shows again. The answer says where the selection went and what the files select beneath it. The change is in the Kit extension: run `uvx omniverse-mcp extension install`, then restart Kit; an older extension still writes at the edit target, and the answer warns (#155).

### Added

- **`capture_sweep`, a new tool in the tool contract, with the route `/jobs/sweep` and the output folder's `sweeps/`:** one call captures a list of shots, each with its own camera pose (a position with a yaw and pitch, a target, or a camera of the stage), lens, variant selections and timeline time, as a job `get_job` reads and `cancel_job` cancels. A scene's check from 50 viewpoints through its switches, about 400 pictures, took one `capture_viewport` and one agent turn a picture. Kit writes the PNGs and a `manifest.json` of each shot's pose, lens, selections, time and file into `mcp_output/sweeps/<name>/`; `get_job` gives one line naming the folder and the shots that came out black or failed. Every shot is checked before anything changes, the selections are switched in Kit's session layer, and every layer and the timeline are as they were afterwards, after a cancel too. A sweep's `manifest.json` given as `shots_file` takes the same shots again, after a change or on a second scene. The sweep is in the Kit extension: run `uvx omniverse-mcp extension install`, then restart Kit; an older extension answers with that advice (#157).
- **Script jobs, three new tools in the tool contract:** `run_script_job` starts a long Python script inside the Kit app, given as code or as a `.py` file on Kit's machine, and answers its id at once; the job runs between Kit's updates, so Kit renders and other tools answer while it does. `get_job` reads its state, its time and the lines it printed since the last read, and once it ends its result or error, waiting up to 100 s for