[jonahgabriel]

Hand-bound OCC companion (union-resolve) for OmniNode-ai/omnibase_infra#3361, ticket OMN-17304.

Evidence-Ticket: OMN-17304

Why this is hand-minted

Autobind mints no companion in this window — OMN-18073 is the open outage for it (every OCC autobind mint on the dev-lane runtime-effects container has failed since 2026-09-09T01:55:02Z). This is the same posture OCC#8760, OCC#8779 and OCC#8786 took in the same window. Without a companion, omnibase_infra#3361 has no receipt to cite and the eligibility contexts fail on the missing citation.

What the product PR is

OMN-17304 AC4, caller side. omnibase_core#1633 shipped RuntimeLocal(host_handlers=...) on 2026-09-01; omnibase_infra has had zero callers for it since (git grep -c host_handlers origin/dev -- src → 0, against a positive control of 2 RuntimeLocal( construction sites), so onex delegate still hosted the entry handler on every run.

#3361 adds --locus {auto,in-process,deployed-lane}, a fail-closed dispatch gate that requires a live STABLE consumer group on the contract-declared command topic before publishing, tri-state live_consumer_groups() in backend_probe, and locus provenance (handler_locus, wire_correlation_id, orchestrator_distribution, dispatch_target) in the receipt and capture log. inmemory keeps host-and-publish byte-for-byte.

The commit was written 2026-08-31 and sat unpushed on a local worktree; it is rebased onto current dev in #3361, not re-derived. Three conflicts, all against work that landed afterwards, resolved in favour of dev's AC3 wiring plus the new locus axis.

Union-resolve, stated

contracts/OMN-17304.yaml already carried five evidence items from three earlier companions (OCC#7826, #7925, #7984). This appends only — no existing item, description, check or binds_ac is edited or removed, so every prior receipt's contract_entry_sha256 binding still resolves.

Evidence carried here

item	shape
dod-OmniNode-ai-omnibase_infra-pr-3361	PR state, plus the new locus test file present in the diff
occ-self-bind-pr-<this PR>	binds OMN-17304 to this companion

Both binds_ac: ["AC4"].

Honest limit on what the product PR proves

AC4's own locus readback (fresh correlation, non-zero docker logs omninode-runtime{,-effects} --since 20m | grep <corr>, no committed-offset movement on the launching host's consumer group) was not obtained. The .201 dev-lane broker restarted 2026-09-09T01:48:44Z with SASL enabled (sasl_mechanisms: ['SCRAM'], one superuser), so every unauthenticated Kafka client is refused at connect — reproduced inside the container with rpk group list, again with explicit brokers on both listeners, and from the launching host with a confluent_kafka AdminClient. The receipts here bind what was actually measured: PR state, diff content, and the unit-level proof (lab full suite 27382 green; the two focused files 89 passed). No synthetic substitute was manufactured for the locus readback.

Rule 22 respected: no credential was rotated, re-issued, revoked or minted, and no secret value was read, printed or decoded. No runtime lane was mutated.