Emit an event when a crafting job is completed

[rubensworks]

Groundwork for #175 (toast notifications for completed crafting jobs). This PR only adds the hook; the toast itself lives in CyclopsMC/IntegratedTerminals#214.

What

CraftingJobFinishedEvent

A new event on the NeoForge event bus, emitted from CraftingNetwork#onCraftingJobFinished for jobs that ran to completion.

Two details worth calling out:

• Cancelled jobs are excluded. CraftingNetwork#cancelCraftingJob cannot simply skip emitting, because it delegates to the crafting interface, which finalizes the job through the regular finishing logic a tick later. So cancelling marks the job via a new transient CraftingJob#isCancelled, which the emit checks. Jobs that disappear together with their crafting interface never reach onCraftingJobFinished at all, so they emit nothing either.
• isRootJob() is captured when the event is constructed. The event is emitted for every completed job, including dependencies, and consumers generally only care about the job that was requested. CraftingJobDependencyGraph#onCraftingJobFinished clears the job's dependent links right after the emit, so reading getDependentCraftingJobs() later would report every job as a root job.

CraftingJob#notifyInitiator

A persisted flag next to the existing initiatorUuid, with which an initiator indicates that it wants to be notified once the job is completed. Set through a new CraftingHelpers#scheduleCraftingJobs overload; the existing signature delegates to it with false, so nothing changes for current callers.

CraftingJob#initialAmount

A persisted copy of the amount as it was when the job was scheduled. The regular amount is decremented while the job runs and is zero by the time the job finishes, so it cannot be used to describe what the job produced. Set for every scheduled job, not just for initiator-driven ones.

Tests

Three game tests in GameTestsCraftingJobFinishedEvent, each on the basic crafting network:

• a completed job emits exactly one event for the requested job, carrying the initiator, the notify flag, and its initial amount
• the notify flag stays unset when the initiator did not ask for it
• a cancelled job emits no event

Each test filters events by a random initiator UUID, so concurrently running tests do not interfere.

Compatibility

Both new NBT fields default to false/0 when absent, so crafting jobs saved by older versions load unchanged. Jobs that were already running when a world is updated report an initialAmount of 0, which consumers should treat as unknown.

🤖 Generated with Claude Code

https://claude.ai/code/session_01QNDY2pZtkXqJrhztYCvNbh