v0.58.0 (continued): the release notification is its own event type, host.release.published@1; host.deploy.activated@1 is the tenant shape only

OP OpenVibers committed 26 Sept 2026 · tag v0.58. · 0 files, +0 −0

The release notification no longer reuses host.deploy.activated.
- host.release.published@1 (catalog visibility public, ADR-016): a network service's release went live. OpenVibe.Host's operator plane publishes it (ovhost deploy/rollback, ovhost announce). Envelope subject { type: release, id: <service>:<release> }, visibility public. Payload exactly the release shape: service, release (the release manifest's pattern), commit or null, origin (an http(s) origin) or null, deployed_at, optional components (kind and version only, at most 32) and rollback: true. Identifiers only.
- host.deploy.activated@1 (now first-party, ADR-004) is one shape, what Host's Stage B already emits for a tenant site's activation: project_id, site_id, site, deploy_id, previous_deploy_id, rollback (subject deploy, visibility internal). No oneOf.

The host manifest lists host.release.published in eventsProduced and its notes name both producers. The release fixtures move to fixtures/host.release.published (plus: a tenant activation and a payload carrying a tenant field are invalid there); host.deploy.activated keeps its tenant fixtures (plus a rollback, and a service release is invalid there). test/run.js: both contracts owned by host and produced by its manifest, public vs first-party, one shape each, neither payload passes for the other, every release field required, identifiers only, the release manifest's release pattern. ADR-016 amendment 1 and the 0.58.0 CHANGELOG entry use the new name. Regenerated; compat vs v0.57.2: no breaking changes. Still 0.58.0, not tagged.

This commit has no diff to show.