[pullfrog]

Fix for the moq-ffi check failure on #7806, stacked on its branch because the branch is locked in the merge queue.

Diagnosis

origin::supervision_tests::container_importers_keep_the_origin_failure_after_other_owners_are_released failed on CI 114130473307 with:

assertion failed: matches!(completion.finished().await, Err(MoqError::Task { .. }))

The test was migrated to origin.route(...).unwrap().broadcast().unwrap(), which drops the MoqRoute and keeps only broadcast handles. Under the new ownership the route is the origin's owner (RouteState::_keepalive), while a broadcast producer is not: once the origin producer and the route are both gone, the driver polls Closed and finishes cleanly. The test then races the driver against its injected panic, so it usually passes on an idle host and loses the race under CI load.

Verified deterministically by dropping the route before the panic and waiting 200 ms: the assertion fails with the same message. Holding the route instead passes 15/15 runs.

Change

• Hold the route for the duration of the failure check, then drop it before the importer assertions, so only the importers still carry the origin's failure. This keeps the test's intent instead of weakening it.
• Clarify the Route doc: the route, not the broadcast, keeps the origin's Driver running.

Verification

• cargo test -p moq-ffi --lib -- origin::supervision_tests: 7 passed.
• cargo fmt --all -- --check and cargo clippy -p moq-ffi --lib --locked -- -D warnings: clean.

Once #7806 is dequeued, this commit (da3f1b09e) can go straight onto quest/m1/api-audit/route/handle.

  ^{｜ View workflow run ｜ via Pullfrog ｜ Using deepseek-v4.1-flash-1017 (free via Pullfrog for OSS) ｜ 𝕏}