Skip to content

Prepare EvalSeal for public release - #3

Merged
noetion merged 2 commits into
mainfrom
release/prepare-publication
Aug 2, 2026
Merged

noetion merged 2 commits into
mainfrom
release/prepare-publication

Conversation

@noetion

@noetion noetion commented Aug 2, 2026

Copy link
Copy Markdown
Owner

Summary

Prepares EvalSeal for public release by resolving every actionable item in the 2 August publication checklist.

  • Repairs byte-exact template approval bindings and adds regression coverage.
  • Adds active Ubuntu CI for Python 3.11 and 3.13, including manifest verification, the full test suite, and the fictional gate example.
  • Reworks the README into a runnable product page with an explicit trust boundary and ten-minute demo.
  • Reframes self-certification-style audit documents as a claims ledger and verification notes.
  • Adds contributing, security, changelog, notice, package metadata, portable commands, and adopter/repository CI distinctions.
  • Rebuilds the wheel and regenerates the release manifest from normalized committed bytes.

Root causes addressed

  • Template files had been re-hashed without refreshing the final approval binding.
  • The only workflow was an adopter template and therefore did not run for this repository.
  • Publication documents mixed useful evidence with self-review framing that weakened credibility.
  • Package and contributor metadata were incomplete for an open-source release.

Verification

  • 72/72 unit tests pass.
  • 91/91 release-manifest entries match exact committed bytes.
  • 8/8 template approval inputs bind to their exact files.
  • The fictional example returns SIMULATED_APPROVE, authorizes_deployment: false, and no blocking issues.
  • The wheel installs in isolation and its packaged sources and metadata match the repository.
  • Markdown structure, local links, workflow syntax, and clean-clone checks pass.
  • Fresh read-only review found no publication blocker.

Merge conditions

  • Both GitHub CI matrix jobs must pass.
  • Fast-forward main without rewriting the reviewed history.
  • Publish the exact wheel with SHA-256 6d8ec6b75d0cf725450327b999ba2d0b942879d33e3de6b2297c09cd6a473ef9.
  • Prune superseded branches only after the reviewed commit is on main.

@noetion

noetion commented Aug 2, 2026

Copy link
Copy Markdown
Owner Author

Publication verification for commit a97a972:

  • Local test suite: 72/72 passed.
  • Release manifest: 91/91 exact byte bindings passed.
  • Template approval inputs: 8/8 matched.
  • Fictional gate: exit 3 with SIMULATED_APPROVE, authorizes_deployment: false, and no blocking issues.
  • Release wheel SHA-256: 6d8ec6b75d0cf725450327b999ba2d0b942879d33e3de6b2297c09cd6a473ef9.
  • Fresh diff review: no blocking findings.

Merge remains conditional on both GitHub CI matrix jobs completing successfully. After that, main should be fast-forwarded, verified again, and obsolete branches pruned.

@noetion
noetion merged commit 2aaa649 into main Aug 2, 2026
4 checks passed
@noetion
noetion deleted the release/prepare-publication branch August 2, 2026 15:14
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