fix: enable explicit decision measurement startup - #1142
Conversation
|
Important Draft PR not reviewedDraft PRs are not automatically reviewed by default.
To automatically review draft PRs, update your CodeRabbit configuration: reviews:
auto_review:
drafts: trueThanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
Exact-head package follow-up: rebuilt the core wheel offline from clean babea95. SHA-256 a16d800953ecf9f8bf3cf5d4b8e5bd62e67039f56b05825e1065d643d9509d90. Reinstalled that wheel into the isolated environment and ran the six entrypoint tests outside checkout with python -I, --noconftest, --import-mode=importlib and -W error: 6 passed in 1.47 s. This is core-wheel entrypoint evidence only; no native integration or customer KPI gain claim. The PR evidence and limitations sections were directly screenshot-inspected in GitHub at 1265x712 English and remain readable. Parent #1107 Security run 34695611099 completed successfully at de21ffd; that result does not establish this Draft successor CI or independent approval. |
|
Verified an additional acceptance boundary at babea95 in an isolated detached checkout: real CLI startup with Build: |
|
Installed-wheel acceptance now passes at babea95. Built with locked maturin 1.15.0 for CPython 3.14.4, installed the core/native wheels plus hash-locked runtime requirements into an isolated environment, and executed from /tmp using Python -I with an empty environment. Explicit assertions require both core and native imports to resolve beneath the installed interpreter prefix. The real CLI, loopback HTTP and SQLite check returned HTTP 200 with one acknowledged persisted receipt and a non-null durable acknowledgement time. Native wheel SHA-256: |
Scope
Stacked on #1107 at de21ffd. Head babea95.
Expose the existing default-off decision receipt option through serve and an explicit CLI switch. Reuse native/store validation. Preserve prior positional arguments and adjacent #911 parser work. No numerical estimator or production default changes.
Evidence
Remaining boundaries
Bounded latest-256 export retains measurement_complete=false and reconciliation_required=true. Complete ingress reconciliation and independently adjudicated correctness are still missing. No accuracy/latency KPI gain, hosted acceptance, protected merge, release or deployment is claimed. Preserve required checks and independent review.