docs: refresh README and testing guidance

[ryanbarlow97]

Describe current character focus and ordinary lectern book behavior; document test tools and reports.

Follows the README layout and documentation ownership rules in TF-Minecraft/Docs. Related guide updates: TF-Minecraft/Docs#110.

Validation: git diff --check; README links, source paths and anchors checked against the task worktrees. Feature and test claims checked against current source and build configuration. Plugin/runtime suites were not rerun for these documentation edits.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

• Configuration used: Organization UI
• Review profile: CHILL
• Plan: Advanced
• Run ID: ec0939ff-6325-4209-b09b-403d4e68bc15

📥 Commits

Reviewing files that changed from the base of the PR and between ff26ef1 and 1e65878.

📒 Files selected for processing (1)

• README.md

Included review availability: This review used your included allowance. Your plan provides up to 1 included review per hour; 0 remain after this review.

---

📝 Summary

Summary by CodeRabbit

• Documentation
  • Clarified that experiments use character focus rather than mental points.
  • Added guidance on how lecterns without an active project handle written books and books and quills.
  • Expanded testing instructions with links to build dependency guidance, details on test coverage and libraries, the location of test reports, and a note that live integrations require server testing.

Walkthrough

The README now describes experiments as spending character focus, documents ordinary lectern behaviour, and expands the testing instructions.

Changes

README guidance

Layer / File(s)	Summary
Project and testing guidance README.md	The project description refers to character focus. The Features section describes lecterns without an active project accepting and opening written books and books and quills. Testing instructions describe the test libraries, coverage, report location and server testing for live integrations.

Priority: ⬇️ Low

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

Change: Other

Merge Risk: ⚪ Minimal · up to 1e658

The README clarifies focus costs, lectern behavior, and test guidance; no concrete documentation mismatch is established, so no actionable merge risk is identified.

• Autopilot · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

---

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.}