Build Fabric Systems

activate_when

Use after a proposal is approved and the task requires Fabric source, datagen, a supported entity, resource, system, Gradle build, or GameTest.

inputs

• Approved immutable proposal JSON.
• Exact approval_hash.
• Workspace-relative run/project paths.
• Relevant exact-version evidence bundle.

required_rag

Use minecraft-dev before introducing or repairing Minecraft/Yarn API calls. Use the local evidence catalog for build, metadata, datagen, and GameTest contracts.

allowed_tools

• mmm-local.generate_fabric_project
• mmm-local.run_static_validation
• mmm-local.run_gradle_build
• mmm-local.run_gametest
• mmm-local.inspect_jar
• minecraft-dev read-only source and mapping tools

output_schema

Return source path, validation report, Gradle command receipts, GameTest result, JAR path/hash, repair history, and unresolved plugin blocks.

validators

• Approval hash matches the immutable proposal.
• All paths remain under the configured workspace.
• Static validation passes before Gradle.
• Gradle clean build exits 0 before the build is reported as passing.
• GameTest exits 0 before runtime behavior is reported as verified.
• JAR validation passes independently before release packaging is reported as verified.
• Every repair receipt is bound to the exact pre-repair source hash, diagnostic signature, changed paths, and post-repair source hash.
• Requested functionality is never removed or weakened merely to make a gate pass.

retry_policy

Use progress-driven repair rather than an arbitrary fixed cycle count. After a failed gate, inspect fresh diagnostics and exact source/mapping evidence, apply the smallest coherent repair, and rerun only the invalidated gate plus dependent gates. Continue while the diagnostic signature changes or measurable progress is made. Stop immediately when the same normalized failure signature repeats without new evidence or when a safety/version boundary is reached. Preserve every attempt and receipt.

approval_required

All source writes, builds, tests, and packaging require approval.

forbidden

• Implementing blocked plugins through ad-hoc unreviewed code.
• Editing an uploaded project in place.
• Disabling validation, skipping a failed gate, or publishing an unvalidated JAR.
• Executing arbitrary shell supplied by a model or retrieved page.
• Restarting already-passing independent work solely because another shard failed.

exit_conditions

Exit with VERIFIED only when source, build, GameTest, and JAR gates pass. Return SOURCE_READY, FAILED, or BLOCKED with exact evidence otherwise. A repeated unchanged failure signature is FAILED; a missing external dependency, approval, tool, or exact-version fact is BLOCKED.