[jaymar921]

Sets up a Gradle module for every version and loader that final releases ship on, so the 1.1.0 port is only porting work. Not a beta: no version bump, the changelog entry stays under Unreleased.

Modules

19 placeholder modules, each pinning its loader, mappings and Java version and holding only an entry point that logs at startup:

Minecraft	Java	Forge	NeoForge	Fabric API
26.2	25	65.1.5	26.2.0.93	0.161.0+26.2
26.1	25	62.0.9	26.1.2.126	0.145.1+26.1
1.21.11	21	61.2.4	21.11.48	0.141.6+1.21.11
1.21.5	21	55.1.18	21.5.101	0.128.2+1.21.5
1.20.6	21	50.2.14	20.6.144	0.100.8+1.20.6
1.20.2	17	48.1.0	-	0.91.6+1.20.2
1.19.4	17	45.4.5	-	0.87.2+1.19.4

Fabric Loader is 0.20.1 everywhere; 26.x uses plain Loom, 1.21.11 and older the remap plugin with Mojang mappings. The existing 26.3 and 1.21.1 modules are untouched.

• scaffold=true in a module's gradle.properties makes gradle/loader.gradle leave out common, minecraft-<version> and JSpecify (NeoForge 1.21.11, 26.1 and 26.2 pin JSpecify 1.0.0), and add the 26.3 icon.
• platforms is still forge-26.3, so CI and betas build one jar. A placeholder builds with ./gradlew :forge-1.20.2:build -Pplatforms=forge-1.20.2.
• No NeoForge 1.20.2: ModDevGradle cannot set it up (20.2 publishes no moddev bundle), so NeoForge starts at 1.20.6. That makes 25 jars per final release.

Docs

ROADMAP supported versions and phase 13 rewritten for the new list (1.20.1 is gone, older versions are no longer frozen), DEVELOPMENT.md gets a "Placeholder modules" section, ARCHITECTURE, README and CHANGELOG updated.

Testing

• All 19 modules build.
• Forge 1.19.4, Fabric 26.1 and NeoForge 1.20.6 dedicated servers start and log the placeholder line.
• Default build (forge-26.3 and tests) is green.