Fabricated Backpacks 1.0.0 - Minecraft 26.3

Stable 1.0.0 release, replacing the alpha version designation.

• Updated Minecraft 26.3 APIs for cooking fuels, item drops, placement, loot, rendering and input while preserving backpack storage and upgrades.
• Fabric build targets Loader 0.19.5; Quilt build targets Loader 0.30.1.
• Forge build targets Forge 66.0.2; NeoForge build targets NeoForge 26.3.0.7-beta. Both are native ports: items, fluids and energy go through each loader's own capability system (ForgeCapabilities handlers on Forge, Capabilities handlers on NeoForge), networking and events use the loader's own APIs, and neither JAR bundles Fabric API or Team Reborn Energy.
• Includes the previous 0.5.2 fixes for menu-safe key bindings, exact item counts, contextual help, reversible compacting and larger jukebox libraries.
• Replaced unnecessary mixins with loader APIs, owned storage/block behavior and read-only test helpers. Necessary gameplay hooks remain where the target loader has no equivalent API; features and verification checks have not been removed.
• Fixed indexed item transfers bypassing void-upgrade rules. Overflow mode now checks the whole backpack before discarding items, while preserving rollback and the caller's selected slot.
• Fixed native-loader fluid-container handling and nested inventory rollback, including water bottles, combined storage capabilities and original stack references. Forge steam-engine hoppers now respect sided fuel/output rules.
• Kept NeoForge equipment contents on an explicit owner-only network channel; other players receive only sanitized appearance data, including on late join.

Choose the artifact for your loader. Fabric and Quilt need the matching Minecraft 26.3 Fabric API; Forge and NeoForge need no additional mods. Back up worlds before upgrading.

Verification per loader, all in GitHub Actions on Java 25 with a virtual display and software audio; no manual installed-JAR testing or human-audible sound check was performed, at the owner's request. Each published artifact has its own checksum and its own verification receipt describing exactly what its run covered.

• Fabric and Quilt: 497 unit tests and 170 server GameTests each, asset and production-JAR audits, the full automated client acceptance, a separate-process saved-world restart, and an actual two-process multiplayer check.
• NeoForge: 509 unit tests and 173 server GameTests, asset and production-JAR audits, full automated client acceptance, a separate-process saved-world restart, and actual two-process multiplayer including private equipment sync.
• Forge: 515 unit tests and 173 server GameTests passed, along with asset and production-JAR audits. Full client acceptance stopped at a transfer synchronization assertion; restart and multiplayer checks were not completed. The test now waits for actual server/client pickup before placement, but this correction was compile-checked only and has not been rerun. Publication with incomplete client verification was explicitly requested by the owner; the Forge manifest is not a passing verification receipt.

Production artifact build commits: Fabric 068326e, Quilt 6f04e84, Forge 06eab9a, NeoForge 4e58a01. Later test-only and publishing-policy commits do not change those production JARs.