docs: refresh README and testing guidance

[ryanbarlow97]

Move detailed test fixture notes into Docs and clarify the README testing summary.

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: 87ca1038-d4dc-4cc3-930b-2891ee5266ef

📥 Commits

Reviewing files that changed from the base of the PR and between 76aa3ab and 6ac476a.

📒 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
  • Updated the testing and coverage guidance with report locations, CI upload details, coverage requirements, and rules for skipped or focused test runs.
  • Added a link to the testing guide for fixture isolation and checking local reports.

Walkthrough

The README testing section now summarises test areas, coverage requirements, report locations, and CI uploads. It also links to the testing guide for fixture isolation and local report checks.

Changes

Testing documentation

Layer / File(s)	Summary
Test coverage and reporting guidance README.md	The section lists test areas, report paths, CI uploads, the 100% production coverage requirement across five metrics, and the rejection of skipped tests. It links to the testing guide and notes the limits of focused test runs.

Priority: ⬇️ Low

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

Change: Other

Merge Risk: ⚪ Minimal · up to 6ac47

The README’s coverage statement matches the build configuration, and the supplied evidence supports its CI guidance. No actionable merge-blocking risk remains for this documentation-only change.

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