docs: sync ROADMAP/CURRENT_STATE with Native Runtime v2.0 Phase B addendum + D by hardcoreerik · Pull Request #82 · hardcoreerik/TheOrc

hardcoreerik · 2026-07-20T04:32:27Z

Summary

Docs-only sync. Both files still described Phase B's cost-estimate half as deliberately deferred and Phase D as untouched — stale since #76, #77, #78, and #79 all landed. Updates:

ROADMAP.md's "Native Runtime v2.0 direction" banner + Phase 3/4 table rows
CURRENT_STATE.yaml's native_runtime status note

No code changes.

🤖 Generated with Claude Code

Summary by CodeRabbit

Documentation
- Updated Native Runtime v2.0 status to show Phases A–C completed and Phase D largely complete.
- Documented fail-closed VRAM admission, live GPU budget readings, and KV/rs-cache-aware cost estimates.
- Added coverage of cancellation recovery, denial behavior, and verified end-to-end native-runtime performance evidence.
- Clarified that native runtime remains opt-in, with Ollama available as fallback.
- Updated roadmap and release timeline details to reflect the latest implementation status.

…endum + D Both files still described Phase B's cost-estimate half as deliberately deferred and Phase D as untouched -- stale since PR #76 (cost estimate), #77 (load-time measurement), #78 (negative fail-closed test), and #79 (cancellation-corruption fix) all landed since the last sync. Updates the Native Runtime v2.0 direction table in ROADMAP.md and the native_runtime note in CURRENT_STATE.yaml to reflect current reality: Phase B fully landed (estimate + measurement), Phase D essentially complete pending the E2E evidence-lane PR (#81, open). Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>

coderabbitai · 2026-07-20T04:32:38Z

Warning

Review limit reached

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

Next review available in: 54 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: e52c78b4-da47-4fd8-9505-49982cc37dca

📥 Commits

Reviewing files that changed from the base of the PR and between aa07f41 and 6f86a27.

📒 Files selected for processing (2)

docs/CURRENT_STATE.yaml
docs/ROADMAP.md

📝 Walkthrough

Walkthrough

Documentation now records the latest Native Runtime v2.0 foundation-hardening progress, including VRAM accounting, load-time measurement, fail-closed behavior, cancellation recovery, E2E evidence, and continued non-default runtime gating.

Changes

Native Runtime documentation

Layer / File(s)	Summary
Foundation-hardening status note `docs/CURRENT_STATE.yaml`	Updates Phases A–D status with KV/rs-cache-aware VRAM estimates, live `nvidia-smi` budgeting, llama.cpp log parsing, fail-closed tests, cancellation recovery, and E2E evidence.
Release roadmap status `docs/ROADMAP.md`	Updates release timing and Native Runtime v2.0 progress, including Phase B addendum completion, Phase D status, Phase 3 measurements, and continued opt-in gating.

Estimated code review effort: 1 (Trivial) | ~5 minutes

Possibly related PRs

hardcoreerik/TheOrc#67: Introduces the Native Runtime v2.0 production-readiness specification reflected by these documentation updates.
hardcoreerik/TheOrc#78: Adds the Phase D fail-closed admission-denial test documented here.
hardcoreerik/TheOrc#81: Adds the Phase D real-model E2E lane and retained evidence referenced in the updated status.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly matches the documentation sync and highlights the main Native Runtime v2.0 Phase B addendum and Phase D updates.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

🧪 Generate unit tests (beta)

Create PR with unit tests
Commit unit tests in branch docs/sync-roadmap-native-runtime-v2

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

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

hardcoreerik · 2026-07-20T05:00:47Z

@coderabbitai review

coderabbitai · 2026-07-20T05:01:09Z

✅ Action performed

Review finished.

Note: CodeRabbit is an incremental review system and does not re-review already reviewed commits. This command is applicable only when automatic reviews are paused.

hardcoreerik · 2026-07-20T05:01:31Z

@coderabbitai full review

coderabbitai · 2026-07-20T05:01:43Z

✅ Action performed

Full review finished.

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

hardcoreerik · 2026-07-20T14:18:11Z

@coderabbitai full review

coderabbitai · 2026-07-20T14:18:20Z

✅ Action performed

Full review finished.

