v0.1.5 — subject watch+unwatch

Wires real subject/watch streaming (was METHOD_NOT_FOUND despite supports_watch) + subject/unwatch cancel. Pins animus-protocol v0.5.13.

v0.1.4: animus-protocol v0.5.7 + subject/delete

Bumps the animus-protocol pin to v0.5.7 (was v0.1.13) and implements SubjectBackend::delete.

What changed

• task/delete and subject/delete now route through SubjectBackend::delete, returning the protocol DeleteSubjectResponse { ok: true } shape and broadcasting a ChangeKind::Deleted event on the watch stream.
• subject/list routes through SubjectBackend::list, honoring the v0.5.7 SubjectFilter additions (native_status, dispatch_label, has_attachment_kind). Accepts both the unwrapped flat filter shape and ao-cli's wrapped {"filter": {...}} shape.
• SubjectSchema.supports_delete = true.
• PluginCapabilities.methods now advertises subject/list, subject/get, subject/update, subject/delete, subject/schema alongside the existing task/* surface.

Compatibility

• task/list continues to use the legacy methods::list path so the historical {"status": "ready"} shorthand and raw native-status strings still work.
• v0.1.3 callers using task/delete will see the new {ok: true} response shape instead of {id, deleted} — this is intentional and matches the protocol shape v0.5.7 hosts expect when SubjectSchema.supports_delete is true.

Binaries

Release binaries built via the existing release.yml CI.

v0.1.3

v0.1.3: declare subject_kind:task capability marker for daemon preflight

v0.1.2

v0.1.2 - cosign keyless signing for release artifacts

v0.1.1

Full Changelog: v0.1.0...v0.1.1

v0.1.0

Full Changelog: https://github.com/launchapp-dev/animus-subject-default/commits/v0.1.0