cleanup normalized CI script option references, remove old CI script doc references

Author: speediedan

.github/CONTRIBUTING.md

@@ -177,7 +177,7 @@ To setup a local development environment, install both local and test dependenci
 
 ```bash
 cd ~/repos/finetuning-scheduler
-./scripts/build_fts_env.sh --repo_home=${PWD} --target_env_name=fts_latest
+./scripts/build_fts_env.sh --repo-home=${PWD} --target-env-name=fts_latest
 
 # Activate (use your venv base path)
 export FTS_VENV_BASE=~/.venvs
@@ -198,17 +198,16 @@ uv pip install pre-commit
 pre-commit install
 ```
 
-**Manual installation with PyTorch nightly:**
+**Manual installation with a PyTorch prerelease (nightly/test):**
 
-When testing against PyTorch nightly builds, use a two-step installation approach:
+When testing against a PyTorch prerelease (nightly or test), use a two-step installation approach:
 
 ```bash
 cd ~/repos/finetuning-scheduler
 
-# Step 1: Install PyTorch nightly (adjust version and CUDA target as needed)
-# Check requirements/ci/torch-nightly.txt for the current nightly version
-uv pip install --prerelease=if-necessary-or-explicit torch==2.10.0.dev20251124 \
-    --index-url https://download.pytorch.org/whl/nightly/cu128
+# Step 1: Install a PyTorch prerelease (adjust version and CUDA target as needed; see configuration in requirements/ci/torch-pre.txt)
+# Example (nightly):
+uv pip install --prerelease=if-necessary-or-explicit torch==2.10.0.dev20251124 --index-url https://download.pytorch.org/whl/nightly/cu128
 
 # Step 2: Install FTS with Lightning commit pin (torch already installed, will be skipped)
 export UV_OVERRIDE=${PWD}/requirements/ci/overrides.txt

.github/copilot-instructions.md

@@ -23,7 +23,7 @@ FTS supports both standalone and unified Lightning packages:
 
 - When set, installs Lightning from a git commit (specified in `requirements/ci/overrides.txt`)
 - Default in dev/CI builds for consistent testing against latest Lightning changes
-- Can be disabled with `--no_commit_pin` flag in build scripts
+- Can be disabled with `--no-commit-pin` flag in build scripts
 
 ## Code Standards
 
@@ -65,7 +65,7 @@ curl -LsSf https://astral.sh/uv/install.sh | sh
 
 # Create development environment (creates traditional venv)
 # The build script handles Lightning commit pinning and optional PyTorch nightly automatically
-./scripts/build_fts_env.sh --repo_home=${PWD} --target_env_name=fts_latest
+./scripts/build_fts_env.sh --repo-home=${PWD} --target-env-name=fts_latest
 
 # Activate the environment
 cd ${FTS_REPO_DIR} && \
@@ -86,44 +86,53 @@ export UV_OVERRIDE=${PWD}/requirements/ci/overrides.txt
 uv pip install -e ".[all]"
 ```
 
-**Manual installation with PyTorch nightly:**
+**Manual installation with a PyTorch prerelease (nightly/test):**
 
 ```bash
 cd ${FTS_REPO_DIR}
 
-# Install PyTorch nightly first (adjust version and CUDA target as needed, see any specified metadata in requirements/ci/torch-nightly.txt or use your preferred one)
-uv pip install torch==2.10.0.dev20251124 --index-url https://download.pytorch.org/whl/nightly/cu128
+# Install a PyTorch prerelease first (adjust version and CUDA target as needed; see configuration in requirements/ci/torch-pre.txt)
+# Example (nightly):
+uv pip install --prerelease=allow torch==2.10.0.dev20251124 --index-url https://download.pytorch.org/whl/nightly/cu128
 
 # Then install FTS with Lightning commit pin
 export UV_OVERRIDE=${PWD}/requirements/ci/overrides.txt
 uv pip install -e ".[all]"
 ```
 
