[noetion]

Summary

Unifies every public and executable project identity under EvalSeal before the first package release.

Surface	Before	After
Project and repository	EvalSeal / evalseal	unchanged
Python distribution	evaluation-methodology-gate	evalseal
Installed command	evaluation-gate	evalseal
Import package	evaluation_gate	evalseal
Wheel	evaluation_methodology_gate-0.1.0-...whl	evalseal-0.1.0-...whl

This pre-publication migration intentionally removes the legacy names instead of preserving aliases that would continue the original confusion.

Implementation

• Renames the source package and every internal import to evalseal.
• Sets the distribution and console entry point to evalseal.
• Moves installed templates and policies under share/evalseal.
• Updates README, operating guides, examples, framework links, tests, and both CI workflows.
• Aligns the adopter workflow root, environment, job, and artifact names with EvalSeal.
• Replaces reserved example.org schema identifiers with canonical EvalSeal source identifiers.
• Rebuilds the wheel and regenerates the release manifest from exact staged Git blobs.
• Records the identity migration in the upcoming 0.1.0 changelog rather than leaving it under an inconsistent Unreleased section.

Review findings resolved

The artifact review caught and corrected two issues that a text-only rename would have missed:

1. The first rebuilt wheel reused an ignored stale build/ directory and contained both evalseal and evaluation_gate. That wheel was rejected, generated state was cleared, and the clean wheel contains only evalseal.
2. All 13 schemas still used the reserved example.org placeholder namespace after the first pass. They now use the canonical EvalSeal source namespace and remain fully resolvable by the registry.

Verification

• 72/72 unit tests pass after the final schema and package changes.
• 91/91 release-manifest entries match exact committed bytes.
• Fresh-clone verification passes with a clean working tree.
• Clean-environment installation exposes distribution evalseal, import evalseal, and command evalseal at version 0.1.0.
• Installed init and hash --approval complete successfully and refresh all eight bindings.
• The clean wheel contains 18/18 package source/schema files matching the repository byte for byte and no legacy package entries.
• Repository-wide scans find zero legacy names, stale wheel hashes, placeholder schema namespaces, or tracked legacy paths.
• All 41 local Markdown links resolve across 34 Markdown files.
• Both workflow files parse successfully.
• Final wheel SHA-256: f5c8357136abf42eee1c93f6aeb2417ff4afa4fd96bb068412884eed69420ea2.

Merge condition

Both GitHub CI matrix jobs for Python 3.11 and 3.13 must pass before merge.

[noetion]

Identity migration verification for commit 5b63227:

• Unit tests: 72/72 passed.
• Release manifest: 91/91 exact bindings passed.
• Fresh clone: tests and manifest passed; working tree remained clean.
• Clean wheel installation: distribution, import, and command all report evalseal 0.1.0.
• Installed workflow: init and hash --approval passed with eight refreshed bindings.
• Wheel audit: 18/18 source and schema files match repository bytes; zero legacy entries.
• Consistency audit: zero legacy identifiers, placeholder schema IDs, obsolete hashes, or tracked legacy paths.
• Documentation: 34 Markdown files and 41 local links passed.
• Workflow YAML: repository CI and adopter workflow both parsed.
• Final wheel SHA-256: f5c8357136abf42eee1c93f6aeb2417ff4afa4fd96bb068412884eed69420ea2.

The initially contaminated wheel was discarded and is not present in this branch. Merge remains conditional on both public CI matrix jobs passing.