Changes

Support reusable JAX driver initialization and runtime batches (#1380)

This is just getting the jax driver to be more in line with fortran. It was lacking features like being able to start/stop at a certain timestep. Certain driver tests were also missing, which got added and included in the driver jenkins test.


* Support reusable JAX driver state and runtime batches

* Keep JAX lifecycle coverage with native driver tests and document its origins

* Mirror the native driver lifecycle test and compare complete JAX statistics

* Run JAX driver extensions as an independent step in the lifecycle stage

* Update the C8 comparison mutation for indexed parameter loading

Port JAX restart initialization and test normal and SILHS continuation (#1381)

This makes jax restarts work. Also adding jax restart test stages in the existing jenkins restart test.

* Port JAX restart initialization and exercise native and SILHS restarts

* Describe restart validation and dependencies for the focused PR

* Describe JAX restart scenarios and their native source equivalents

* Keep JAX restart validation in the shared harness and exercise distinct columns

Port standalone JAX loss evaluation and consistency checks (#1382)

This adds the capability for the jax to run and compute loss vs les data the same as fortran does. Fortran uses the "loss driver" which does this, and has some additional testing code and a clubb_standalone_loss program that supports that, so this was basically just porting more of the high level fortran code to jax and hooking it up with some of the high level python scripts the tuner uses.


* Support reusable JAX driver state and runtime batches

* Add standalone JAX loss evaluation and consistency coverage

* Keep standalone loss CLI coverage separate from tuning

* Remove trailing whitespace from extracted loss CLI tests

* Run JAX loss help checks in the JAX pytest suite

* Keep JAX lifecycle coverage with native driver tests and document its origins

* Document loss test scenarios, native counterparts and JAX extensions

* Keep the native loss executable path intact in the test description

* Mirror the native driver lifecycle test and compare complete JAX statistics

* Run JAX driver extensions as an independent step in the lifecycle stage

* Update the C8 comparison mutation for indexed parameter loading

* Reject unsupported loss restarts before opening model resources

* Clean up merged loss launcher state and document early restart rejection

* Move loss frontends and tests out of the tuner package

Call the existing Fortran Python API directly from its installed standalone loss frontend, and keep the JAX standalone frontend with its source port. Share unchanged table formatting, relocate lifecycle and CLI coverage, and update runners and documentation.