Repository navigation
evidence(OMN-15960): OCC companion for OmniNode-ai/omniclaude#1985 - #6395
Merged
jonahgabriel merged 2 commits intoAug 12, 2026
Merged
Conversation
jonahgabriel
added
the
ci:ready
jonahgabriel
enabled auto-merge (squash)
August 12, 2026 20:35
jonahgabriel
deleted the
auto/omninode-ai-omniclaude-pr-1985-occ-autobind
branch
August 12, 2026 20:42
jonahgabriel
added a commit
that referenced
this pull request
Aug 12, 2026
…#6400) * fix(OMN-15960): falsifiable deploy-gate probe for omniclaude PR #1985 The auto-minted OCC companion (PR #6395, merged) shipped dod-deploy-assessment with a gh-diff+grep check that the deploy-gate correctly rejects (F-05): it never depends on a live surface, only on text the PR author wrote. Appends dod-deploy-assessment-falsifiable (append-only — the prior entry is untouched) using the deploy-gate's own documented hermetic no-live-deploy pattern (OMN-14051): a live GitHub contents-API fetch of the merged file at PR #1985's head SHA, asserting the symbol the fix introduces. This is the correct pattern here specifically because PR #1985's own finding is that omniclaude is never deployed as a live runtime service anywhere (omnibase_infra/docker/Dockerfile.runtime does not install omniclaude; omniclaude/deployment/Dockerfile is explicitly CI-validation-only) — there is no docker/kubectl/psql live-container target to probe. Falsifiability verified both directions before authoring: - ref=<PR #1985 head SHA> → grep -q finds the symbol → PASS - ref=dev (pre-PR) → grep -q does not find it → FAILS (positive control) contract_sha256 / contract_entry_sha256 computed via omnibase_core.validation.validator_receipt_gate against the yamlfmt-stabilized contract file, matching the receipt-gate's own hashing algorithm. OMN-15960 * fix(OMN-15960): self-bind receipt for OCC PR #6400 occ-preflight / eligibility failed on this PR with reason pr_ticket_mismatch: none of the existing receipts (all bound to the prior, now-merged OCC#6395) reference this PR's own commit history — the F-01 in-repo trap (OCC PRs must validate against their own in-tree checkout, per docs/RECEIPT_LOCATIONS.md). Appends occ-self-bind-pr-6400 mirroring the shape of the prior occ-self-bind-pr-6395 entry, pointing pr_number/branch/commit_sha at this PR (#6400, jonah/omn-15960-deploy-gate-falsifiable-probe) so the self-bind resolves. commit_sha references the immediately-prior pushed commit (8dfdb4a...), an ancestor of this PR's eventual HEAD. OMN-15960 * fix(OMN-15960): buffer the deploy-assessment probe against SIGPIPE (Rule E) test_rule_e_census_totals_agree_with_the_baseline_and_scan (OMN-15411) correctly flagged the first draft's check_value as sigpipe-fragile: an unbounded producer (base64-decoded file body) piped straight into `grep -q`, which exits at the first match and can turn a real PASS into a false RED (exit 141) under `bash -o pipefail` — growing the frozen shrink-only ratcheted census from 311 to 312. Rewrites the check_value using the linter's own prescribed fix (scripts/lint_contract_check_values.py::sigpipe_fragile_violation): buffer the producer through command substitution first, then pipe the already-materialized string — body="$(<producer>)" && printf '%s' "$body" | grep -qF 'MARKER' Verified: linter.sigpipe_fragile_violation(new_value) is None (no longer flagged); functional PASS/FAIL both directions unchanged (present at PR #1985's head SHA, absent at dev); local tests/unit/scripts/test_lint_contract_check_values_corpus_baseline.py full file green (15 passed), Rule E subset green (7 passed). occ-self-bind-pr-6400's contract_sha256 field updated to match the whole-file hash after this edit (its own contract_entry_sha256 is unchanged, confirming OMN-13888's non-destructive-append property: editing a sibling entry does not perturb this one's per-entry hash). OMN-15960
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.
Deterministic OCC evidence companion for OmniNode-ai/omniclaude#1985, authored by node_occ_companion_effect (RSD-3, OMN-14622) from the node_occ_companion_compute plan. Every byte is a pure function of the compute plan (attestation-oracle reproducible).