Skip to content

dsh-sessionflow v1.3.0 — seventh tool (evidence_verify), Core v1.5.0 pairing

Latest

Choose a tag to compare

@HarryHeYu HarryHeYu released this 15 Nov 08:54
· 1 commit to main since this release
2ad05c8

Seventh tool: sessionflow_evidence_verify. The plugin can now ask the core whether an Evidence Reference (seq N · #digest) still points at the event it was made from. It is a thin callOp() pass-through over Core v1.5.0's additive evidence_verify op — no second verification algorithm, no exit-code reinterpretation. Tool surface 6 → 7.

Compatibility

plugin core bridge schema
1.3.0 v1.5.0 1
1.2.0 v1.3.1 1
1.1.0 v1.3.0 1
  • Core v1.5.0 is required for the seventh tool (it adds the op). The six older tools keep working on earlier cores.
  • On a core without the op the seventh tool answers unknown op: 'evidence_verify' — a capability error, never a verdict and never NOT_FOUND. Verified against the published v1.4.1 wheel, not a stub.
  • REQUIRED_SCHEMA_VERSION stays 1: the op is additive, not a protocol bump.
  • Missing core: the tool still registers, and every call names the binary it tried to run.

Trust boundaries

  • MATCH is not "the claim is true." It means the indexed event matches the recorded digest — reference consistency only.
  • exit_code is a result field, not a process status: the four non-zero verdicts are normal results and are returned verbatim.
  • The tool validates session_id / seq / digest before spawning; a malformed reference is refused locally, with no core process started.
  • The Core's INVALID_REFERENCE verdict therefore cannot be produced through this tool; it stays reachable for any caller that sends such a reference straight to the Core. Pre-rejecting locally is not the same as the Core lacking the state.
  • Native resume by an agent is NOT VERIFIED.
  • Model-driven tool selection is not claimed as end-to-end verified. What this release pins is the deterministic contract: input → bridge call → result formatting.

Also included (merged earlier, first released here)

  • sessionflow_merge now builds an argv the core's argparse can actually parse: = option form, -- separator, --json placed before it. Over-long values are refused by name before the spawn instead of surfacing as ENAMETOOLONG against the executable.
  • The bridge mechanics tests no longer leak VOYAGER_BIN / VOYAGER_PYTHON into later tests (#6).
  • A provider-filtered sessionflow_recent no longer under-returns silently: a window-limited answer is marked truncated, including the case where the wanted provider sits entirely behind the window.
  • Stub fixtures now produce shapes a real core can actually produce.

Assets

file size sha256
dsh-sessionflow-1.3.0-src.tar.gz 160,247 B 647fcbcfb3318b87643bd4e42686b047a207a0dfa28dff649cf10811cf1c2f16
dsh-sessionflow-1.3.0.tgz 49,111 B 30290c6e4b0e18037ab22c8688e1464c2233b5ce2776bf8d67eba8511febf04a

Both are produced from the tag tree with line-ending conversion disabled, so the bytes match the git blobs and a Linux/macOS checkout reproduces them:

git -c core.autocrlf=false archive --format=tar.gz \
    --prefix=dsh-sessionflow-1.3.0/ v1.3.0 -o dsh-sessionflow-1.3.0-src.tar.gz
git -c core.autocrlf=false archive v1.3.0 | tar -x -C tree && cd tree
npm ci && npm pack          # -> dsh-sessionflow-1.3.0.tgz (26 files)

npm pack normalises entry mtimes, so repeated packs from the same tag give the same digest (verified twice). The plugin is not published to a registry; the tarball is an inspection and integrity artifact.

Full write-up: docs/release-v1.3.0.md

Install

dsh plugin --profile <profile> add github:HarryHeYu/dsh-sessionflow

Then check the core pairing: voyager --version should print 1.5.0, and voyager doctor should report bridge schema 1.