fix(authoring): separate offline public evidence from installer security - #204
Draft
777genius wants to merge 1 commit into
Draft
fix(authoring): separate offline public evidence from installer security#204777genius wants to merge 1 commit into
777genius wants to merge 1 commit into
Conversation
Refs #199. Preserve production security and lifecycle checks, version the offline evidence boundary, and retain the unmet successful distributed installer dry-run requirement.
|
Important Draft PR not reviewedDraft PRs are not automatically reviewed by default.
To automatically review draft PRs, update your CodeRabbit configuration: reviews:
auto_review:
drafts: trueThanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
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.
The public native E2E driver invoked a valid installer dry-run in a zero-network lane. Production installer security consults the Security Index and acquires lintai, so the test failed before lifecycle and packed planner checks could finish.
This separates the executable offline observations from the existing injected planner gate without changing production security. Explicit v2 evidence records real installer help/preflight rejection and keeps successful distributed add --dry-run marked not evaluated. The original successful production CLI requirement remains required for the full goal. Strict v1/private interpretation, lifecycle checks, and the ten-project/thirty-plan matrix remain intact.
Stacked on #199 at cdf0aa4. Head 9606e24: eleven files, 498 additions and 29 deletions. Writer focused checks passed: 11 Node tests, 16 Python tests, three named Go main/release tests and two planner/source-harness tests. Root verified 59 artifact hashes, all eleven source hashes and exact patch before mechanical commit.
Independent hosted review ACCEPT at this exact head; all focused checks passed independently. Fresh candidate and actual public preparation succeeded. The E2E worker then stopped before native execution because the environment denied the required strace/ptrace observation probe. No native TAP, 71-call completion or public ten-project/thirty-plan gate was produced; no reroute or retry was attempted. Current CI: packed Linux and three native platforms passed; Windows amd64 failed and required aggregate failed, so this PR remains draft and is not merge-ready. No old candidate bytes are repinned, and no full E2E, release or security-scanner acceptance is claimed. Production Go, launchers, security adapters, dependencies and preserved YAML functionality are unchanged.
Refs #199