+# To configure PyTorch prerelease used by the build scripts and azure pipelines, edit `requirements/ci/torch-pre.txt`:
+
+# Line 1: torch version (e.g., 2.10.0 for test/RC or 2.10.0.dev20251203 for nightly)
+
+# Line 2: CUDA target for local builds (e.g., cu128) — CI uses cpu
+
+# Line 3: channel type: "test" or "nightly"
+
 ### Development Environment Scripts
 
 Use the provided build script for automated setup:
 
 ```bash
 # Standard development build (uses FTS_VENV_BASE or default ~/.venvs)
-./scripts/build_fts_env.sh --repo_home=${PWD} --target_env_name=fts_latest
+./scripts/build_fts_env.sh --repo-home=${PWD} --target-env-name=fts_latest
 
 # Build with explicit venv directory (recommended for hardlink performance)
-./scripts/build_fts_env.sh --repo_home=${HOME}/repos/finetuning-scheduler --target_env_name=fts_latest --venv-dir=/mnt/cache/${USER}/.venvs
+./scripts/build_fts_env.sh --repo-home=${HOME}/repos/finetuning-scheduler --target-env-name=fts_latest --venv-dir=/mnt/cache/${USER}/.venvs
 
 # Build without Lightning commit pinning (use PyPI release)
-./scripts/build_fts_env.sh --repo_home=${PWD} --target_env_name=fts_latest --no_commit_pin
+./scripts/build_fts_env.sh --repo-home=${PWD} --target-env-name=fts_latest --no-commit-pin
 
 # Build with specific PyTorch nightly version
-./scripts/build_fts_env.sh --repo_home=${PWD} --target_env_name=fts_latest --torch_dev_ver=dev20240201
+./scripts/build_fts_env.sh --repo-home=${PWD} --target-env-name=fts_latest --torch_dev_ver=dev20240201
 
 # Build with PyTorch test channel
-./scripts/build_fts_env.sh --repo_home=${PWD} --target_env_name=fts_latest --torch_test_channel
+./scripts/build_fts_env.sh --repo-home=${PWD} --target-env-name=fts_latest --torch_test_channel
 
 # Build from Lightning source
-./scripts/build_fts_env.sh --repo_home=${HOME}/repos/finetuning-scheduler --target_env_name=fts_latest --from-source="lightning:${HOME}/repos/lightning"
+./scripts/build_fts_env.sh --repo-home=${HOME}/repos/finetuning-scheduler --target-env-name=fts_latest --from-source="lightning:${HOME}/repos/lightning"
 
 # Build with oldest compatible dependencies (Python 3.10, mirrors CI oldest matrix)
-./scripts/build_fts_env.sh --repo_home=${HOME}/repos/finetuning-scheduler --target_env_name=fts_oldest --oldest
+./scripts/build_fts_env.sh --repo-home=${HOME}/repos/finetuning-scheduler --target-env-name=fts_oldest --oldest
 ```
 
 **Venv Location Options:**

CHANGELOG.md

