IC Expansion: Core 1.0.11

Multi-version support

• Restore the maintained Forge 1.19.2 Core implementation as the legacy behavioral baseline.
• Add the NeoForge 26.1.2 Core target for the current FTB Industrial Contraptions line.
• Move version-neutral rules into the shared common module while keeping Minecraft, loader, and FTBIC implementation details version-specific.
• Keep the NeoForge 26.1.2 Large Blast Furnace as an intentional structure-validation scaffold only; recipe processing, energy use, progress, and production inventory are deferred to a later implementation.

Compatibility and architecture

• Give each shipped IC Expansion module ownership of its own registry lifecycle.
• Remove the dormant ftbiceop fallback path; unknown expansion module IDs now fail explicitly instead of silently registering through Core.
• Isolate modern FTBIC generator energy transport behind a version-specific compatibility bridge rather than spreading upstream-private cable/network details through content modules.
• Keep Zap cable transport and FE interoperability aligned with FTB Industrial Contraptions behavior.
• Require NsTut Lib 0.8.1+ within the 0.8.x compatibility line for NeoForge 26.1.2 Core, establishing the dependency contract ahead of the planned Large Blast Furnace multiblock migration.
• Remove the stale mandatory Patchouli dependency from Core; guide integrations are owned by content modules.

Build and release

• Add independent CI lanes for shared tests, Forge 1.19.2, and NeoForge 26.1.2.
• Add an explicit modern verification gate backed by an ephemeral Minecraft server bootstrap that verifies FTB Industrial Contraptions, Core, Generators, and the required modern library dependency load together.
• Publish legacy and modern artifacts under the correct Java/runtime targets.
• Source-control the Core CurseForge description and use per-version release notes for CurseForge and GitHub publishing.

Documentation

• Replace Forge MDK boilerplate with project documentation covering supported targets, dependencies, compatibility rules, development, and the modern port architecture.