Fix runtime safety and Console contract regressions - #1350
Merged
Merged
Conversation
Owner
Author
|
Superseded by #1351, which isolates the validated runtime Settings change from unrelated concurrent commits that landed on the original head branch. |
This was referenced Sep 18, 2026
dotnetpower
enabled auto-merge (squash)
September 18, 2026 04:55
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.
Summary
ActionRunand resource-claim pathstate_kvnamespace while preserving atomic transitions and fail-fast PostgreSQL configurationSafety
This change adds no ActionType, provider mutation, deployment, promotion, or execution authority. Huginn remains the deterministic Event/Change collector, Forseti remains the judge and Verdict owner, Thor remains the sole privileged executor, and Odin and Saga retain actionless triage evidence. Local Settings materialization remains non-manageable, and Cost Governance keeps current UTC as its production default.
Validation
fdai_corePostgreSQL analyzer claim/release/reclaim passedCI follow-up
The superseded settings-only PR exposed deterministic integration failures. This branch refreshes the catalog-derived question bank and dependent CQAS artifact, removes wall-clock expiry from the Cost Governance tests through the production-safe clock seam, and retains the routed design-context line budget.
Closes #1349
Supersedes #1351