Release v0.24.0 · kikutano/tinyprobe

Leave a step out of one run: run --skip. The step that deletes what you want to look at, a slow sleep, a step against a service that is down today: skip it for this run, and the file stays as it is, so a step never stays out by mistake in CI. A step is named as with --to, by its number as inspect lists it or by its name, and the option can be repeated (spec 0021).
```
tinyprobe run tinyprobe/workflows/users.yaml -e tinyprobe/env.local.yaml --skip 11 --skip "Deleted user is gone"
```
```
  ✓ Patch the user          PATCH  200      397µs  /api/users/56
  – Delete the user         skipped (--skip)
  – Deleted user is gone    skipped (--skip)

  steps...............: 10/10 passed  2 skipped
```
Skipped steps are not counted: the run passes when the steps that ran passed. A later step that needs a value only a skipped step saves fails and says why: Variable 'userId' is not defined: step 7 (Create a user), which saves it, was skipped. With --to, skipped steps after the target are ignored. --skip takes one workflow file.
For tools. run_started lists the skipped steps in skipped and the summary counts them in skipped_steps (new keys, protocol 1); in the JUnit report they are <skipped message="Skipped with --skip"/>. The MCP run tool takes skip, so an agent can explore a flow without the step that would delete what it looks at. tinyprobe-app uses it for ⊘ Skip on the steps of a workflow.

Update: tinyprobe update, or run the install command again.

What's Changed

Full Changelog: v0.23.0...v0.24.0