Checkpoint, clip skip and vae settings are not saved normally between sessions.

Nobody has claimed this yet.

Could be a side effect of my fiddling, but none of the gr.state variables are getting saved to the current value.
When one presses "Apply settings" (ie during run_settings), the value which these three gr.state components sends is always the default, thus upon reload they'll be set to: sd_model_checkpoint to null then the first in the list, CLIP_stop_at_last_layers to 1, sd_vae to Automatic (though irrelevant to forge).
As such, I think it would be preferable to exclude any gr.state components from the standard save - it's noted these are meant to be managed by forge anyway.

If anyone with a more standard install can confirm this glitch, that'd be swell.

Start at run_settings and trace how the gr.state variables sd_model_checkpoint, CLIP_stop_at_last_layers, and sd_vae are read during “Apply settings.” Confirm the behavior on reload and ensure the three state values no longer overwrite their current settings during the standard save; verify that checkpoint, CLIP, and VAE settings persist normally between sessions.

Written by the indexing model from the issue text.