fix(proof): fail closed on incomplete harbor evaluate - #267
Merged
Merged
Conversation
Reject nonzero Harbor exits, score every measured trial, fail truncated off-limits scans and unknown inspect rules, and refuse import paths whose origin is outside the staged artefact. Co-authored-by: Mathis <echobt@users.noreply.github.com>
7 tasks
Contributor
Author
5 tasks
Greptile SummaryThis update continues to harden the Harbor proof adaptor so incomplete evaluation or inspection results fail closed, score evidence is derived consistently, and staged agent resolution remains constrained to the submitted artefact. Confidence Score: 5/5No blocking issues remain in scope. There are no accepted new findings and no outstanding prior-review findings to score. Reviews (2): Last reviewed commit: "fix(proof): fail closed on incomplete ha..." | Re-trigger Greptile |
6 tasks
11 tasks
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
Follow-up to squash-merged #266 (
41b51ac). That merge landed before the Greptile P1 fail-closed commit. This PR is the same fix, rebased ontomain.T-Rex-verified P1s on the Harbor evaluate adaptor:
report.json;summarize.pyalso refusesharbor_exit != 0.module:Classis resolved in the evaluate import env (artefact parent only) and rejected when the origin is outside the staged artefact.stat/readOSError), or binary regular files mark the scan incomplete so off-limits rules cannot pass on uninspected contents.Owner semantics unchanged: Harbor
-ais an import path; evaluate FAIL CLOSED without an agent at$PROOF_ARTIFACT_DIR/agentor…/recipe/agent; miner BYOK required (no owner-key fallback);terminus-2only for baseline with no miner artefact.Greptile
Every PR is reviewed by Greptile before merge. Config:
.greptile/.@greptileaiposted after each pushTest plan
deploy/guest/runners/rlm_fc_in_guest_harbor/tests/run.shincluding P1 regressions (nonzero Harbor exit, 260-trial mean vs evidence cap, truncated off-limits scan, unknown rule id, escapedimport_path, oversized/unreadable/binary skipped files)cargo run -p xtask -- external-docs-checkcargo test --workspace(adaptor-only change; CI)cargo fmt --all -- --check(CI)Risk
Operators must re-bake or replace the live Harbor adaptor for scoring to change. No
BASE_*env, deployed path, or crypto domain tag changes.Naming
I did not rename
BASE_*environment variables, deployed host paths(
/opt/base,/run/base, …), GHCRbaseintelligence/basepackage names, orbase-*-v1cryptographic domain tags, unless this PR’s purpose is a coordinatedcutover documented in
docs/NAMING.md.