Skip to content

sessionFlow v1.5.0

Latest

Choose a tag to compare

@github-actions github-actions released this 14 Nov 12:44
· 10 commits to main since this release
ab42a25

Voyager v1.5.0

Feature release, 2026-11-14. Two changes: the Evidence Verify API op
(by @SunnyRad, closing #22) and strict machine-derived repo scope (#31 Q5,
#45). No schema change — the core bridge schema stays 1, so this is fully
compatible with the DSH plugin v1.2.0 (which requires schema 1); no
plugin change is needed.

Scope note: this release carries both changes because both landed on main
before the tag was cut. It is not "the Evidence release" alone.

Evidence Verify API op (evidence_verify)

The machine surface for the five verification verdicts, over the JSON-lines
API (voyager api / callOp()). A thin, read-only pass-through to
evidence.verify() — the SAME verification the CLI uses; no second
implementation. Author: @SunnyRad (PR #24;
closes #22).

  • The five verdicts — MATCH / MISMATCH / NOT_FOUND / UNVERIFIABLE /
    INVALID_REFERENCE — are returned verbatim in result.status,
    decoupled from process exit codes; a callOp() client keeps every state
    instead of seeing them flattened into a generic failure.
  • MATCH says the indexed event is the one the reference was made from —
    reference consistency, not truth.
  • BRIDGE_SCHEMA_VERSION stays 1; integration_info().ops grows 9→10;
    the CLI, the fingerprint algorithm and the store are untouched.
  • An older Core answers unknown op: 'evidence_verify' — a capability
    error
    , distinct from an evidence NOT_FOUND (verified live against the
    published v1.4.1 wheel).

Machine-derived repo scope is strict

A sibling directory's WorkThread (E:/x/demo-old while working in
E:/x/demo) could enter current-work scope through same_repo_loose's
substring rule — and with no local thread at all, the sibling was returned as
the only current thread (status READY, current_work has_thread: true, no
flag; PR #45, design and
call-site map on #31).

  • resolve_work_thread / discover_continuity gain an additive
    repo_strict keyword: strict path-suffix matching for machine-derived
    repo paths (cwd fallback, git toplevel, the bridge) — status,
    current_work, continue_context, switch, continue, the session-start
    hook, the launcher, MCP discovery; loose matching preserved for a
    typed CLI --repo short name (D19), pinned by a test.
  • The ambiguity contract itself is unchanged (pinned by a test): AMBIGUOUS
    with a default-labelled newest candidate, stable ordering.
  • End-to-end regressions drive real sibling directories through
    status / launcher.prelaunch / hook.startup_handler — red on the
    pre-fix tree, green here.

Compatibility

  • Bridge schema stays 1; the DSH plugin v1.2.0 (six tools) needs no
    change. The plugin's seventh tool (sessionflow_evidence_verify) lands
    with plugin v1.3.0 as a separate release.
  • Index compatible in both directions with v1.4.x / v1.3.x: no schema change,
    no migration.
  • Historical v1.4.x release notes ("the Evidence verify API op is not part
    of this release") remain correct as history and are untouched.

Verification

  • Full suite: python -m pytest tests/ -q — counts recorded in the README
    ("measured at v1.5.0").
  • Pre-tag gate: python scripts/check_release_ready.py --version 1.5.0 --plugin-root ../dsh-sessionflow.
  • Artifacts: one wheel + one sdist, twine check clean, no tests//scratch
    in the wheel, isolated-install smoke: voyager --version, doctor exit 1
    pre-scan, integration-info schema 1 with evidence_verify in ops,
    five-state live probe, machine-scope refusal probe.