Dev - #998
Merged
Merged
Conversation
chore: back-merge v3.0.0 into dev
…esign feat(formal): define participant crossing bisimulation
feat: integrate admitted trial realization provenance
…sonar new-code gate
refactor: split raes/module_registry into an API-stable subdomain package
…ckages (#49) Convert four >500-line modules into same-named packages behind API-stable re-export facades (no behavior change): - raes_runtime/control_plane_api -> _responses/_auth/_operation_routes/ _workflow_routes/_participant_routes; version seam + app factory stay in the facade so test_version_classification's distribution_version patch holds. - raes_runtime/workflow_result_contract_checks -> _models/_context/ _step_checks/_history_checks; diagnostic order preserved. - raes_mcp/tools/authoring -> tools/_templates/_helpers. - raes_mcp/tools/inspection -> tools/_common/_summary/_elements/_references. Drain the four entries from oversized_allowlist.yaml; retarget the ruff per-file-ignores, requirement_order.yaml ownership root, and the shared-semantic-integrity coverage path to the new package locations.
…ud new-code gate The pure-move split re-attributes the moved MCP tool code as new code, so SonarCloud's raes-strict new-code gate flagged 33 pre-existing maintainability smells (cognitive/cyclomatic complexity, >3 returns, missing type hints, deep nesting, register() length). Extract cohesive helpers and add type hints, preserving every MCP tool name, description, signature, and output string (behavior verified by test_mcp_server.py). Pre-validated with the raes-strict profile via analyze_code_snippet.
feat: lower runtime configuration realization concerns
refactor: split runtime control-plane and MCP tooling modules into packages
feat: implement participant opacity conformance profile
…-trial-scheduling # Conflicts: # .gitignore
…cheme-bindings feat: add portable external concept bindings
…loud parameter-count gate
feat: publish SCE-006 isolated batch trial scheduling handoff
… entry The .codex file is the repo's Codex agent-rules doc (read by the skill-discovery tests in test_agent_inventory_skill.py), not a personal dotfile. It was both tracked and listed in .gitignore; the ignore entry is the bug. Keep it tracked and remove the entry, retaining only the stray tool working-directory ignores.
fix: stop ignoring a tracked agent-rules file that tests read
feat: add governed adaptive difficulty policies
feat: model-check finite participant opacity profiles
fix: resolve SonarCloud quality gate findings
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.
Summary
Related issues
Changes
Test plan
nox -s verifygate passes, or unchecked sessions are listed belowChecklist
CHANGELOG.mdfrom it)Notes for review