Repository navigation
v0.5.7: restore subject/delete + plugin-runtime subject helpers
Restores the animus-subject-protocol surfaces wiped by the v0.1.14 "sync from animus-cli" regression and re-adds the animus-plugin-runtime subject helpers downstream Rust plugins depend on.
Restored on animus-subject-protocol 0.1.14 → 0.1.15
METHOD_SUBJECT_DELETE = "subject/delete"wire constantBackendError::Unsupported(String)variant + RpcError mapping toMETHOD_NOT_SUPPORTED(-32001)SubjectBackend::deletetrait method with default impl returningUnsupportedDeleteSubjectRequest/DeleteSubjectResponseSubject::native_status,Subject::status_metadata,Subject::attachmentsSubjectAttachment { id, kind, uri, title, mime_type, metadata }StatusDispatchHint { native_status, maps_to, dispatch_label, description }SubjectSchema::native_status_values,SubjectSchema::status_dispatch_hintsSubjectFilter::native_status,dispatch_label,has_attachment_kindSubjectChangedEvent::previous_native_status,previous_dispatch_labelChangeKind::DispatchLabelChanged,::AttachmentAdded,::AttachmentRemoved
Added
SubjectSchema::supports_delete: bool— mirror ofsupports_create, defaults tofalsefor back-compat.
animus-plugin-runtime 0.2.0 → 0.2.1
subject_backend_main(info, backend)— drop-in for the v0.1.13 entrypoint. Auto-derives kind-prefixed<kind>/<verb>aliases frombackend.schema().kinds, forwardshealth/checktobackend.health().subject_backend_main_with_capabilities(info, backend, extra)— parity with v0.1.13.subject_backend_main_with_kinds(info, backend, kinds)— explicit kinds list.subject_plugin/subject_plugin_with_kind_aliases— builder-style.Plugin::on_health(hook)— backend-specifichealth/checkrouting.Plugin::advertised_methods()/Plugin::has_method_handler()— test accessors.
Kept from v0.1.14
schemars::JsonSchemaderives on every public message typeanimus-subject-protocol-export-schemabin
Why
The v0.1.14 "sync from animus-cli" merge replaced the upstream protocol crate with a snapshot of the in-tree ao-cli copy, silently dropping a number of subject extensions that downstream plugins depended on. v0.5.7 makes the upstream protocol forward-compatible with v0.1.13 again, so downstream Rust subject plugins can bump their pin to v0.5.7 in a single edit and pick up subject/delete instead of staying trapped on v0.1.13.