# session-flow 3.1.0: verify reuses existing evidence

> Verify reuses evidence that still applies and runs only the checks that are missing, failing or stale. Simplify becomes an add-on, and a project can name a runbook for delivery.

- Type: release
- Published: 2026-10-23
- Author: Mats Hoppenbrouwers (hoponthestack)
- Canonical URL: https://www.frameworkreboot.com/writing/session-flow-3-1-0-verify-reuses-existing-evidence

v3.1.0 · MIT · https://github.com/matshoppenbrouwers/session-flow

## Changes

- /session-verify first maps existing evidence to each accepted criterion. It reuses results that still apply and runs only the checks that are missing, failing or stale.
- Known test failures live in one project file, known-failures.md in the testing path. A failure not listed there is a fail entry, and a baseline is never recorded as waived.
- /session-post-implementation no longer simplifies by default. Simplify is an add-on in every preset.
- The sequence marks an accepted or active item with (acceptance stale) when its acceptance no longer names the current scope fingerprint. The task view shows the same state.
- The optional paths.runbook key points at the file that says how the project commits, pushes and deploys. When the user asks to deliver, /session-next follows it and records a receipt of the revision, target and health result.
