v1.4.0

Upgrading

A2A and durable tasks ship off. Turning them on needs PostgreSQL, api.durableTasks.enabled, api.a2a.enabled, and requestReplyEnabled on each agent you want reachable. A cluster that leaves them off is unaffected.

Added

• Agent-to-agent (A2A 1.0) support. Kyber agents can be given work by outside systems and can hand work to other agents. Each agent publishes its own Agent Card on an authenticated endpoint.
• Durable tasks underneath it. A task survives a control-plane or agent restart, reports progress, returns text, JSON or file results, can be cancelled, and can ask the caller a question mid-run and wait for the answer.
• Live task streams. A caller can follow a task as it runs and reconnect without losing events.
• Per-caller ownership. A caller sees and controls only its own tasks, with a separate scope per operation.
• A published capability list per agent, empty until an operator fills it in. Nothing about an agent is exposed automatically.
• Outbound peers. Allowlist named HTTPS peers and their credentials; the agent gets tools to discover, delegate, follow up and download artifacts, and never sees the URL or the token.
• Conformance runs in CI against the official A2A test kit.
• Agents can read their own profile — name, runtime, model, phase, skills. Not placement, credentials or channels.
• Disk usage shows a soft reservation as a reservation, alongside the real free space on the underlying disk.

Fixed

• The installed PWA stays signed in instead of asking for the API key again after every control-plane restart.
• Durable-task settings in the chart never reached the control plane, so the feature could not be switched on at all.
• Row menus in the agent list offered actions the agent's state does not allow; they now match the detail page.
• Text requests submitted through the request API never reached the agent — the request ID format was rejected in the pod.
• A skill written as a single flat file kept warning as unmanaged, and stale skill links are now cleaned up.