Skip to content

fix(engine): calibrate test context and harden reproducibility - #5

Merged
danielcadev merged 3 commits into
mainfrom
codex/m0.3-engine
Aug 30, 2026
Merged

danielcadev merged 3 commits into
mainfrom
codex/m0.3-engine

Conversation

@danielcadev

Copy link
Copy Markdown
Contributor

Summary

  • calibrate test-context reachability without downgrading mixed test and production paths
  • classify and order candidates using every retained evidence-path step while preserving fail-closed abstentions
  • add regression coverage for all-test, mixed, production, and unresolved execution contexts
  • formalize the inert fixture dependency policy and update Next.js to 15.5.21, Flask to 3.1.3, and Django to 5.2.17
  • pin CI to Ubuntu 24.04, Rust 1.92.0, exact action identities, locked dependencies, bounded jobs, cargo-audit 0.22.2, and cargo-deny 0.20.2
  • bind an authorized npm CLI pilot to exact Engine source, evidence, binary, target, and report identities

Authorized npm CLI evidence

The final run analyzed npm CLI commit b888cc9a9ff34a8b023ff47b784692396635397b with Engine source commit c3aa5f7ee54139eac2e0398d6e4bc09969488cef and evidence binding commit adf92157366251538946d4707de643ba05700c05.

It recorded:

  • 4,859 candidate files and 4,847 scanned files
  • 57,748 normalized facts and 14 retained facts
  • 208,157 conceptual nodes and 368,627 conceptual edges
  • seven retained nodes and four retained edges
  • three candidate paths
  • zero findings, three explicit abstentions, zero diagnostics, and zero errors
  • 13.03 seconds wall time and 737,204 KiB peak RSS on the recorded host

The report SHA-256 is 5f13488477fb859bab640875e3482fc87f85bf5c6a691c613e95c596b086084f.

Verification

  • cargo fmt --all -- --check
  • cargo clippy --workspace --all-targets --locked -- -D warnings
  • cargo test --workspace --locked — 238 passed
  • cargo audit — 426 dependencies and 1,226 advisories, with only the two documented build-time exceptions RUSTSEC-2026-0194 and RUSTSEC-2026-0195
  • cargo deny check — passed
  • CI workflow and YAML validation — passed

Dependency-alert boundary

The existing GitHub alerts originate from inert fixture manifests that are not installed or executed. This PR updates and documents those fixtures but does not dismiss hosted alerts. GitHub must recompute their state after merge.

Claim boundary

Zero findings is not a clean verdict or a complete security audit. All three npm leads remain abstentions requiring human judgment. This PR does not establish human superiority, production safety, or general scanner effectiveness.

Keep test paths analyzed while ranking already-abstained test-only evidence after production paths, add neutral regressions, document npm CLI pre/post accounting, and retire fixture dependency alert noise with patched versions and explicit execution warnings.

Signed-off-by: Daniel Castrillon <danielcadev@users.noreply.github.com>
Use every retained evidence-path step for test-context ordering, cover mixed paths, advance the inert Django fixture to verified patched 5.2.17, and pin the CI toolchain and dependency gates.

Signed-off-by: Daniel Castrillon <danielcadev@users.noreply.github.com>
Record the clean-commit rebuild identity and final frozen npm scan hash, resource sample, and byte accounting without changing scanner source.

Signed-off-by: Daniel Castrillon <danielcadev@users.noreply.github.com>
@danielcadev
danielcadev merged commit ffc724d into main Aug 30, 2026
2 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