Skip to content

Fix Evidence submission after refreshing Context - #27

Merged
piaro merged 1 commit into
mainfrom
fix/evidence-refresh-submission
Sep 8, 2026
Merged

piaro merged 1 commit into
mainfrom
fix/evidence-refresh-submission

Conversation

@piaro

@piaro piaro commented Sep 8, 2026

Copy link
Copy Markdown
Owner

Problem and change

Adding Evidence and refreshing Context before submission made the Evidence require its own digest, causing evidence-backed outcome requires an Evidence Record. The input matcher now treats Evidence for the same Change and Requirement as verification outputs while continuing to validate all dependencies captured when the Evidence was created.

This allows truthful unsatisfied and inconclusive outcomes to be submitted without a commit. Regression tests cover single and multiple Evidence Records, refreshing between additions, and rejection when code, Contract, Decision, Change, or a recorded Evidence dependency changes. The Builder skill and English/Japanese documentation describe the workflow. Record formats and CLI arguments are unchanged.

Addresses #22 (comment)

Validation

  • cargo fmt --check
  • cargo clippy --all-targets --locked -- -D warnings
  • cargo test --locked
  • sh scripts/tests/test-rust.sh

All checks passed. Network tests were rerun outside the sandbox because it blocks local listeners.

@piaro
piaro merged commit 5900514 into main Sep 8, 2026
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant