Even though secp256k1_musig_nonce_gen_internal can currently only fail if the surrounding API function is misused (invalid keypair or keyagg_cache parameters, making the corresponding seckey validation or pubkey/keyaggcache load calls fail), clearing out the stack memory holding the secret key as well in this case seems reasonable to follow best practices.
The issue was reported off-band by l0rinc (thanks!), in the course of analyzing the secp repository with AI tooling.