[onexbot-occ-writer]

Automated lane-census refresh, opened by the refresh leg built in OMN-18606.

Collected on the lab host by the census runner (vars.LANE_CENSUS_RUNS_ON_JSON) against the
same docker daemon the hourly onex-disk-gc census pass reads.

• emitted_at: 2026-10-01T05:47:03.235251+00:00
• drift findings: 1
• refresh reason: topology_changed

Before this leg existed, every refresh of this file was a person opening
a PR — six of them between 2026-07-22 and 2026-09-14, plus a seventh
while OMN-18606 was being written. Review the census delta and merge.

[onexbot-occ-writer]

OCC autobind did not mint a companion for this PR: no changed-file candidate could be proven RED against the merge base, and emitting a PR-existence probe instead would be non-falsifiable evidence (OMN-15247). Hand-authored evidence is required.

Considered 1 changed file(s):

• deploy/lane-census/census-snapshot.json: no candidate grammar reads this file type (only Python declarations, uv.lock lines, release-artefact lines and contract-pin lines are proposed)

This verdict is occ-autobind's, derived from this head and its merge base alone. A second producer, the occ-companion-effect backstop, consumes its own command on the lab bus and may still mint a companion under the generic binding. Whether it does depends on that consumer running, not on this diff (OMN-18876).

[jonahgabriel]

Superseded by #4406, a fresh census emitted 2026-10-01T07:20Z with 0 drift findings. The ci-bus finding on this snapshot (unexpected_container omninode-ci-bus-labwork-user) was declared by #4395 (OMN-20213), which merged at 07:06Z. Closing so only one census PR stays armed.