Build for Oruva
Add tools to Oruva's right-click menu with a local-first, out-of-process plugin model and an explicit trust boundary.
The API version describes the execution contract, bridge messages, placeholders, and local HTTP endpoints. The manifest schema describes the structure of plugin.json, including its required capabilities block. These are separate version numbers. The machine-readable contract is plugin_sdk/schema/plugin.schema.json inside the SDK.
An Oruva plugin adds actions to the assets in an Oruva library. When a user right-clicks an asset, your plugin's actions appear in the Plugins submenu; choosing one either runs your program directly or opens your action's optional interface.
Three principles shape the whole platform:
args and ui), and the hash of every file in the folder. Any change to any of those invalidates the approval automatically.Versioning promise
Plugin API v1 fields will not silently change meaning. New abilities such as actions[].ui and actions[].icon appear as optional fields; the structured capabilities object carries its own required version so that the capability contract can evolve without touching the manifest schema. Anything incompatible requires a new schema_version (as schema 2 did when it made capabilities required) or a new capability version. Version your own plugin semantically — the update badge users see is driven by your version field.