v0.52.0

Release notes

0.52.0

Optional A2A input contracts from the entry stage schema, console publish/edit defaults, and safer A2A error handling.

Features

• Publish A2A pipelines without a separate schema file. input_schema is optional; when omitted, the contract is the pipeline entry stage's io.input.schema, which supports hosted workspaces where you cannot add files. Multi-entry pipelines still require a file (400 a2a_input_schema_multiple_entries). Set input_schema to null or "" to use the entry stage again. Entry-stage schema edits count as drift like other stage edits. See A2A.
• Console publish and edit dialogs use the entry stage schema. It is the default in the publish form; the edit dialog can switch between entry schema and a file. GET /api/a2a/pipeline-stages includes entry, so the form prompts for a file when a multi-entry pipeline is selected. See Console: A2A.

Fixes

• A2A errors no longer expose server paths. Reload, status, and publication errors use paths relative to the project or data directory, or the file name only. POST /api/a2a/reload without a configuration file returns 409 a2a_not_enabled instead of a raw ENOENT message.
• A failed schema file listing no longer blocks publishing from the entry stage's schema.