docs: add fork-identity banner (evaOS maintained fork of GBrain)

[100yenadmin]

The README identified verbatim as upstream GBrain — first-person "I'm Garry Tan, CEO of YC", upstream bun install -g github:garrytan/gbrain, links to garrytan/gbrain — with no signal this is our maintained fork. An agent (or user) following it cold would use the wrong install path and mis-attribute the project.

Prepends an honest fork-identity banner that:

• labels this as electricsheephq/eva-brain, evaOS's maintained fork of GBrain, crediting upstream with links;
• clarifies fleet install/deploy flows through the evaOS golden runtime + fleet-rollout path, not the upstream bun-install below;
• points to the canonical evaos-support-control/docs/fleet-contract.md.

The upstream marketing body is left intact but clearly demarcated as upstream-origin content. Pure additive docs, reversible, zero code/fleet impact. Part of EPIC-6 garrytan#271.

Optional owner follow-up (taste): a deeper rebrand replacing the upstream first-person pitch with evaOS product framing — deferred as a marketing-voice decision.

[chatgpt-codex-connector]

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.
To continue using code reviews, add credits to your account and enable them for code reviews in your settings.

[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: 42 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: 04244d05-b594-4872-b7e0-4c6bc9eeb41c

📥 Commits

Reviewing files that changed from the base of the PR and between ed9a064 and c0c4a61.

📒 Files selected for processing (1)

• README.md

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch docs/fork-identity

---

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