ce-code-review report labels the in-process adversarial reviewer "harness-native fallback"

Problem

In compound-engineering 3.25.0, a ce-code-review run in mode:agent where the cross-model peer was deliberately not started produced this in its report's coverage.cross_model.degraded field:

Code review: harness-native fallback for the adversarial lens; no cross-model peer ran …

That phrase already means something specific in ce-work's shipping gate (references/shipping-workflow.md): the fallback used when ce-code-review itself cannot produce a completed receipt, so the session runs the host's own review command instead. None of that happened here:

• ce-code-review loaded and returned status: complete
• the adversarial lens ran through the skill's own in-process adversarial-reviewer persona, the documented local fallback when no peer starts (references/select-and-route.md, Stage 3d)
• the peer was skipped because the invocation prohibited external provider egress for a private repo

Why it matters

ce-work's ship-handoff gate accepts Code review: harness-native fallback as an exact skip phrase. A caller or reader who matches on that string will read a complete review as one that ran without ce-code-review. That understates the coverage, and it also makes the phrase unreliable as a gate signal.

Expected

When the in-process adversarial-reviewer covers the lens, the report should say so in its own terms, e.g. adversarial lens: in-process fallback (cross-model peer not run: <reason>), matching peer.outcome: in-process-fallback. Keep harness-native fallback for the case shipping-workflow.md defines.

Repro shape

ce-code-review mode:agent depth:full base:<ref> on a local diff that selects the adversarial lens, with an invocation constraint prohibiting cross-model egress. finish-input.json records peer.outcome: "in-process-fallback", and the report leaf still emits the harness-native fallback wording.