Repository navigation
Register runtime-state classification in acceptance policy - #5264
Merged
Merged
Conversation
This was referenced Oct 11, 2026
Trecek
added a commit
that referenced
this pull request
Oct 13, 2026
The runtime-state root classification map was restored in #5263, but it was still absent from the acceptance-policy registry. Future additions to its exemptions could therefore escape the policy comparison. Register `_CLASSIFIED_ELSEWHERE` as an `int_map` with `default=0`. The registration now compares against the dictionary-shaped base containing #5263, preserving the existing policy reader and approval mechanism. Validation: policy comparison against `dbc689db57d3d847758ec08dd5bad31105f39730` and `pre-commit run --all-files` passed. The configured MCP `test_check` (`task test-local-gate`, conservative filtering) passed against that actual PR base: 11,771 passed, 197 skipped, 12 xfailed on `3a0a9f8eae7a4d84a7e14d8b0b899ea76b30bd07`. The first gate compared against stale local `develop` at `0bf84f3`, whose value still had the old set shape: 51,229 passed and one policy-comparison test failed. The runner's comparison base was temporarily pinned to the fetched, dictionary-shaped PR base for the successful rerun, then restored. Both results are preserved locally. Refs #5258. After merge, integrate the registered policy and runtime repairs into the existing #5255 scenario branch, perform both E-3 replays against the unchanged seed, and record the actual clone-admission evidence in #5258 before closing it. This PR supplies the remaining policy entry; it does not claim the live replay has already happened.
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
1 participant
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.
The runtime-state root classification map was restored in #5263, but it was still absent from the acceptance-policy registry. Future additions to its exemptions could therefore escape the policy comparison.
Register
_CLASSIFIED_ELSEWHEREas anint_mapwithdefault=0. The registration now compares against the dictionary-shaped base containing #5263, preserving the existing policy reader and approval mechanism.Validation: policy comparison against
dbc689db57d3d847758ec08dd5bad31105f39730andpre-commit run --all-filespassed. The configured MCPtest_check(task test-local-gate, conservative filtering) passed against that actual PR base: 11,771 passed, 197 skipped, 12 xfailed on3a0a9f8eae7a4d84a7e14d8b0b899ea76b30bd07.The first gate compared against stale local
developat0bf84f3, whose value still had the old set shape: 51,229 passed and one policy-comparison test failed. The runner's comparison base was temporarily pinned to the fetched, dictionary-shaped PR base for the successful rerun, then restored. Both results are preserved locally.Refs #5258. The registration is merged and the two post-merge clone-admission replays are complete, with exact evidence and separately failed full-commissioning outcomes recorded in #5258 and #5255.
Post-merge verification — 2026-10-11
This policy registration is merged. Both post-merge default clone invocations succeeded in runs 38170521660 and 38170536595; code/policy/replay evidence and teardown are recorded in #5258. The full workflows failed later on terminal-result/session-measurement and kitchen/tracker handling; #5255 commissioning remains incomplete.