- click and press steps take save_response {method, path, save}: the
recorder waits, before the step acts, for the 2xx JSON response to the
request it triggers and saves values from it
- {saved:name} sends a saved value in a request path (and its query), a goto
URL, and a request's JSON body, where a string that is only the
placeholder keeps the saved JSON type; header values and Basic
credentials parts take {source: "saved", name}
- Basic credentials take parts: [username, password], each a literal,
secret, saved, cookie or local storage value, so the schema repeats the
part union once; path_params and json_values are gone, which keeps the
compact MCP catalog under its 1 MiB frame
- validation refuses a saved value no earlier step saves; other braces are
sent as written
- Evidence records an empty save list as absent, so scenarios that save
nothing record the same parameters and scenario_sha256 as before
- environment-build warns about saved values named like credentials that
are not marked secret (credential-named-saved-values)
- the skill writes the way the UI does and falls back to request steps;
skill version 50
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
