Repository navigation
feat: admit exact ER coverage and earn specification conformance - #61
Draft
b10x-bot[bot] wants to merge 5 commits into
Draft
b10x-bot[bot] wants to merge 5 commits into
b10x-bot[bot] wants to merge 5 commits into
Conversation
Add a closed reader profile for ESS suite28 and inventory suite29 without introducing compiled ESS dependencies. Preserve exact numeric lexemes, suite association, inventory and parent lineage checks, with explicit refusals for unsupported types. Retain producer fixtures, guard mutation and review evidence. Refs: story:admit-er-direct-return-evidence
Admit the unchanged 414-case ER suite and report in a permanent reader regression and retain full-gate results after the independent review and mutation checks. Close the implemented reader work with the exact producer and execution identities. Refs: story:admit-er-direct-return-evidence
Retain and re-admit exact report and suite sources before deriving lifecycle eligibility for a complete passing current model. Preserve original evidence kinds, timestamp precision and a distinct recorded basis; newer failing or partial runs cannot be hidden by older success. Retain negative guards, mutation restoration, legacy readback, seven independent CLI probes and the successful real ER transition. The complete gate passes with the planning store held unchanged. Refs: story:bind-current-coverage-to-specification-lifecycle
Preserve the current CLI-only aep interface and the independently reviewed coverage lifecycle bridge. Reconcile the changelog and remove stale alias claims before verifying the combined source.
b10x-bot
Bot
changed the title
Compose the reviewed coverage lifecycle bridge with main's committed status, evidence and review validation and snapshot verification changes. Verify the combined planning behavior before final publication.
This branch has not been deployed
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
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.
AEP could neither admit Entity Runtime's direct-return ESS suites nor use admitted current coverage to earn specification conformance. This change adds the closed ER return profile for suite/28 and inventory suite/29, retains exact report and suite originals, and re-admits them when evaluating lifecycle eligibility.
Only the latest complete, whole-system, all-origin, nonempty passing coverage for the current model qualifies. Newer failed or partial runs veto older success; original milliseconds resolve same-second ordering. Derived eligibility is recorded separately, preserving the coverage evidence kind and legacy behavior. No compiled ESS dependency, store format change or package version change is introduced.
The actual ER release pair passes all 414 scenarios and now moves its specification from validated to conforming through this CLI. Exact suites, reports, hashes, mutation failures and restored successes are retained. Seven independent adversarial cases passed, including admission after the original input files were deleted. Released AEP 0.63.1 reads the resulting history. The full repository gate, MSRV and website checks passed; current-main integration also preserves removal of the protocol alias.
Refs: story:admit-er-direct-return-evidence; story:bind-current-coverage-to-specification-lifecycle.
Publication follow-up is blocked. The last published implementation revision is
18a18a3f1cfa110dc5c9a675b3e9956f74c29bb7; its full local and CI gates passed and merged ER PR47 pins it. A later documentation-only composition with current main passed the full local gate, but Gates refused publication:merged pull request missing or ambiguous. Main now includes GitHub-generated branch-update commit74956edad272b9489193248b347692edfffdeda6from #64; the completed PR merge is938320e349ac4b0e5e8a21feb497b881dc5bd993, so the intermediate commit lacks the completed-merge provenance required by delivery. The unpublished composition and governed blocker are retained in a managed recovery archive. This PR remains draft until that provenance is resolved through Gates and the final candidate passes CI.