… criteria (#83) Maps each of NATIVE_RUNTIME_V2_SPEC.md §6's entry criteria to a concrete, evidence-bearing campaign phase (HV-0..HV-6) across the real three-machine fleet: NewcorePC (Warchief, RTX 5070 Ti 16GB), HardcorePC (RTX 3050 6GB), HardcoreLaptopMSI (RTX 4060 8GB). Fleet surveyed live over SSH during planning (GPUs, drivers, repo paths/states verified, both remotes synced to master @ aa07f41); pinned test-GGUF distribution to both workers initiated with SHA-256 recorded for per-box verification. Honest blockers listed up front: HardcorePC's unresolved native-lib regression is a hard HV-0 precondition (and doubles as the campaign's first real diagnosability exercise), the laptop's CUDA-redist bundling must be verified per-box, and PR #81/#82 must merge first. The plan produces the §6 EVIDENCE only -- the flip itself stays gated on an explicit recorded product decision, per the spec. Co-authored-by: Claude Fable 5 <noreply@anthropic.com>

coderabbitai

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@docs/CURRENT_STATE.yaml`:
- Around line 107-109: Synchronize the real-model E2E evidence lane’s status by
adding the same pending-merge qualifier used in docs/ROADMAP.md lines 662-663 to
docs/CURRENT_STATE.yaml lines 107-109 and docs/ROADMAP.md line 676; update both
locations consistently, unless PR `#81` has landed, in which case record the
completed status instead.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

Push a commit to this branch (recommended)
Create a new PR with the fixes

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: 3332c831-f8c6-4594-9235-0de916ea93f8

📥 Commits

Reviewing files that changed from the base of the PR and between aa07f41 and 611dfb5.

📒 Files selected for processing (2)

docs/CURRENT_STATE.yaml
docs/ROADMAP.md

coderabbitai · 2026-07-20T14:20:57Z

+      real-model E2E lane with a retained JSON evidence artifact (discovery
+      through real admission through inference through telemetry;
+      25.7 tok/s, 284ms TTFT, 2.5GB measured VRAM on the reference box) are


🗄️ Data Integrity & Integration | 🟡 Minor | ⚡ Quick win

Synchronize the E2E evidence lane’s merge status across both documents.

The foundation note and Phase 3 roadmap row omit that the real-model evidence lane is still pending merge, while docs/ROADMAP.md Lines [662-663] and the PR summary preserve that status.

docs/CURRENT_STATE.yaml#L107-L109: add the pending-merge qualifier, or update after PR #81 lands.

docs/ROADMAP.md#L676-L676: use the same pending-merge wording as Lines [662-663].

📍 Affects 2 files

docs/CURRENT_STATE.yaml#L107-L109 (this comment)

docs/ROADMAP.md#L676-L676

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@docs/CURRENT_STATE.yaml` around lines 107 - 109, Synchronize the real-model E2E evidence lane’s status by adding the same pending-merge qualifier used in docs/ROADMAP.md lines 662-663 to docs/CURRENT_STATE.yaml lines 107-109 and docs/ROADMAP.md line 676; update both locations consistently, unless PR `#81` has landed, in which case record the completed status instead.

CodeRabbit finding: ROADMAP.md's banner still said the E2E lane was "built, verified on real hardware, and pending merge" while CURRENT_STATE.yaml's parallel note omitted that qualifier entirely -- inconsistent, and now stale either way since PR #81 actually merged. Updated both to say landed. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>

hardcoreerik · 2026-07-20T14:23:28Z

@coderabbitai full review

coderabbitai · 2026-07-20T14:23:48Z

✅ Action performed

Full review finished.

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

coderabbitai Bot reviewed Jul 20, 2026

View reviewed changes

hardcoreerik merged commit 4b51450 into master Jul 20, 2026
2 checks passed

hardcoreerik deleted the docs/sync-roadmap-native-runtime-v2 branch July 20, 2026 14:27

Navigation Menu

docs: sync ROADMAP/CURRENT_STATE with Native Runtime v2.0 Phase B addendum + D - #82

docs: sync ROADMAP/CURRENT_STATE with Native Runtime v2.0 Phase B addendum + D#82
hardcoreerik merged 2 commits into
masterfrom
docs/sync-roadmap-native-runtime-v2

hardcoreerik commented Jul 20, 2026 •

edited by coderabbitai Bot

Loading

Uh oh!

coderabbitai Bot commented Jul 20, 2026 •

edited

Loading

Review limit reached

Walkthrough

Changes

Uh oh!

hardcoreerik commented Jul 20, 2026

Uh oh!

coderabbitai Bot commented Jul 20, 2026 •

edited

Loading

Uh oh!

hardcoreerik commented Jul 20, 2026

Uh oh!

coderabbitai Bot commented Jul 20, 2026 •

edited

Loading

Uh oh!

hardcoreerik commented Jul 20, 2026

Uh oh!

coderabbitai Bot commented Jul 20, 2026 •

edited

Loading

Uh oh!

coderabbitai Bot left a comment

Uh oh!

coderabbitai Bot Jul 20, 2026

Uh oh!

hardcoreerik commented Jul 20, 2026

Uh oh!

coderabbitai Bot commented Jul 20, 2026 •

edited

Loading

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

Conversation

hardcoreerik commented Jul 20, 2026 • edited by coderabbitai Bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Summary

Summary by CodeRabbit

Uh oh!

coderabbitai Bot commented Jul 20, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Review limit reached

Walkthrough

Changes

Uh oh!

hardcoreerik commented Jul 20, 2026

Uh oh!

coderabbitai Bot commented Jul 20, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

hardcoreerik commented Jul 20, 2026

Uh oh!

coderabbitai Bot commented Jul 20, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

hardcoreerik commented Jul 20, 2026

Uh oh!

coderabbitai Bot commented Jul 20, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

coderabbitai Bot left a comment

Choose a reason for hiding this comment

Uh oh!

coderabbitai Bot Jul 20, 2026

Choose a reason for hiding this comment

Uh oh!

hardcoreerik commented Jul 20, 2026

Uh oh!

coderabbitai Bot commented Jul 20, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

hardcoreerik commented Jul 20, 2026 •

edited by coderabbitai Bot

Loading

coderabbitai Bot commented Jul 20, 2026 •

edited

Loading

coderabbitai Bot commented Jul 20, 2026 •

edited

Loading

coderabbitai Bot commented Jul 20, 2026 •

edited

Loading

coderabbitai Bot commented Jul 20, 2026 •

edited

Loading

coderabbitai Bot commented Jul 20, 2026 •

edited

Loading