Hopper validation on October 5, 2026

366383: bundled demo using existing environment, COMPLETED 0:0
366384: freshly installed pinned environment, COMPLETED 0:0
366385: Miniforge initialization with fresh environment, COMPLETED 0:0

Verified: two parallel chains, posterior mean check, RDS reload with 3000 draws, CSV, session record, trace and density PDF visual inspection, Conda exports.
Miniforge 26.7.2-0: official installer download, SHA256 verification, batch installation succeeded. Interactive prompts were not automated.
Fixed: checksum URL must use versioned release asset.
Added: optional JAGS_ENV_PREFIX for isolated testing; default remains ~/.conda/envs/jags.
Not validated: other users account permissions, research model and dependencies, CRAN archive fallback, full environment restore.
Remote validation files retained at ~/codex-jags-validation-20261005; existing ~/.conda environment was not replaced.

Polished helpers: job 366462 COMPLETED 0:0; activate.sh, submit.sh, status.sh and Slurm CPU-count handling verified.

Readability and helper revision, October 6, 2026

366465: first submission with prompted settings, COMPLETED 0:0.
366466: new SSH session, no interactive input; reused saved settings, COMPLETED 0:0.
366468: rebuilt environment from the explicit Conda export, reinstalled jagsUI,
then submitted hello.R on main with --cpus-per-task 4. COMPLETED 0:0 with PASS.
This supersedes the earlier full-environment-restore limitation. The demonstration
still uses two chains; four allocated CPUs verifies the resource override, not
four-chain scaling. All tests used ndodds's authorized standard account.

Seven local submission tests pass: reconnect persistence, argument boundaries,
per-run resource overrides, failed-submission preservation, invalid/missing inputs,
settings treated as data, copied-user settings, reset recovery, and help behavior.
Other users' permissions, research models/dependencies, interactive installer
prompt navigation and the CRAN archive fallback remain untested.
