simulo asset validate

Validate without publishing: a local tree runs a real cloud dry-run validation (same validator as publish, nothing published), or revalidate a published ref on a runtime (–runtime; new validation record, never a new version).

usage: simulo asset validate [-h] [--kind {robot,world,prop}] [--name NAME] [--entry FILE]
                             [--root DIR] [--base {fixed,floating}] [--report PATH] [--json]
                             [--runtime ALIAS]
                             target

Arguments

Argument	Description
TARGET	A local package tree/file to dry-run validate in the cloud, or a published ref (e.g. robot/forklift:v1).

Options

Option	Description
--kind {robot,world,prop}	Asset kind — selects the validation profile; never guessed. One of: robot, world, prop.
--name NAME	Asset name slug (default: the slugified entry-file or directory name, echoed back).
--entry FILE	Package-root-relative entry file — required only when auto-detection is ambiguous.
--root DIR	Package root — the explicit security and portability boundary: dependencies are collected beneath it and never from elsewhere on this machine.
--base {fixed,floating}	Robot base mode: fixed (bolted down — manipulators) or floating (mobile/legged). URDF cannot express this; default for URDF robots is fixed, always echoed. One of: fixed, floating.
--report PATH	Write the validation (or local packaging) report JSON to PATH.
--json	Print a machine-readable JSON result on stdout (progress lines go to stderr).
--runtime ALIAS	Revalidate a PUBLISHED ref on this runtime (omit for the platform default).