Skip to content

fix(ops): wire G001 current-state inspection - #309

Merged
ael-dev3 merged 1 commit into
mainfrom
codex/0.4-wire-g001-current-state
Sep 20, 2026
Merged

ael-dev3 merged 1 commit into
mainfrom
codex/0.4-wire-g001-current-state

Conversation

@ael-dev3

Copy link
Copy Markdown
Owner

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.

@ael-dev3
ael-dev3 merged commit e42aa15 into main Sep 20, 2026
8 checks passed
@ael-dev3
ael-dev3 deleted the codex/0.4-wire-g001-current-state branch September 20, 2026 03:59
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.
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