docs: refresh README and testing guidance

[ryanbarlow97]

Document test frameworks, report paths, dependency preparation and LuckPerms integration limits.

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: 1bb1d58f-954a-432c-ab02-48aeaacdda9f

📥 Commits

Reviewing files that changed from the base of the PR and between 68d8133 and 4ec2a0b.

📒 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
  • Expanded the test guidance with information on test coverage, report locations, CI uploads and the limits of mock-based testing.
  • Directed readers to the build guide for pinned dependencies.

Walkthrough

The README test instructions now link to the build guide and describe test frameworks, coverage areas, report locations, CI uploads, and the limits of mock-based verification.

Changes

Test documentation

Layer / File(s)	Summary
Test and coverage instructions README.md	The README links to the build guide, names the test frameworks and covered areas, and gives the Surefire report location. It also describes JaCoCo coverage requirements and reports, CI coverage-report uploads, and the limits of mock-based verification.

Priority: ⬇️ Low

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

Change: Other

Merge Risk: ⚪ Minimal · up to 4ec2a

The updated test guidance reflects the configured frameworks, coverage checks, report locations, and mock-based tests. No material merge risk was 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.}