- drop per-guide Validation sections; manual gates stay in MANUAL_CHECKS
- drop audit/provenance lines (reference checkouts, dated refreshes, commit pins)
- state version status and Scala-free compile check once in API.md
- replace API.md status prose with link to migration status
- fix RELEASE_NOTES dangling sentence
- rewrite README for GTNH fork and Java port
The notes told consumers what breaks on rebuild but not whether the
migration they are being asked to make is final. Without that, the
reasonable reading is that adopting the Java surface now buys a second
migration when the Scala runtime is removed later.
State the guarantee: the removal release drops the Scala-shaped entry
points and keeps their Java siblings, so one migration to the documented
surface is the whole cost. Name the one way to pay it twice, which is
aiming at a raw dev-jar class such as scalatraits.TRedstoneTile instead
of the stable IRedstoneTile capability interface. That is the mistake a
failing rebuild invites, and it fails at runtime in between.
Record two limits honestly: the guarantee covers the documented and
audited surface, which is why removal waits on adoption evidence rather
than source patches, and the source-layout move out of src/main/scala
changes no class, package or descriptor and so is invisible.
Algent