feat(evidence): publish the Flow 1.32.0 comparison; mark 1.31.0 superseded - #294
Merged
Conversation
…seded The daily evidence-freshness workflow went red when Flow 1.32.0 replaced 1.31.0 on PyPI: published numbers described an engine nobody serves. Publishes a fresh Flow 1.32.0 comparison, independent replication, transaction-fault probe, and remote-lease contract probe, run against the exact published wheel (d58dcf8b...) and release-tagged source (d1b054c7...), from Evals commit b7d4fe8. 93 counted trials: - comparison and replication: compiled replay correct in 18 of 18 trials; selector controls halt safely under drift; zero silent incorrect success, wrong actions, over-halts, or model calls - transaction probe: uncertain deliveries return RECONCILIATION_REQUIRED with no blind retry or replay dispatch - remote lease probe: absent-or-changed frame leases refuse actuation Every campaign states production_acceptance: false. The registry marks the Flow 1.31.0 set superseded instead of changing or deleting it.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changed
d58dcf8b…, sdistc3125f16…, release-tagged sourced1b054c7…(v1.32.0), and Evals commitb7d4fe84…Why
The daily evidence-freshness workflow has been red since Flow 1.32.0 replaced 1.31.0 on PyPI (runs 32342633608, 32457392921). Published numbers described an engine nobody serves. This follows the PR #286 pattern: bounded campaigns, exact artifact binding, documented reproduction.
Counted result
93 counted trials against Flow 1.32.0, run locally (synthetic MockMed, loopback only, headless Chromium, no model calls):
RECONCILIATION_REQUIRED; no blind retry or replay dispatchHALTED_BEFORE_EFFECT)Zero silent incorrect success, zero wrong actions, zero over-halts, zero model calls across all counted arms.
Every campaign states
production_acceptance: false. This set is development evidence, not a Production lifecycle admission, and establishes nothing about hosted, customer-workflow, native-desktop, RDP, or Citrix acceptance.Validation
37 passedintests/test_published_evidence_freshness.py