[DevOps]: v3 data diagnostics backfill

[tomvothecoder]

Task Details

After #281 is complete and the E3SM v3 data has been ingested, backfill the corresponding diagnostic links.

Steps to Complete

Create a one-time script that scans the LCRC web diagnostics path and:

1. Identifies diagnostic output matching the ingested v3 cases.

2. Copies the matching diagnostic directories into /diagnostics_archive/production.

3. Runs the SimBoard diagnostic scanner.

4. Verifies that the scanner links each diagnostic directory to the correct case using:

   • case_name
   • hpc_username
   • machine_id

Open Questions

• These diagnostic runs predate zppy’s generation of provenance.settings. Determine whether this file can be reconstructed with enough information for SimBoard to process the diagnostics reliably.
• SimBoard obtains CASE_GROUP from env_run*.xml in the E3SM case documentation. Determine whether CASE_GROUP can be recovered for these runs.
• If CASE_GROUP cannot be recovered, place all v3 diagnostic directories directly under /diagnostics_archive/production rather than in case-group subdirectories.

Acceptance Criteria

• The one-time backfill script finds and copies all available v3 diagnostic directories.
• The directory layout is compatible with the SimBoard diagnostic scanner.
• The scanner links each copied diagnostic directory to the correct ingested case.
• The handling of missing provenance.settings and CASE_GROUP metadata is documented.