Repository navigation
fix(ci): prove the indeterminate verdict on unknown-until-apply evidence - #37
Merged
Merged
Conversation
The platform runtime proof checked a Kubernetes deployment Policy against the shared data Playground plan. That scenario no longer declares Kubernetes resources, so the check found no target and returned no decision on every platform. Analyze the documented check-architecture plan without its saved plan instead: the new subnet's network stays unknown until apply, so the Policy that passes on the locked project is indeterminate and exits 3. The proof now also requires the unknown_until_apply reason and no longer depends on what the Playground scenarios declare.
Contributor
Contribution progressSource: Selected validations:
Applicable consumers are synchronized on their development branches and the staging sites. Releases are published from main; the Release row follows them. |
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.
Change
The platform runtime proof checked a Kubernetes deployment Policy against the shared data Playground plan. Since the Playground scenarios were replanned as changes to existing infrastructure (#27), that plan declares no Kubernetes resources, so the check found no target and every native runtime job failed with
Policy result status no_decision is not indeterminate.The indeterminate verdict is now proven on the documented check-architecture plan analyzed without its saved plan. The new subnet's network stays unknown until apply, so the same Policy that passes on the locked project exits 3 as indeterminate. The proof also requires the
unknown_until_applyreason, and the unused Kubernetes Policy leaves the synthetic pack.Validation
bun scripts/verify-platform-runtime.tspasses end to end on macos-arm64 with the 0.2.1 candidate binary and with the published 0.2.0 binary: indeterminate 1 evaluation (exit 3), passed 3, violated 3.no_decisionfor the removed Policy on the current shared data plan, so the failure came from the fixture, not from the binary.bun test scripts/verify-platform-runtime.test.ts(29 pass),bun run typecheck,biome check.