fix(ops): wire G001 current-state inspection - #309
Merged
Merged
Conversation
ael-dev3
added a commit
that referenced
this pull request
Sep 20, 2026
Refresh the durable 0.4 release records to the current protected M2 state. Records protected main 5870717, PRs #309 and #310, Verify 35494158124, CodeQL 35494158121, exact preflight 35496632288, the converged native M1 family/closure/scanner/candidate counts, and the explicit finalReleasePrepared:false plus remaining private/live release gates. Also records stale-family diagnosis 35490374334 and repaired current-state route. No runtime or gameplay code changes.
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.
Problem: g001-current-state was exposed in workflow choices and implemented in the G001 lane, but the readonly job guard and fixed Linux caller omitted it, so dispatches fell through to the unsupported job. Change: route it through operate_readonly, add the fixed caller mapping with current-state-inspected status, and align regression coverage. Source-only; no provider or realm operation, gameplay change, or admission-policy change. Verification: 293 focused tests passed, 83 skipped; git diff --check clean. Generated sealed family remains source-bound and must be regenerated after this source commit is promoted.