@@ -4,7 +4,7 @@ All notable changes to this project will be documented in this file.
 
 The format is based on [Keep a Changelog](http://keepachangelog.com/en/1.0.0/).
 
-## [2.10.0] - 2025-XX-XX
+## [2.10.0] - 2025-01-25
 
 ### Added
 

README.md

@@ -80,8 +80,15 @@ The `build_fts_env.sh` script automatically handles Lightning commit pinning and
 git clone https://github.com/speediedan/finetuning-scheduler.git
 cd finetuning-scheduler
 
-# Standard development build (handles Lightning pin automatically and builds with PyTorch nightly (if configured in requirements/ci/torch-nightly.txt)
-./scripts/build_fts_env.sh --repo_home=${PWD} --target_env_name=fts_latest --venv-dir=/path/to/.venvs
+# Standard development build (handles Lightning pin automatically and installs an optional PyTorch prerelease if configured in `requirements/ci/torch-pre.txt`)
+./scripts/build_fts_env.sh --repo-home=${PWD} --target-env-name=fts_latest --venv-dir=/path/to/.venvs
+
+# To configure PyTorch prerelease used by the build scripts, edit `requirements/ci/torch-pre.txt`:
+#   Line 1: torch version (e.g., 2.10.0 for test/RC or 2.10.0.dev20251203 for nightly)
+#   Line 2: CUDA target (e.g., cu128) — CI uses cpu
+#   Line 3: channel type: "test" or "nightly"
+
+# Note: `manage_standalone_processes.sh` is an optional wrapper to run long-running coverage/build scripts with checks for other concurrent conflicting processes, and run options (--use-nohup etc) — you can also run `build_fts_env.sh` and `gen_fts_coverage.sh` directly.
 
 # Activate (use your venv base path)
 export FTS_VENV_BASE=~/.venvs  # or /mnt/cache/${USER}/.venvs
@@ -100,25 +107,24 @@ export UV_OVERRIDE=${PWD}/requirements/ci/overrides.txt
 uv pip install -e ".[all]"
 ```
 
-#### Manual installation with PyTorch nightly:
+## Manual installation with a PyTorch prerelease (nightly/test)
 
-When `torch-nightly.txt` is configured, use a two-step installation approach:
+When using a PyTorch prerelease (nightly or test), use a two-step installation approach:
 
 ```bash
 git clone https://github.com/speediedan/finetuning-scheduler.git
 cd finetuning-scheduler
 
-# Step 1: Install PyTorch nightly (adjust version and CUDA target as needed)
-uv pip install --prerelease=if-necessary-or-explicit torch==2.10.0.dev20251124 \
-    --index-url https://download.pytorch.org/whl/nightly/cu128
+# Step 1: Install a PyTorch prerelease (adjust version and CUDA target as needed; see configuration in requirements/ci/torch-pre.txt)
+# Example (nightly):
+uv pip install --prerelease=if-necessary-or-explicit torch==2.10.0.dev20251124 --index-url https://download.pytorch.org/whl/nightly/cu128
 
 # Step 2: Install FTS with Lightning commit pin (torch already installed, will be skipped)
 export UV_OVERRIDE=${PWD}/requirements/ci/overrides.txt
 uv pip install -e ".[all]"
 ```
 
-The nightly version is specified in `requirements/ci/torch-nightly.txt` and documented in
-`requirements/ci/torch-override.txt` for reference.
+The prerelease version is configured via `requirements/ci/torch-pre.txt`. The `lock_ci_requirements.sh` and `build_fts_env.sh` scripts will read this file to determine whether to pre-install a prerelease PyTorch during builds.
 
 #### Install a specific FTS version from source using the standalone `pytorch-lighting` package:
 

docs/source/install/dynamic_versioning.rst

@@ -67,8 +67,13 @@ environment variable. This is handled automatically by the build scripts and CI
 .. code-block:: bash
 
     # The build_fts_env.sh script automatically sets up Lightning commit pinning
-    # and optionally installs PyTorch nightly (if configured in requirements/ci/torch-nightly.txt)
-    ./scripts/build_fts_env.sh --repo_home=${PWD} --target_env_name=fts_latest
+    # and optionally installs a PyTorch prerelease (if configured in `requirements/ci/torch-pre.txt`)
+    ./scripts/build_fts_env.sh --repo-home=${PWD} --target-env-name=fts_latest
+
+# To configure PyTorch prerelease used by the build scripts, edit `requirements/ci/torch-pre.txt`:
+#   Line 1: torch version (e.g., 2.10.0 for test/RC or 2.10.0.dev20251203 for nightly)
+#   Line 2: CUDA target (e.g., cu128) — CI uses cpu
+#   Line 3: channel type: "test" or "nightly"
 
 **Manual installation with Lightning commit pin:**
 
@@ -81,23 +86,23 @@ environment variable. This is handled automatically by the build scripts and CI
     export UV_OVERRIDE=${PWD}/requirements/ci/overrides.txt
     uv pip install -e ".[all]"
 
-**Manual installation with PyTorch nightly:**
+**Manual installation with a PyTorch prerelease (nightly/test):**
 
-When ``torch-nightly.txt`` is configured, use a two-step installation approach:
+When using a PyTorch prerelease (nightly or test), use a two-step installation approach:
 
 .. code-block:: bash
 
     git clone https://github.com/speediedan/finetuning-scheduler.git
     cd finetuning-scheduler
 
-    # Step 1: Install PyTorch nightly (adjust version and CUDA target as needed)
-    uv pip install --prerelease=if-necessary-or-explicit torch==2.10.0.dev20251124 \
-        --index-url https://download.pytorch.org/whl/nightly/cu128
+    # Step 1: Install a PyTorch prerelease (adjust version and CUDA target as needed; see configuration in requirements/ci/torch-pre.txt)
+    # Example (nightly):
+    uv pip install --prerelease=allow torch==2.10.0.dev20251124 --index-url https://download.pytorch.org/whl/nightly/cu128
 
     # Step 2: Install FTS with Lightning commit pin (torch already installed, will be skipped)
     export UV_OVERRIDE=${PWD}/requirements/ci/overrides.txt
     uv pip install -e ".[all]"
 
-The nightly version is specified in ``requirements/ci/torch-nightly.txt`` and documented in
-``requirements/ci/torch-override.txt`` for reference. The specific Lightning commit is defined in
-``requirements/ci/overrides.txt``.
+The prerelease version is configured via ``requirements/ci/torch-pre.txt``. The `lock_ci_requirements.sh` and
+`build_fts_env.sh` scripts will read that file to determine whether to pre-install a PyTorch prerelease during builds.
+The specific Lightning commit is defined in ``requirements/ci/overrides.txt``.

scripts/README_warnings_cleanup.md

@@ -98,8 +98,8 @@ The warnings cleanup automation replaces the manual process previously documente
 
 ```bash
 # Builds/rebuilds test environments
-build_fts_env.sh --repo_home=... --target_env_name=fts_latest
-build_fts_env.sh --repo_home=... --target_env_name=fts_oldest --oldest
+build_fts_env.sh --repo-home=... --target-env-name=fts_latest
+build_fts_env.sh --repo-home=... --target-env-name=fts_oldest --oldest
 ```
 
 ### 2. Test Execution
@@ -347,8 +347,8 @@ When modifying the automation scripts:
 
 ```bash
 # Rebuild environments manually
-./scripts/build_fts_env.sh --repo_home=${PWD} --target_env_name=fts_latest
-./scripts/build_fts_env.sh --repo_home=${PWD} --target_env_name=fts_oldest --oldest
+./scripts/build_fts_env.sh --repo-home=${PWD} --target-env-name=fts_latest
+./scripts/build_fts_env.sh --repo-home=${PWD} --target-env-name=fts_oldest --oldest
 ```
 
 ### "Warnings still unmatched after update"

scripts/automate_warnings_cleanup.py

@@ -243,8 +243,8 @@ def _setup_environments(self) -> bool:
             logger.info(f"Building environment: {env_name}")
             cmd = [
                 str(build_script),
-                f"--repo_home={self.config.repo_home}",
-                f"--target_env_name={env_name}",
+                f"--repo-home={self.config.repo_home}",
+                f"--target-env-name={env_name}",
                 f"--venv-dir={self.config.venv_base}",
                 *extra_args,
             ]

scripts/build_fts_env.sh

@@ -3,15 +3,15 @@
 # Utility script to build FTS environments using uv
 # Usage examples:
 # build latest (uses FTS_VENV_BASE or default ~/.venvs):
-#   ./build_fts_env.sh --repo_home=~/repos/finetuning-scheduler --target_env_name=fts_latest
+#   ./build_fts_env.sh --repo-home=~/repos/finetuning-scheduler --target-env-name=fts_latest
 # build latest with explicit venv directory (recommended for hardlink performance):
-#   ./build_fts_env.sh --repo_home=${HOME}/repos/finetuning-scheduler --target_env_name=fts_latest --venv-dir=/mnt/cache/${USER}/.venvs
+#   ./build_fts_env.sh --repo-home=${HOME}/repos/finetuning-scheduler --target-env-name=fts_latest --venv-dir=/mnt/cache/${USER}/.venvs
 # build oldest (CI oldest build simulation with Python 3.10 and oldest deps):
-#   ./build_fts_env.sh --repo_home=${HOME}/repos/finetuning-scheduler --target_env_name=fts_oldest --oldest
+#   ./build_fts_env.sh --repo-home=${HOME}/repos/finetuning-scheduler --target-env-name=fts_oldest --oldest
 # build release:
-#   ./build_fts_env.sh --repo_home=${HOME}/repos/fts-release --target_env_name=fts_release
+#   ./build_fts_env.sh --repo-home=${HOME}/repos/fts-release --target-env-name=fts_release
 # build latest from a package from source:
-#   ./build_fts_env.sh --repo_home=${HOME}/repos/finetuning-scheduler --target_env_name=fts_latest --from-source="lightning:${HOME}/repos/lightning:pytorch"
+#   ./build_fts_env.sh --repo-home=${HOME}/repos/finetuning-scheduler --target-env-name=fts_latest --from-source="lightning:${HOME}/repos/lightning:pytorch"
 #
 # To configure PyTorch version (nightly/test/stable), edit requirements/ci/torch-pre.txt
 set -eo pipefail
@@ -32,30 +32,30 @@ source "${SCRIPT_DIR}/infra_utils.sh"
 usage(){
 >&2 cat << EOF
 Usage: $0
-   [ --repo_home input]
-   [ --target_env_name input ]
+   [ --repo-home input]
+   [ --target-env-name input ]
    [ --oldest ]                # Use oldest CI requirements (Python 3.10, requirements-oldest.txt)
-   [ --uv_install_flags "flags" ]
-   [ --no_commit_pin ]
+   [ --uv-install-flags "flags" ]
+   [ --no-commit-pin ]
    [ --venv-dir input ]
    [ --torch-backend input ]  (cpu, cu128, auto; default: cu128 for CUDA 12.8)
    [ --from-source "package:path[:extras][:ENV_VAR=value]" ]
    [ --help ]
    Examples:
     # build latest (uses FTS_VENV_BASE or default ~/.venvs):
-    #   ./build_fts_env.sh --repo_home=\${HOME}/repos/finetuning-scheduler --target_env_name=fts_latest
+    #   ./build_fts_env.sh --repo-home=\${HOME}/repos/finetuning-scheduler --target-env-name=fts_latest
     # build latest with explicit venv directory (recommended for hardlink performance):
-    #   ./build_fts_env.sh --repo_home=\${HOME}/repos/finetuning-scheduler --target_env_name=fts_latest --venv-dir=/mnt/cache/\${USER}/.venvs
+    #   ./build_fts_env.sh --repo-home=\${HOME}/repos/finetuning-scheduler --target-env-name=fts_latest --venv-dir=/mnt/cache/\${USER}/.venvs
     # build oldest (CI oldest build simulation):
-    #   ./build_fts_env.sh --repo_home=\${HOME}/repos/finetuning-scheduler --target_env_name=fts_oldest --oldest --venv-dir=/mnt/cache/\${USER}/.venvs
+    #   ./build_fts_env.sh --repo-home=\${HOME}/repos/finetuning-scheduler --target-env-name=fts_oldest --oldest --venv-dir=/mnt/cache/\${USER}/.venvs
     # build release:
-    #   ./build_fts_env.sh --repo_home=\${HOME}/repos/fts-release --target_env_name=fts_release
+    #   ./build_fts_env.sh --repo-home=\${HOME}/repos/fts-release --target-env-name=fts_release
     # build latest with no cache:
-    #   ./build_fts_env.sh --repo_home=\${HOME}/repos/finetuning-scheduler --target_env_name=fts_latest --uv_install_flags="--no-cache"
+    #   ./build_fts_env.sh --repo-home=\${HOME}/repos/finetuning-scheduler --target-env-name=fts_latest --uv-install-flags="--no-cache"
     # build latest without using CI commit pinning:
-    #   ./build_fts_env.sh --repo_home=\${HOME}/repos/finetuning-scheduler --target_env_name=fts_latest --no_commit_pin
+    #   ./build_fts_env.sh --repo-home=\${HOME}/repos/finetuning-scheduler --target-env-name=fts_latest --no-commit-pin
     # build latest from Lightning source:
-    #   ./build_fts_env.sh --repo_home=\${HOME}/repos/finetuning-scheduler --target_env_name=fts_latest --from-source="lightning:\${HOME}/repos/lightning:pytorch"
+    #   ./build_fts_env.sh --repo-home=\${HOME}/repos/finetuning-scheduler --target-env-name=fts_latest --from-source="lightning:\${HOME}/repos/lightning:pytorch"
 
     # To configure PyTorch version, edit requirements/ci/torch-pre.txt:
     #   Line 1: torch version (e.g., 2.10.0 for test, 2.10.0.dev20251124 for nightly)
@@ -65,7 +65,7 @@ EOF
 exit 1
 }
 
-args=$(getopt -o '' --long repo_home:,target_env_name:,oldest,uv_install_flags:,no_commit_pin,venv-dir:,torch-backend:,from-source:,help -- "$@")
+args=$(getopt -o '' --long repo-home:,repo_home:,target-env-name:,target_env_name:,oldest,uv-install-flags:,uv_install_flags:,no-commit-pin,no_commit_pin,venv-dir:,torch-backend:,from-source:,help -- "$@")
 if [[ $? -gt 0 ]]; then
   usage
 fi
@@ -74,11 +74,11 @@ eval set -- ${args}
 while :
 do
   case $1 in
-    --repo_home)  repo_home=$2    ; shift 2  ;;
-    --target_env_name)  target_env_name=$2  ; shift 2 ;;
+    --repo-home|--repo_home)  repo_home=$2    ; shift 2  ;;
+    --target-env-name|--target_env_name)  target_env_name=$2  ; shift 2 ;;
     --oldest)   oldest=1 ; shift  ;;
-    --uv_install_flags)   uv_install_flags=$2 ; shift 2 ;;
-    --no_commit_pin)   no_commit_pin=1 ; shift  ;;
+    --uv-install-flags|--uv_install_flags)   uv_install_flags=$2 ; shift 2 ;;
+    --no-commit-pin|--no_commit_pin)   no_commit_pin=1 ; shift  ;;
     --venv-dir)   venv_dir=$2 ; shift 2 ;;
     --torch-backend)   torch_backend=$2   ; shift 2 ;;
     --from-source)
@@ -167,7 +167,7 @@ fts_install(){
     unset PACKAGE_NAME
     cd ${repo_home}
 
-    # Set UV_OVERRIDE for Lightning commit pin, unless --no_commit_pin is specified
+    # Set UV_OVERRIDE for Lightning commit pin, unless --no-commit-pin is specified
     local override_file="${repo_home}/requirements/ci/overrides.txt"
     if [[ -z ${no_commit_pin} ]]; then
         export UV_OVERRIDE="${override_file}"

scripts/gen_fts_coverage.sh

@@ -126,7 +126,7 @@ all_supported_pattern="@($(join_by_pipe "${supported_fts_latest[@]}" "${supporte
 
 env_rebuild(){
     # Build command arguments array
-    local -a cmd_args=("${repo_home}/scripts/build_fts_env.sh" "--repo_home=${repo_home}" "--target_env_name=$1")
+    local -a cmd_args=("${repo_home}/scripts/build_fts_env.sh" "--repo-home=${repo_home}" "--target-env-name=$1")
 
     # Add oldest flag if specified
     if [[ $oldest -eq 1 ]]; then
@@ -135,12 +135,12 @@ env_rebuild(){
 
     # Add uv_install_flags if specified
     if [[ -n "${uv_install_flags}" ]]; then
-        cmd_args+=("--uv_install_flags=${uv_install_flags}")
+        cmd_args+=("--uv-install-flags=${uv_install_flags}")
     fi
 
-    # Add no_commit_pin flag if specified
+    # Add no-commit-pin flag if specified
     if [[ $no_commit_pin -eq 1 ]]; then
-        cmd_args+=("--no_commit_pin")
+        cmd_args+=("--no-commit-pin")
     fi
 
     # Add venv-dir flag if specified