[Compatibility] Productive Metalworks deterministic recipe integration

[swear01]

Scope

• Mod: Productive Metalworks
• Mod ID: productivemetalworks
• ATM10 representative version: 1.15.0
• Artifact source: https://www.curseforge.com/minecraft/mc-mods/productive-metalworks/files/all?page=1&pageSize=20&showAlphaFiles=hide&version=1.21.1
• SHA-256: pending acquisition and local verification by the assigned worker; do not substitute platform metadata for a computed SHA-256.

Audit starting point

• Candidate recipe classes/families: unresolved; the worker must enumerate every compat-kit scan candidate, then manually classify each class/family before any implementation.
• Candidate stations/catalysts: unresolved; exact owning stations/catalysts must come from the representative artifact and matching official source.
• Typed resources: unresolved; item/fluid/energy/chemical/mana/addon-resource semantics must be proven per accepted family.
• Determinism risks: dynamic machine state, chance, world/entity access, generic ingredient surfaces, capability mutation, multi-block/live-state behavior, remainders, catalysts/tools, and non-atomic resource conversions are fail-closed until source-backed proof exists.
• Explicitly excluded: runtime reflection or class-name/serializer/EMI/JEI inference; client authority; generic getIngredients() inference; silent skips; third-party EMI workstation registration; any unresolved or nondeterministic family.
• Known domain boundary: the public project describes a foundry multiblock. Treat all multiblock/live-foundry state as unsupported unless a complete deterministic transaction contract is proven.

Acceptance checklist

• Obtain the exact representative artifact and record URL, version, SHA-256, and official-source revision where available.
• Run Compat Kit scan then decide; manually review every candidate and preserve explicit rejections.
• Complete the committed audit and contract with exact recipe, station, input/catalyst/tool/remainder, typed-resource, output, rate/work, and determinism evidence.
• Create the RED scaffold/test, confirm the expected failure, then implement only through the public modular compatibility SDK.
• Add present-mod real-behavior assertions plus atomic shortage/capacity/overflow/stale-holder/rollback coverage or an evidence-backed fail-closed result.
• Run Compat Kit verification, applicable fixture/GameTest, modular-SDK Python tests, git diff --check, and required full PR gates under the heavy-Gradle semaphore.
• Update all affected active documentation.
• Open a draft PR linked to this issue, obtain current-head GitHub CI and independent external GitHub bot-review evidence, then merge through GitHub only.

Campaign tracking

• Umbrella: [Compatibility] Audit and expand deterministic support for ATM10 1.21.1 #33
• Branch: pending
• Worktree: pending
• PR: pending
• Review evidence: pending
• CI evidence: pending
• Merge SHA: pending

[swear01]

Coordinator dispatch: branch compat/issue-42-productivemetalworks; worktree ../Auto_Storage-worktrees/issue-42-productivemetalworks; primary worker model cursor-grok-4.5-high; heavy Gradle work is globally limited to two slots.

[swear01]

Worker evidence (Productive Metalworks 1.15.0)

PR: #46 (ready for review; external bot left to review controller)

Outcome C — fail-closed. Zero production recipe families.

Item	Value
Artifact	productivemetalworks-1.21.1-1.15.0.jar
SHA-256	1dcf9e10fc457c92d9ed466336104927169817cd509ca9ca69dec734f994d124
Source	7c6483c51e1a9def633a939ea75e0018dd079ffa
Audit	compat/audits/productivemetalworks/1.15.0.json (23 candidates, all rejected)
Contract	compat/contracts/productivemetalworks.json
Compat Kit report	build/compat-kit/productivemetalworks-report.json (12/12 passed)
Fixture	runProductivemetalworksGameTestServer — 8/8 passed
Matrix	3/3 passed; craftable workload 12,232
build / runData / scripts unittest	green / no datagen drift / 409 OK

Issue template incorrectly named Oritech; this worker followed Productive Metalworks scope from the coordinator + umbrella #33.

[swear01]

Coordinator correction: the original issue body was assigned from an unordered local-file listing. This replaces it with the correct productivemetalworks scope and artifact metadata. The dedicated branch, worker, local acceptance evidence, and PR scope were already correct.