docs: multi-machine HIVE validation plan for the default-runtime flip criteria

[hardcoreerik]

Summary

Plan-only doc mapping each of NATIVE_RUNTIME_V2_SPEC.md §6's default-runtime-flip entry criteria to a concrete, evidence-bearing campaign phase (HV-0..HV-6) across the real three-machine fleet:

• NewcorePC — Warchief + reference worker (RTX 5070 Ti 16GB)
• HardcorePC — low-VRAM worker (RTX 3050 6GB) — carries the known unresolved native-lib regression, listed as a hard HV-0 precondition
• HardcoreLaptopMSI — mobile worker (RTX 4060 8GB) — CUDA-redist bundling verification required per box

Fleet was surveyed live over SSH during planning (GPUs/drivers/repo states verified, both remotes synced to master @ aa07f41, pinned test-GGUF distribution with recorded SHA-256 initiated). The plan produces §6 evidence only — the flip stays gated on an explicit recorded product decision, per the spec.

Notes

• Folds the deferred "second concurrent role" Phase D increment into HV-3 rather than leaving it orphaned.
• Harness guidance: PowerShell driver on the Warchief + existing HIVE campaign contracts; per-box NUnit lanes stay the single-box floor. Small reviewed PRs per phase, as always.

🤖 Generated with Claude Code

[coderabbitai]

Warning

Review limit reached

@hardcoreerik, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 59 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: 0fc1d027-a493-4737-90d0-d917c3ca6795

📥 Commits

Reviewing files that changed from the base of the PR and between aa07f41 and 04b86d4.

📒 Files selected for processing (1)

• docs/NATIVE_RUNTIME_HIVE_VALIDATION_PLAN.md

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch docs/hive-validation-plan

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[hardcoreerik]

@coderabbitai full review

[coderabbitai]

✅ Action performed

Full review finished.

---

Your plan includes PR reviews subject to rate limits. More reviews will be available in 59 minutes.