Verify global installed mixed-provider target after OpenCode metadata recovery #223

Problem

The actual global installed mixed-provider startup is blocked before the handler by missing native OpenCode Session metadata. The observed index has 52 orphan messages / 246 parts referring to four missing native Sessions; the exact index_stale/OpenCode error is recorded in issue #205. Original provider rows and current inputs remain retained. Searches of reachable copies, backups and exports did not recover the original four authoritative Session records.

Change

Restore only the authoritative matching original native Session records through a supported provider restore/export or an accessible complete backup with owner-approved target and consistent backup. Then verify the fully active installed mixed-provider target across OMP, Pi, Codex, Claude and OpenCode. Preserve current inputs, provenance, row identity and payload. Retain authoritative native metadata, every active provider input, and the existing source records. Recovery identity fix in #205 is an integration dependency. The absence of the original four records is an external prerequisite. Any source change requires a concrete consumer defect demonstrated during the supported provider repair.

Acceptance

1. Verify the authoritative source and binding of the four original Session records; restore valid provider relationships while preserving all 52 messages and 246 parts.
2. Record installed artifact revision/version and effective active configuration.
3. Exercise ordinary startup and list/search JSON and robot, exact context, OMP command/failure/sequence/pattern behavior, using returned native anchors and all active inputs. Verify repeated startup creates no duplicates. Run the exact targeted command go test ./internal/readers ./cmd/backscroll -run 'OpenCode|MixedProviderNativeOwnershipReplayAndRecovery' -count=1. If code changes are required, run just check && just ci exactly once after the code change. Actual CLI proof is required regardless of code changes.
4. Record scope, evidence privacy and any remaining prerequisites. Keep private paths, IDs, raw payloads and public credential information out of public evidence. Complete private regression before production restore.

Additional runtime integration prerequisite

The operator authorized a reversible pause of OpenCode ingestion to test the remaining providers. The exact original manifest is retained privately; all other inputs and provider stores are unchanged. This pause is not completion of this issue: final acceptance still requires authoritative repair and OpenCode enabled.

That real installed-target test exposed a separate Claude resumed/forked transcript UUID conflict in sync-batch validation. The compatible canonical-event correction is an integration dependency for final global acceptance. Authoritative OpenCode restoration can start independently of the Claude correction. The 32640 existing OpenCode indexed rows and their payload fingerprint were preserved during the failed startup. Native GitHub blocked-by relationships bind the existing recovery identity dependency and the separately tracked Claude correction.

Relationship intent: blocked_by issue:#205 and the compatible cross-path native UUID correction.

Breakdown source: plan