[faceofcat]

Machines can now run recipe cycles while reserving their inputs and output space, preserve progress across saves and interruptions, and synchronize processor state and reservations with their menus. A separately packaged companion mod demonstrates the API with four playable machines.

Changes

• Add slot/tank reservation plans, transactional cycle completion and rollback, recipe processors, and a feature host for ticking, persistence, and synchronization.
• Respect reservations in automation and menu interactions, including client prediction, partial transfers, interruption/resume, and multiple processors sharing storage. Preserve contents correctly when machines are broken or replaced.
• Add the optional mmdlib_companion source set and jar: Crusher, one-slot Converter, Dual Crusher, and Creative Power Source. Keep companion and test content out of the library jar.
• Add reusable energy gauges and bookmark-style information drawers; update recessed slots, shaded progress arrows, and fluid rendering. The Crusher's water/lava preview tank supports held and cursor fluid containers without mixing fluids.
• Fix persistence after in-place shift-click merges and partial extraction: server-side machine slots now notify the block entity when vanilla changes a stack directly.
• Document the processor, reservations, screen components, and companion setup.
• Merge the latest base build/release changes, migrate companion runs to ModDevGradle, and consolidate CI into build_status.yml. Remove duplicate ci.yml while retaining library GUI smoke tests with/without JEI, adding the companion smoke, and preserving diagnostic artifacts.

Validation

• ./gradlew check passed after integrating base commit 1a11cdc: 91 JUnit tests and 76 server game tests (65 library, 11 companion), plus asset, import, and packaging checks.
• Both shift-click persistence regressions failed before the fix and pass afterward. They check the chunk save flag and saved item counts; a rejected transfer leaves the save flag unchanged.
• runCompanionClientSmoke passed under ModDevGradle, opening all four networked menus and checking synchronized values and fluid-container transfers. Partial, full, and empty gauges were visually inspected during UI validation.
• The library GUI smoke passed with and without JEI under the merged build setup. Consolidated workflow YAML parsed successfully.
• build verifyReleaseClasses verifyCompanionPackaging passed after the GUI runs, confirming release artifacts exclude injected test content.

Integration note

The build/release-system changes from #89 are merged into this branch with a merge commit; existing feature history is preserved. The shared base workflow now owns build/check and GUI validation, without a second duplicate check job.