Skip to content

chore(occ-deps): update rerun state after 9d7ba402 - #1547

Closed
github-actions[bot] wants to merge 1 commit into
mainfrom
automation/occ-rerun-state-9d7ba402
Closed

github-actions[bot] wants to merge 1 commit into
mainfrom
automation/occ-rerun-state-9d7ba402

Conversation

@github-actions

Copy link
Copy Markdown
Contributor

Automated OCC rerun state update for merge 9d7ba40.\n\nThis PR is opened instead of direct-pushing to protected main.

@jonahgabriel

Copy link
Copy Markdown
Contributor

Closing: superseded by #1574 (identical diff, latest OCC rerun-state). Part of OMN-11979 Wave 1 cleanup.

andywu42 pushed a commit to andywu42/onex_change_control that referenced this pull request Jun 10, 2026
…apter DI refactor (OmniNode-ai#861)

* docs(OMN-10731): add OCC contract and DoD receipts for SQLiteProjectionAdapter DI refactor

Binds omniclaude PR OmniNode-ai#1547. Dual receipts: dod-pr-1547-head (PR open at
recorded head 6877077a) and dod-ci-1547-green (all non-receipt CI gates
pass on same commit). dod-occ-pr receipt to follow once this PR is open.

* docs(OMN-10731): add dod-occ-pr receipt for OCC PR OmniNode-ai#861

Self-referential receipt confirming OCC PR OmniNode-ai#861 is open carrying the
OMN-10731 contract. Completes the three-receipt DoD for this ticket.
@jonahgabriel
jonahgabriel deleted the automation/occ-rerun-state-9d7ba402 branch June 11, 2026 17:58
jonahgabriel added a commit that referenced this pull request Aug 5, 2026
…#6083)

* evidence(OMN-15692): OCC companion for OmniNode-ai/omnibase_core#1547

OCC evidence companion for the round-#3 remediation of the MSK
gateway-only enforcement rule (ruling 39, operator 2026-08-04) —
omnibase_core PR #1547 fixes 7 adversarial-verification defects against
the msk-direct-broker-endpoint url-authority rule: baseline self-defeat
(the branch had pre-seeded the 3 only known live violations, self-defeating
the guard), an anti-gaming check scoped to repo=="omnibase_core" only
(blind to omnibase_infra's own baseline growth), a .env file-selection
hole (Path.suffix is empty for a bare .env file), a bare-substring
test-path exemption that waived deploy/latest.yaml /
docker/stability-test/** / attestation.yaml, and missing .json/.tf/
Dockerfile/.env.<profile> scan-surface coverage.

* evidence(OMN-15692): add self-bind entry for OCC companion PR #6083

Cites OMN-15692.

* evidence(OMN-15692): PASS receipts for OCC companion PR #6083, independently verified

Cites OMN-15692. runner=claude-code-subagent-omn-15692-remediation ran all
5 probes at 2026-08-05T00:42:38Z; verifier=fable-delta-0804-orchestrator
(session foreground orchestrator, distinct identity) independently
re-executed the same 5 probes at ~2026-08-04T23:05Z and confirmed matching
results. run_timestamp records the verifier's confirming run per the
adversarial-receipts convention (verifier != runner required for PASS).
jonahgabriel added a commit that referenced this pull request Sep 17, 2026
Four product PRs now land under OMN-18601 -- omninode_infra #1536, #1543 and
#1547, plus omnibase_infra #3727 (the v0.38.31 cut that unblocks the
promotion's parity gate) -- so the autobinder has authored
contracts/OMN-18601.yaml repeatedly and this companion went DIRTY when dev
gained the #3727 entries.

Resolved as an APPEND-ONLY structural union, per the recorded resolution for
this collision class and identically to the earlier OMN-18582 case:

* dev's file text is kept VERBATIM -- no yaml re-dump, which mangles quoting
  and unicode and can trip the yamlfmt contamination ratchet;
* the two identifiers dev lacks are spliced in as exact byte blocks:
  dod-OmniNode-ai-omninode_infra-pr-1547 and occ-self-bind-pr-10102;
* the seven identifiers present on BOTH sides are kept once from dev, because
  a duplicate id is a contract-shape risk and dev's copy is the one existing
  receipts are hashed against.

Asserted by the splice rather than by eye: no duplicate identifier in the
result, and every unique identifier from both sides survives. Eleven entries
in, eleven out.

VERIFIED with the real validator rather than by inspection: every receipt
under drift/dod_receipts/OMN-18601/ that declares a contract_entry_sha256
recomputes equal to it against the union -- 11 matches, 0 mismatches. That is
the control for this resolution: validation is entry-hash-first, so appending
entries cannot invalidate an existing receipt, and a union that moves no entry
hash should rebind nothing.

Refs: OMN-18601
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant