@statelyai/mcp 0.9.6 → 0.10.0

package/README.md

@@ -293,8 +293,11 @@ createMachine({
 
 <!-- apply_machine_patches registration from src/server.ts and apply-patches response contract -->
 
-Applies semantic patches to a machine and returns the updated document. Use
-`to` to choose the returned format.
+Applies semantic patches in memory and returns a non-mutating behavioral
+proposal: the updated document, the structured patches, and a concise
+`behavioralSummary`. It never writes the source file or invokes Git. Use `to`
+to choose the returned format; the coding agent remains responsible for its
+actual source edit.
 
 Patches use semantic graph operations. For example:
 
@@ -335,6 +338,42 @@ createMachine({
 
 </details>
 
+## `review_machine_implementation`
+
+<!-- review_machine_implementation registration from src/server.ts -->
+
+Reviews an agent-edited machine against the original source and proposed
+semantic patches. It validates the edited machine, derives the behavior the
+edit actually introduced, and reports missing, extra, or divergent changes.
+The returned `stately-behavior-review.md` artifact contains the semantic
+summary plus before/after Mermaid graphs, ready for the agent to save or paste
+into its pull request.
+
+The workflow keeps ownership explicit:
+
+1. Inspect the existing machine.
+2. Call `apply_machine_patches` for structured behavioral guidance.
+3. Edit the source with the coding agent's normal tools.
+4. Call `review_machine_implementation` with the original source, edited
+   source, and proposed patches.
+5. Let the coding agent create its branch, commit, and pull request normally.
+
+Neither tool writes files, creates branches, commits, pushes, or contacts a Git
+provider. The surgical writer remains an optional primitive for an agent that
+wants minimal source edits; it does not own the surrounding workflow.
+
+<details>
+<summary>Summary: verify an agent-authored behavior change</summary>
+
+```text
+Ask Stately for patches that add a verifyingFraud state between processing and
+completed. Edit the machine source yourself, then ask Stately to review the
+edited machine against the original source and those patches. Save the returned
+Markdown behavior review and include it in the pull request you create.
+```
+
+</details>
+
 ## `generate_graph_paths`
 
 <!-- generate_graph_paths registration from src/server.ts and graph-paths response contract -->
@@ -577,6 +616,9 @@ Self-host Stately Studio, then replace the hosted URL above with your
 deployment's `/api/mcp` endpoint, for example
 `https://studio.example.com/api/mcp`.
 
+When the editor runs with `AUTH_PROVIDER=none`, MCP tool calls do not require a
+bearer credential. Keep the endpoint behind your own trusted access boundary.
+
 After deployment, run the protocol and MCP App canary with a read-only bearer
 credential: