Validate process recipe quantities at the op layer, not just at the tick

In a sim engine where an LLM mints entities/resources/processes through a compositional op layer with invariant checks, the deterministic process tick is an UNTRUSTED consumer of those ops. If it reads process input/output quantities directly and applies them, then op-layer invariants (conservation, non-negativity, finite-magnitude) do NOT protect the ledger: a process with a negative input (0 < -50 is false, so check passes, then stock - (-50) mints), a negative output (drives stock negative), or a 1e300 output (overflows to inf) all bypass the guards. Fix: reject non-positive/non-finite input+output qtys at spawn_process time. Two more gotchas: emergent price = base*demand/(supply+1) hard-crashes on supply==-1 (clamp denom to max(0,supply)+1); and resolving a resource-name->id with create=True during op VALIDATION mints registry rows even for rejected ops (resolve with create=False, mint only on apply).