What
Plugins now expose their version as declared in plugin.json through the SDK wire format.
Details
- The version string is emitted verbatim from the plugin manifest (plugin-author-controlled — validate before trusting)
- Omitted when the manifest declares no version
- The
versionfield appears in thepluginsarray in two SDK message types: thesystem:initmessage (sent at session startup listing all loaded plugins) and thereload_pluginsengine-control response (sent after a plugin reload) - In both locations the field is typed as
S.string().optional(), so hosts must handle its absence for plugins that omit aversionin their manifest - A separate
plugin_versionattribute is also recorded in telemetry events for marketplace-approved plugins when a skill command is invoked, enabling per-version usage metrics on the server side; third-party plugins emit"third-party"as the repository sentinel and no version is sent to telemetry
Evidence
Schema addition (search for "The plugin's version as declared in its plugin.json manifest, emitted verbatim"); wire positions (search for u7a used in system:init plugins array and reload_plugins response schema)
Strings lifted out of the shipped bundle, so the claim above can be checked against them.