Update to Minecraft 26.3

[rubensworks]

Updates to Minecraft 26.3, alongside CyclopsMC/CyclopsCore#243. ./gradlew build passes, unit tests pass, and all 48 game tests are green — including testBlockRecipeHandlerCapBrewingStand, testBlockWorkerCapBrewingstand* and the furnace equivalents, which is what gives confidence in the brewing rework below.

CommonCapabilitiesAPI submodule

The submodule points at eac103d, the current master-26, which carries both the SlotDisplay$TagSlotDisplay HolderSet<Item> fix (CyclopsMC/CommonCapabilitiesAPI#9) and the self-containment fix (CyclopsMC/CommonCapabilitiesAPI#10), both merged.

DataComparator now implements the API's new IDataComparator so that the API compiles without this mod, which is what CyclopsCore needs to track master-26.

Brewing became datapack-driven

This is the substantial part. PotionBrewing is gone, replaced by BrewingRecipe under RecipeType.BREWING plus a BREWING_FUEL component.

• PotionHelperCommonCapabilities reads those recipes instead of walking PotionBrewing's container and potion mixes. That also drops the breadth-first graph walk and its "infinite loop detected" guard, which only existed because brewing was not recipe-driven.
• Potion ingredients are expanded into their container items crossed with the potions their PotionsPredicate allows, and each output is produced by calling the recipe's own assemble, so BrewingRecipe subtypes that derive the output container from the input (as the vanilla mixes do) still come out right.
• The emitted recipe definitions keep the existing four-slot shape — reagent in slot 0, potions in 1 to 3 — so downstream automation is unaffected.
• VanillaBrewingStandRecipeHandler#simulate resolves brewing through the recipe manager.
• BrewingStandBlockEntity#isBrewable now takes the ServerLevel and the block entity, so the worker defers to it rather than reimplementing the check.

The game test asserts at least 279 brewing recipes are enumerated and that every one of them simulates successfully, so this is covered end to end rather than just compiling.

Furnaces

• FuelValues is gone, replaced by the COOKING_FUEL data component. canWork checks for that component rather than a positive burn duration; vanilla itself uses the same check for fuel-slot validity.
• The recipeType field is gone — the furnace holds a cached recipe check instead. That also removes the reflection the worker previously needed.

Other

• BundleContents#itemCopyStream renamed to itemCopies.
• Vanilla's item ids shifted, so the registry-id snapshots in TestIngredientMatcherItemStack move from 1051 to 1162. These assert a raw Item.getId difference, so they are expected to move every version.
• Visual Workbench and Puzzles Lib are compileOnly until they release for 26.3. Their 26.2 builds refuse to load on 26.3 and fail the test JVM's mod loading outright. The mod compat itself only activates when visualworkbench is present, so nothing is lost at runtime; there is a TODO to put them back on implementation.

---

Generated by Claude Code

[rubensworks]

Heads-up on merge order: DataComparator now implements the new IDataComparator from the API, and the submodule points at d9a3254 on the branch of CyclopsMC/CommonCapabilitiesAPI#10.

Please merge that PR first. If it is squashed, the pin here becomes an orphan commit, so I will move it to the resulting master-26 commit right after and push again.

---

Generated by Claude Code

[rubensworks]

On the red CI here, for the record: the Build job fails while resolving :compileClasspath, before compiling anything.

Could not find org.cyclops.cyclopscore:cyclopscore-26.3-neoforge:1.30.0-1038

That artifact does not exist yet. CyclopsMC/CyclopsCore#243 is the 26.3 update that produces it, and its Deploy to Maven job is skipped on PR branches, so nothing is published until it merges. Every run on this branch since the 26.3 commit has failed on this same line, including the ones before today's IDataComparator change, so it is not caused by anything in this PR and there is nothing to port in.

I build this locally against a publishToMavenLocal CyclopsCore, where build and runGameTestServer both pass. CI here should go green on a re-run once #243 is merged and deployed; no cyclopscore_version bump should be needed, since it already points at 1.30.0-1038.

---

Generated by Claude Code

[coveralls]

coverage: 71.327% (-0.5%) from 71.856% — claude/minecraft-26-3-update-xr1cny into master-26