Issues running kclaim style proofs

• Re-executing a KClaim (with --save-directory) where a proof changes or a dependency changes, does not trigger --reinit behavior. We should be parsing the claims, and invalidating any claims where the claim itself or a dependency has changed.
• Parallel proof discharge waits for each batch of proofs instead of adding to the queue of tasks asynchronously. This means that if there a few really long running proofs in one layer of proofs, we won't move on to the proofs in the next layer who's dependencies are already discharged.
• Proofs whos dependencies are not discharged should not be run unless the dependency is admitted or the user specifies to admit dependencies. Perhaps?

Start by tracing the --save-directory and --reinit handling, then inspect how proof dependencies and parallel batches are queued. Done means changed claims or dependencies are invalidated, eligible proofs are queued without unnecessary batch waits, and proofs with undischargeable dependencies follow the stated admission rule.