Repository navigation
evidence(OMN-16700): OCC Evidence-Source autobind for OmniNode-ai/omnibase_compat#196 - #7252
Merged
jonahgabriel merged 2 commits intoAug 27, 2026
Merged
Conversation
…mpat#196 OCC companion by node_pr_lifecycle_fix_effect (OMN-13317 F1 / OMN-13990 / OMN-14285). Product PR head 9cb6c54b437018e31973e5c1220346efc02bd5be.
onexbot-occ-writer
Bot
added
ci:ready
jonahgabriel
enabled auto-merge (squash)
August 27, 2026 02:51
jonahgabriel
deleted the
auto/omninode-ai-omnibase_compat-pr-196-occ-autobind
branch
August 27, 2026 03:13
jonahgabriel
added a commit
that referenced
this pull request
Aug 27, 2026
…g it `Pre-commit / yamlfmt` fails on this companion and only on this companion. The summary line `node_occ_companion_compute (OMN-14285) for OmniNode-ai/omniintelligence PR #853.` exceeds yamlfmt's max width, so the hook rewraps it and the job goes red. The three sibling companions minted in the same batch (#7250 omnibase_spi, #7252 omnibase_compat, #7253 omnidash) all pass — the line length depends on the repo name, and `omniintelligence` is the one long enough to cross the limit. This is a formatting-only change to a `>` folded scalar: a folded scalar joins its lines with a space, so the parsed value is unchanged. Verified rather than asserted — `yaml.safe_load` of the file before and after the reflow compares equal as sorted JSON. No evidence content is altered, and the contract is still what compute authored. Re-minting would not help: the defect is deterministic in the repo name, so a fresh mint reproduces it exactly. The real fix belongs in `node_occ_companion_compute`, which should wrap its own summary; filed on OMN-16698 for omnimarket.
jonahgabriel
added a commit
that referenced
this pull request
Aug 27, 2026
… (#7251) * evidence: OCC companion pass 1 for OmniNode-ai/omniintelligence#853 * evidence: OCC companion self-bind for #7251 * style(OMN-16698): reflow the minted summary so yamlfmt stops rejecting it `Pre-commit / yamlfmt` fails on this companion and only on this companion. The summary line `node_occ_companion_compute (OMN-14285) for OmniNode-ai/omniintelligence PR #853.` exceeds yamlfmt's max width, so the hook rewraps it and the job goes red. The three sibling companions minted in the same batch (#7250 omnibase_spi, #7252 omnibase_compat, #7253 omnidash) all pass — the line length depends on the repo name, and `omniintelligence` is the one long enough to cross the limit. This is a formatting-only change to a `>` folded scalar: a folded scalar joins its lines with a space, so the parsed value is unchanged. Verified rather than asserted — `yaml.safe_load` of the file before and after the reflow compares equal as sorted JSON. No evidence content is altered, and the contract is still what compute authored. Re-minting would not help: the defect is deterministic in the repo name, so a fresh mint reproduces it exactly. The real fix belongs in `node_occ_companion_compute`, which should wrap its own summary; filed on OMN-16698 for omnimarket. --------- Co-authored-by: node-occ-companion-effect <occ-companion-effect@omninode.ai> Co-authored-by: jonahgabriel <jonah@omninode.ai>
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.
Autobind OCC evidence for
OMN-16700.Triggered by node_pr_lifecycle_fix_effect OCC companion emitter on OmniNode-ai/omnibase_compat#196 (OMN-13317 F1 / OMN-14285).
Evidence-Ticket: OMN-16700