Repository navigation
ci(OMN-20943): omnimemory's imperative contract guard calls omnibase_core's reusable with its own shrink-only allowlist - #611
Merged
jonahgabriel merged 1 commit intoOct 11, 2026
Conversation
…owlist Move the historical omnimemory allowlist unchanged and pin the reusable and canonical-file-shape hook/job to the core commit that reads its declaration. Bind all three criteria to focused executable tests, including refusal controls.
onexbot-occ-writer Bot
pushed a commit
to OmniNode-ai/onex_change_control
that referenced
this pull request
Oct 11, 2026
…omnimemory#611 OCC companion by node_pr_lifecycle_fix_effect (OMN-13317 F1 / OMN-13990 / OMN-14285). Product PR head 1a839b9d091c46a9017e3bc133113e5585cd2380.
jonahgabriel
pushed a commit
to OmniNode-ai/onex_change_control
that referenced
this pull request
Oct 11, 2026
…memory (#13694) * evidence(OMN-20943, OMN-20940): author OCC companion for OmniNode-ai/omnimemory#611 OCC companion by node_pr_lifecycle_fix_effect (OMN-13317 F1 / OMN-13990 / OMN-14285). Product PR head 1a839b9d091c46a9017e3bc133113e5585cd2380. * evidence(OMN-20943, OMN-20940): self-bind OCC#13694 + rebind contract_sha256 --------- Co-authored-by: omnimarket-bot <bot@omninode.ai>
jonahgabriel
deleted the
ci/OMN-20943-imperative-contract-guard-occ-ret-memguard-i1-8e80
branch
October 11, 2026 20:21
This was referenced Oct 12, 2026
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
1 participant
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.
OMN-20943, under parent OMN-20074, moves omnimemory's imperative guard caller to core's reusable at
031148215620031436cba30619bbae67c0bb38ad. The caller passesimperative-contract-allowlist.yaml, moved byte-identically from the historical guard at725d2967b031d7065efd41d0751f903638202cc1, with its four paths and metadata unchanged.The job id
imperative-contract-guardand contextimperative-contract-guard / Imperative Contract Guardare unchanged.The canonical-file-shape hook and CI job use the same core pin, which reads the caller's shrink-only allowlist declaration. The lifecycle validator sharing that hook block is byte-identical across the revision change. The application dependencies and lock are unchanged; tests use isolated core 0.47.41 because locked core 0.47.39 lacks the ratchet handler.
contracts/OMN-20943.yamlbinds all three criteria to executabletest_passescommands.Lab: host=h201 lane=occ-ret-memguard-i1-8e80 command=uv run pytest tests/ci/test_imperative_contract_guard_caller_omn20943.py -q -n 0 observed=5 passed; merge-base control 5 failed; pinned core/OCC clean exits 0/0 and planted exits 1/1 with identical findings; canonical-file-shape new pin passed and old pin refused the same allowlist; candidate DoD 3/3 verified and merge-base 0/3 verified.
AC3 used the pinned core CLI and historical OCC CLI on isolated copies of omnimemory's tree with freestanding scanning enabled. Adding raw
httpx.getto the live retrieval handler produced one live blocker in both; the clean tree had zero. Complete JSON findings matched after normalizing the allowlist location. The source was scanned without executing the planted request.Ruff format/check, focused mypy and pre-commit on all six changed files passed. No new suppression annotation or baseline entry was added.
Evidence-Ticket: OMN-20943
Evidence-Source: OCC#13694