v0.3.0 — observation lifecycle
agent-catalog v0.3.0 — technical preview
An observation-lifecycle release: the catalog now tells you not just what agents exist, but whether what it's showing you is current. Published via npm trusted publishing (OIDC) with provenance.
Added
- Cluster visibility in the UI. A
Clustercolumn on the fleet page and acluster: <name>chip on the agent card — in a multi-cluster setup you can see which cluster an agent runs on. - Observation lifecycle v0 — an outage no longer reads as a deletion. Each scan stamps
last-observed-at+source-status: available; a failed cluster list keeps the last good snapshot but marks itsource-status: unavailablewithsource-last-success-at. Surfaced as aSourcecolumn (online/offline) and a card chip/hint. - Interface drift — declared vs. served skills. For kagent agents with a live A2A card, declarative
a2aConfigskill IDs are compared against the card's served skills; mismatches setinterface-status(in-sync|drift) + aninterface-driftdetail, also underspec.agent.interface. Shown as anInterfacecolumn and card chip. - Fleet column chooser. Lower-signal columns hidden by default, toggleable per view.
Docs
- First release where both packages render a README on npm; plus demo screenshots and the agent-operations roadmap.
Full notes: CHANGELOG.md.