docs: update wordings in readme

[chilijung]

Minor fixes in the readme

Summary by CodeRabbit

• Documentation
  • Updated all references from "Wren" to "Wren Engine" throughout documentation to reflect current branding.

[coderabbitai]

📝 Walkthrough

Walkthrough

README.md has been updated to consistently reference "Wren Engine" instead of "Wren" throughout the documentation, updating headers, descriptions, and usage instructions to reflect the rebranding.

Changes

Cohort / File(s)	Summary
Documentation Branding Update README.md	Rebranding changes replacing "Wren" references with "Wren Engine" in headers, capability descriptions, and usage instructions (e.g., "Wren helps an agent..." → "Wren Engine helps an agent..."; "Use Wren through MCP" → "Use Wren Engine through MCP").

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• Update README.md #1116: Modifies README.md to adjust references to "Wren Engine" with overlapping branding updates
• Update readme with MCP #1109: Makes overlapping documentation changes to README.md renaming and reframing "Wren" as "Wren Engine" with MCP-related content updates
• add overview image #1154: Updates README with "Wren Engine" branding and content changes

Suggested reviewers

• goldmedal
• douenergy

Poem

🐰 Rebranding hops across the page,
From "Wren" to "Wren Engine" stage,
Each word now wears its fuller name,
Consistency is now the game!
A rabbit's edit, small but bright, 🎉

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Title check	✅ Passed	The title accurately reflects the main change: updating wording/terminology in the README from 'Wren' to 'Wren Engine' throughout the documentation.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch update/readme

📝 Coding Plan

• Generate coding plan for human review comments

---

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 and usage tips.}

[coderabbitai]

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (2)

README.md (2)

181-181: ⚠️ Potential issue | 🟡 Minor

Incomplete terminology update.

Line 181 uses "Wren is built to expose" instead of "Wren Engine is built to expose", which is inconsistent with the terminology standardization goal of this PR.

📝 Suggested fix for consistency

-That last point matters: context only helps agents when it is available at runtime. Wren is built to expose that layer over MCP and APIs.
+That last point matters: context only helps agents when it is available at runtime. Wren Engine is built to expose that layer over MCP and APIs.

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@README.md` at line 181, Update the terminology for consistency by replacing
the phrase "Wren is built to expose" with "Wren Engine is built to expose" in
the README sentence that currently reads "That last point matters: context only
helps agents when it is available at runtime. Wren is built to expose that layer
over MCP and APIs."; ensure the new wording matches the project's standardized
"Wren Engine" usage.

---

122-122: ⚠️ Potential issue | 🟡 Minor

Incomplete terminology update.

Line 122 still uses "Without Wren" instead of "Without Wren Engine", which is inconsistent with the goal of this PR to standardize on "Wren Engine" throughout the documentation.

📝 Suggested fix for consistency

-Without Wren, an agent may know where the data is but still not know how to answer the question correctly.
+Without Wren Engine, an agent may know where the data is but still not know how to answer the question correctly.

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@README.md` at line 122, Update the remaining instance of the phrase "Without
Wren" in the README (the sentence "Without Wren, an agent may know where the
data is but still not know how to answer the question correctly.") to use the
standardized term "Without Wren Engine"; change the text to "Without Wren
Engine, an agent may know where the data is but still not know how to answer the
question correctly." to keep terminology consistent with the rest of the
documentation.

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Outside diff comments:
In `@README.md`:
- Line 181: Update the terminology for consistency by replacing the phrase "Wren
is built to expose" with "Wren Engine is built to expose" in the README sentence
that currently reads "That last point matters: context only helps agents when it
is available at runtime. Wren is built to expose that layer over MCP and APIs.";
ensure the new wording matches the project's standardized "Wren Engine" usage.
- Line 122: Update the remaining instance of the phrase "Without Wren" in the
README (the sentence "Without Wren, an agent may know where the data is but
still not know how to answer the question correctly.") to use the standardized
term "Without Wren Engine"; change the text to "Without Wren Engine, an agent
may know where the data is but still not know how to answer the question
correctly." to keep terminology consistent with the rest of the documentation.

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 8ad8582d-e345-4b23-a536-3f16e5e9f3cc

📥 Commits

Reviewing files that changed from the base of the PR and between 926cedc and 0705b63.

📒 Files selected for processing (1)

• README.md