build(deps): bump chap-coordinator from 0.2.13 to 0.3.0

[dependabot]

Bumps chap-coordinator from 0.2.13 to 0.3.0.

Release notes

Sourced from chap-coordinator's releases.

CHAP 0.3.0: documents that match the code, refused calls on the record, and review that holds

CHAP 0.3.0 is the first release under the versioning rules in ROADMAP.md: a minor release may break things, and the changelog lists every break under "Breaking" with a migration. The protocol packages are 0.3.0 and implement specification 0.3.

If you are upgrading

Five changes are most likely to reach you.

Advertise the profiles you call. A workspace serves the methods of the profiles it advertises, together with the reads and the key methods. A call to a method of a profile the workspace does not advertise is refused with -32601. Add the profile at workspace.create, or with workspace.set_profiles.

Expect refused calls on the log. A member's refused attempt at a governed action, such as a decision on a review addressed to someone else, is recorded. The entry holds the call under request with an outcome beside it, so a reader that takes envelope from every entry has to allow for entries without one. audit.read takes filter.outcome: "accepted" to read accepted calls alone. Back up a Python store before going back to an earlier release, which cannot read a log that holds a refusal.

Escalating or superseding keeps the review. The successor of a task that requires review requires it too. Completing it opens a review addressed to the human members other than its assignee and completer, so a workspace needs such a member, or an explicit review.request naming the reviewers.

Membership and pauses hold on more methods. task.route, review.depth, escalate.auto and participant.leave need a member. A paused participant is given no task through task.route, escalate.raise, control.supersede or handoff.accept.

task.update opens no review and reaches no pause. Use review.request or task.complete to open a review, and control.pause to pause.

The changelog covers the rest: the order in which a call is checked, the control.snapshot result shape, control.resume restoring the state held at the pause, explicitly empty selection lists, fields of the wrong type, how whisper.answer and audit.submit_to_scitt appear on the log, and the version moving to 0.3 in the schema identifiers and in the content type of SCITT statements.

Security fixes

Each of these affects 0.2.13, and 0.2.13 receives no further fixes. Upgrade to 0.3.0.

• Taking over a member by joining again. Where a deployment configures an

... (truncated)

Changelog

Sourced from chap-coordinator's changelog.

0.3.0: documents that match the code, refused calls on the record, and review that holds

Read the Breaking section before upgrading. The packages implement specification 0.3. RELEASE_NOTES_0.3.0.md summarises the upgrade, the security fixes and the known issues.

Breaking

• A token or presentation binds only to its participant. A participant.join whose token carries a chap_participant_uri naming another participant is refused with -32404. A join under an existing member's name is accepted with a token only for the member's recorded subject, or, for a member with no recorded subject, with a token whose chap_participant_uri names the member (-32404 otherwise), and with a presentation only from the member's recorded holder (-32411 otherwise). A re-join token with no acr clears the member's old acr. Before, anyone holding a token or presentation the deployment's verifier accepted could join under an existing member's name, add a key and sign as that member. Migration: a deployment that binds an identity to a member after it first joined issues tokens carrying chap_participant_uri, or has its verifier add the claim. A member with no recorded holder cannot bind a presentation by joining again.
• The routing methods and participant.leave need a member. task.route, review.depth, escalate.auto and participant.leave refuse a caller who is not a workspace member with -32011, as SPECIFICATION 6.3.1 requires of every method outside its exemptions. A non-member's task.route reassigned the task, its review.depth and escalate.auto recorded decisions, and its participant.leave wrote a leave to the log, each under whatever name the caller gave. The refusal is not recorded. A second participant.leave from the same caller is refused, where it answered left: true, and the routing parameter schemas list from as required. A from that is not a string is refused by both references with -32011 and the words Not a workspace member: from is not a participant URI, or with -32070 before that where signatures are required; the Python coordinator raised out of dispatch on a list or an object from, and with signatures or step-up on, on a list or an object workspace. Migration: send these calls from a member.
• escalate.raise applies the checks a created task meets. The successor requires review when the original did, or when it is a trial task on a workspace that advertises modes/1.0; it never required review before, so escalating a task let its successor complete with no reviewer decision. An assignee who is paused is refused with -32063. The successor takes the mode new_task.mode names, or else the original's, and a mode above the workspace's current ceiling is refused with -32040; an escalation carried the original's mode past a lowered ceiling. Migration: completing the successor of a reviewed task opens a review addressed to the human members other than its assignee and completer, and is refused with -32011 where there are none, so escalating a reviewed task to the only human member needs another human to join, or an explicit review.request naming the reviewers. To escalate a task whose mode is above a lowered ceiling, name a mode within the ceiling in new_task.mode.

... (truncated)

Commits

• cdec73c chap-analytics 0.2.1
• e0a3aab Release 0.3.0
• 8fa6da1 Fix the conformance Action, task.update into review, audit.read paging and a ...
• d95a8e8 Keep review on successors, require membership for routing, and honour partici...
• 1bd3bc5 Guides: describe what the coordinators do today
• 862f3fa Roadmap: a neutral long-term home, and what a chain head shows
• b487bd6 Licences, versioning rules, the implementations list and governance notes
• b4b1f1e SECURITY.md as one threat model, and a token or presentation binds only to it...
• a6abbc7 Bring the specification, profiles and conformance documents into line with bo...
• 2bf78a2 Add a public roadmap to 1.0 (#179)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)