Compose published relation consumers with the public PBT campaign

[CaelmBleidd]

Compose the independently published public campaign and numeric relation APIs before the coordinator is added. The merge resolutions preserve compact input export, native coverage, compiler-owned local capture, empty point requests and both ordinary and explicitly focused property search. There is no new scheduling policy.

Exact dependencies: #597 b09a010f8, #590 285951203fd46f3579ba914e050717d4c1c29081, and #596 b57c44fa27f994d325745c1798e7427738d4a812. The inherited feature diffs remain those PRs; this branch isolates their semantic composition so the coordinator can be reviewed separately.

Validation: 67 focused Kotlin campaign/refuter/inference/export tests and 235 native adapter tests passed on the composed tree. Shared property-search main Detekt passed after preserving its focused-search contract. This is a dependency integration branch; no PR has been merged into main.

Review boundary: the current diff against #597 is +5015/-51 because it includes the numeric dependency stacks. It is not a new 5000-line coordinator. The semantic merge resolutions are confined to five files:

• fast-check-adapter/package.json: keep both compact-input and compiler-capture native test entry points.
• fast-check-adapter/src/execute-property.ts: keep empty-point requests used by the public campaign while retaining the compiler-local single-point guard.
• fast-check-adapter/src/external-witness.ts: retain source coverage and compiler/entry relation events in the same original-admission callback, preserving argument order.
• FastCheckBackend.kt: preserve empty-point requests and the compiler-local identity validation together.
• UsvmPropertySearcher.kt: keep the public deadline/coverage/completed-input controls and the previously published explicit entry-focused query; both share the same original-precondition/property execution. The two subsequent ordinary composition-repair commits touch only this file (+23/-14), preserving its lint contract.

git show --remerge-diff 2a1e10ccb exposes those semantic resolutions, but its added/deleted-line counts include conflict markers and are not a reliable measure of new product code.

Suggested user-controlled merge route: first review and merge each prerequisite of #576/#580 and the public chain through #597; then #576 and #580 -> #584, followed by #590 and #596. Reconcile this composition after those exact dependencies, and review the coordinator child separately. No branch or pull request is merged by this task.