docs(hive): mark August 2026 scope as internal-only

[100yenadmin]

Tracker/doc realignment for the evaOS Teams August program (Lane E).

What

Adds an August 2026 = INTERNAL ONLY scope banner to the two Electric-authored scope documents:

• VISION_HIVE.md
• docs/hive-thin-adapter-runbook.md

Zero customer exposure this month; ElectricSheep-internal dogfood of the v0.5.2-es Internal Canary only. Mobile/Windows out of scope.

Milestone disposition (already applied on the tracker)

• Milestone Upstream: first-class Hermes ACP runtime in Buzz #2 Hive — Guarded Business Beta → deferred note added, left OPEN
• Milestone Upstream: persist channel-to-ACP session mapping and resume after restart #3 Hive 1.0 — General Rollout → deferred note added, left OPEN

Deferred, not dropped: gate issues #11 #12 #40 #62 #79 #13 stay open and unedited, and both milestones are re-scoped at the September readiness read.

Deliberate deviation from the program plan (please note)

The program plan said "add an internal-only August scope banner to the 8 VISION*.md files." Seven of those eight are upstream Buzz documents — VISION.md, VISION_ACTIVITY.md, VISION_AGENT.md, VISION_MESH.md, VISION_MODERATION.md, VISION_PROJECTS.md, VISION_SOVEREIGN.md were last touched by upstream PRs block#1776, block#1381, block#1285, block#1616 — and they describe Buzz, not the Electric adapter.

Banner-ing them would add seven permanent merge-conflict points against stock Buzz v0.5.2 on every upstream pull, for no reader benefit. That is exactly the "fattens the adapter" tripwire, so the banner is confined to the two Electric-authored docs and the runbook says so explicitly. Escalated to Fable via status/E-hive.md; happy to widen if overruled.

Verification

Docs only — no code, no behavior change, no adapter surface change.

[coderabbitai]

Warning

Review limit reached

You’ve reached a temporary PR review limit under our Fair Usage Limits Policy.

Your recent review volume is higher than typical usage, so adaptive limits are currently applied.

Next review available in: 37 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: Organization UI

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: a44d48bd-3103-49ff-a1fd-cb08a9a2211a

📥 Commits

Reviewing files that changed from the base of the PR and between 38c68e2 and 434c5f9.

📒 Files selected for processing (2)

• VISION_HIVE.md
• docs/hive-thin-adapter-runbook.md

Warning

Billing warning: we have not been able to collect payment for this subscription for more than 72 hours. Please update the payment method or pay any pending invoices in Billing to avoid service interruption.

---

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

[100yenadmin]

Fable sign-off: merged. Deferred-not-dropped framing + thin-adapter discipline (upstream VISION files untouched) both correct.