You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Additive protocol fold-ins surfaced by v0.5.0 production use; all changes
are backward-compatible.
animus-queue-protocol (0.1.0 -> 0.2.0):
- METHOD_QUEUE_RELEASE_PENDING ("queue/release_pending") returns an
Assigned entry to Pending without canceling it. Fills the gap that
previously forced the daemon to call queue/completion(cancelled) when
it discovered a subject was already being worked on by another
in-flight lease.
- QueueReleasePendingParams { entry_id, reason }
- QueueReleasePendingResponse { entry_id, status }
- New error code QUEUE_ENTRY_NOT_ASSIGNED (-32208); data SHOULD include
the actual entry status.
animus-workflow-runner-protocol (0.1.0 -> 0.2.0):
- WorkflowPhaseRunRequest.mcp_config: Option<serde_json::Value> mirrors
WorkflowExecuteRequest.mcp_config so phase-level retries can pass MCP
server config to the agent runner.
- workflow_status module: PAUSED ("paused") + PENDING ("pending")
constants previously collapsed to "running" on the wire.
- workflow_status::Parsed + workflow_status::parse() parse helper with
Unknown(String) fallback documenting the additive-vocabulary contract:
consumers default-match unknown statuses to Running semantics.
animus-control-protocol:
- Fix pre-existing build break under --all-features: test helper
sample_event() referenced Subject / SubjectChangedEvent fields that
do not exist in animus-subject-protocol (native_status,
status_metadata, attachments, previous_native_status,
previous_dispatch_label). Strip the stale field assignments so cargo
clippy --all-targets --all-features passes on the v0.5 branch.
0 commit comments