compute-env-setup

1# Compute environment setup
2 
3Prepare one reproducible environment definition and instructions for one small user-managed host
4activation file. Open-Science resolves `submitJob(..., { environment: '<name>' })` by sourcing
5`~/.open-science/environments/<name>.sh` before the workload. Existing `~/.openscience/environments/<name>.sh` definitions remain readable in place. Before creating an activation, check both names: update the existing definition at its exact location; if both exist, ask the user which to retain. Never create a second activation just to rename the brand. The file contains activation only; it
6does not install packages when a job starts.
7 
8Software environment setup and Slurm accounting service configuration are separate concerns.
9An unavailable `sacct` service is not evidence that Python, Conda, modules, or the named activation
10file are missing. Use the Remote Compute Skill's Slurm troubleshooting reference for scheduler
11status and cancellation problems; do not make enabling accounting the only recovery path or assume
12the user has administrator privileges.
13 
14The environment, package caches, images, and activation file are user-managed durable resources,
15not Open-Science-owned components. This Skill may inspect them and prepare exact setup/removal
16commands, but must not execute commands that create, replace, or remove those resources. The user
17or host administrator runs those commands outside Open-Science and owns their lifecycle. Do not
18…