Update UM for Jhan's stash change

[Whyborn]

The change to the STASHmaster file causes the code to break with the new STASHmaster_A. I didn't realise this would actually cause the model to break- UM needs to be updated with @JhanSrbinovsky's change to increase the number of allowed stash variables.

---

🚀 The latest prerelease access-am3/pr24-3 at 1dc0b20 is here: #24 (comment) 🚀

[github-actions]

🚀 Attempted to deploy access-am3 Prerelease pr24-1 with commit 33f99c5

🖥️ Gadi Deployment ❌

[github-actions]

🚀 Attempted to deploy access-am3 Prerelease pr24-1 with commit 1dc0b20

🖥️ Gadi Deployment ❌

[JhanSrbinovsky]

From #191 in configs repo:

"Unlike in ESM1.6, we don't actually output any CABLE fields through diagnostics (Thats what required the increased ndiagp parameter)"

[Whyborn]

!redeploy

[github-actions]

🚀 Attempted to deploy access-am3 Prerelease pr24-3 with commit 1dc0b20

🖥️ Gadi Deployment ✔️

Usage Instructions

access-am3, defined in ./spack.yaml, will be deployed to Gadi as:

• 2026.02.000 as a Release (when merged).
• pr24-3 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-am3/pr24-3

When using the above modules, the binaries shall be on your $PATH.

For advanced users, this Prerelease is also accessible on Gadi via /g/data/vk83/prerelease/apps/spack/0.22/spack in the access-am3-pr24-3 environment.
Due to inode-saving measures, one will have to manually untar the environment metadata before environment activation with tar -xf .spack-env .spack-env.tar. It will require one to have write privileges.

Configuration Information

This Prerelease is deployed using:

• access-nri/spack on branch 0.22
• access-nri/spack-packages version 2025.09.004
• access-nri/spack-config version 2026.02.000

If the above was not what was expected, commit changes to config/versions.json in this PR.