roar-cli 0.3.4__tar.gz → 0.3.6__tar.gz

{roar_cli-0.3.4 → roar_cli-0.3.6}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: roar-cli
-Version: 0.3.4
+Version: 0.3.6
 Classifier: Development Status :: 3 - Alpha
 Classifier: Intended Audience :: Developers
 Classifier: Intended Audience :: Science/Research
@@ -51,6 +51,14 @@ Project-URL: Repository, https://github.com/treqs/roar
 
 **Run Observation & Artifact Registration**
 
+## Quickstart
+
+```bash
+uv tool install roar-cli      # installs the `roar` command (Python 3.10+)
+roar init                     # set up roar in your project
+roar run <command>            # track a run — then `roar dag` to see it
+```
+
 `roar` tracks data artifacts and execution steps in ML pipelines, enabling reproducibility and lineage queries. `roar` tracking happens automagically by observing your commands as they run, capturing essential context without requiring you to define a pipeline explicitly.
 
 By identifying files based on their actual content rather than their names, it ensures you can always trace a result back to the exact inputs and code that produced it. This gives you reliable reproducibility and a clear history of your artifacts, all derived naturally from your workflow.
@@ -60,12 +68,16 @@ While `roar` captures your work locally, connecting it to a GLaaS (Global Lineag
 ## Installation
 
 ```bash
-pip install roar-cli
-# or with uv
+# Recommended: install the `roar` command in an isolated tool environment
+uv tool install roar-cli
+# or: pipx install roar-cli
+
+# Into an existing environment (e.g. to use roar alongside Ray in the same venv)
 uv pip install roar-cli
+# or: pip install roar-cli
 ```
 
-Requires Python 3.10+.
+Requires Python 3.10+. (A single stable-ABI wheel covers every Python 3.10+.)
 
 > For the full prereqs, platform support matrix, tracer-backend setup,
 > macOS SIP notes, and sdist build steps, see the canonical
@@ -83,44 +95,17 @@ Requires Python 3.10+.
 
 PyPI wheels are published for Linux (`x86_64`, `aarch64`) and macOS (`x86_64`, `arm64`).
 
-If a matching wheel isn't available, `pip install` falls through to the
-source distribution. The sdist ships the Rust tracer source but no
-pre-built binaries, so it requires a C toolchain (`gcc` / `clang`), Rust
-(`rustup`), and a few minutes to compile the tracers on first install.
+On platforms without a published wheel (e.g. musl/Alpine, Windows, or glibc
+older than the manylinux baseline), `pip install` falls through to the
+source distribution, which ships the Rust tracer source but no pre-built
+binaries — so it needs a C toolchain (`gcc` / `clang`), Rust (`rustup`),
+and a few minutes to compile the tracers on first install.
 
 ### Development Installation
 
-```bash
-# Clone the repository
-git clone https://github.com/treqs/roar.git
-cd roar
-
-# One-shot dev install: Python package + Rust tracer binaries
-bash scripts/install-dev.sh
-```
-
-`scripts/install-dev.sh` runs `pip install -e ".[dev]"` (preferring `uv`
-when available) and then builds the Rust tracer binaries
-(`roar-tracer`, `roar-tracer-preload`, `roar-tracer-ebpf`, `roard`,
-`roar-proxy`) and stages them into `roar/bin/`. A bare
-`pip install -e .` does _not_ build the tracer binaries because they
-live in separate cargo crates outside the maturin manifest, so
-`roar run` would fail with "No tracer binary found" until the script
-runs. See [Building from source](#building-from-source) below for
-details and the manual flow.
-
-## Quick Start
-
-```bash
-# Initialize roar in your project
-cd my-ml-project
-roar init
-
-# Run commands with provenance tracking
-roar run python preprocess.py --input data.csv --output features.parquet
-roar run python train.py --data features.parquet --output model.pt
-roar run python evaluate.py --model model.pt --output metrics.json
-```
+Installing from source (editable Python package + Rust tracer binaries) is
+covered under [Development → Building from source](#building-from-source).
+The fast path is `bash scripts/install-dev.sh`.
 
 ## Product Telemetry
 
@@ -162,8 +147,8 @@ roar config set telemetry.enabled false
 Environment opt-outs always win over saved config:
 
 ```bash
-DO_NOT_TRACK=1 roar run python train.py
-ROAR_NO_TELEMETRY=1 roar run python train.py
+DO_NOT_TRACK=1 roar run python3 train.py
+ROAR_NO_TELEMETRY=1 roar run python3 train.py
 ```
 
 Telemetry is also suppressed automatically in CI, pytest, and Roar-managed
@@ -258,7 +243,7 @@ Run a command with provenance tracking. Roar captures:
 - Command arguments
 
 ```bash
-roar run python train.py --epochs 10 --lr 0.001
+roar run python3 train.py --epochs 10 --lr 0.001
 roar run ./scripts/preprocess.sh
 roar run torchrun --nproc_per_node=4 train.py
 
@@ -611,9 +596,9 @@ Named groups of artifacts, used for downloaded datasets or upload bundles.
 
 ```bash
 # Record your pipeline
-roar run python preprocess.py
-roar run python train.py --epochs 10
-roar run python evaluate.py
+roar run python3 preprocess.py
+roar run python3 train.py --epochs 10
+roar run python3 evaluate.py
 
 # Later, reproduce an artifact
 roar reproduce <model-hash> --run
@@ -639,40 +624,21 @@ Add `.roar/` to your `.gitignore` (roar offers to do this during `roar init`).
 
 ## GLaaS Server
 
-Roar can register sessions, jobs, steps, and artifacts with a GLaaS (Global Lineage-as-a-Service) server using the `roar register` command.
-
-### Server Setup
-
-```bash
-# Install with server dependencies
-uv pip install -e ".[server]"
-# or without uv
-pip install -e ".[server]"
-
-# Run the server
-glaas-server
-
-# Or with custom host/port
-GLAAS_HOST=0.0.0.0 GLAAS_PORT=8080 glaas-server
-```
-
-The server provides:
-
-- REST API for artifact and job registration
-- Web UI at `/` with artifact and job browsers
-- Search and filtering by command, GPU, file type, etc.
-
-### Client Configuration
+GLaaS (Global Lineage-as-a-Service) is the shared registry roar publishes to
+with `roar register` and `roar put`. It's hosted at
+[glaas.ai](https://glaas.ai) (default API endpoint `https://api.glaas.ai`),
+so there's nothing to run yourself — sign in and publish.
 
 ```bash
-# Set the GLaaS server URL
-roar config set glaas.url http://localhost:8000
+# Sign in (browser/device flow) for attributed, private, or project publishing
+roar login
 
-# Show your SSH key (copy to GLaaS web UI)
-roar auth register
+# Or register an SSH key for programmatic auth
+roar auth register      # show your public key to paste at glaas.ai
+roar auth test          # verify the connection
 
-# Test authentication
-roar auth test
+# Point roar at a different GLaaS deployment if needed
+roar config set glaas.url https://api.glaas.ai
 ```
 
 > [!TIP]
@@ -751,13 +717,13 @@ Verify the install with `roar tracer`; every backend listed should be
 ruff check .
 
 # Format check
-ruff format --check
+ruff format --check .
 
 # Type checking
 mypy roar
 
 # Run all checks at once
-ruff check . && ruff format --check && mypy roar
+ruff check . && ruff format --check . && mypy roar
 ```
 
 ### Running Tests

{roar_cli-0.3.4 → roar_cli-0.3.6}/README.md

@@ -2,6 +2,14 @@
 
 **Run Observation & Artifact Registration**
 
+## Quickstart
+
+```bash
+uv tool install roar-cli      # installs the `roar` command (Python 3.10+)
+roar init                     # set up roar in your project
+roar run <command>            # track a run — then `roar dag` to see it
+```
+
 `roar` tracks data artifacts and execution steps in ML pipelines, enabling reproducibility and lineage queries. `roar` tracking happens automagically by observing your commands as they run, capturing essential context without requiring you to define a pipeline explicitly.
 
 By identifying files based on their actual content rather than their names, it ensures you can always trace a result back to the exact inputs and code that produced it. This gives you reliable reproducibility and a clear history of your artifacts, all derived naturally from your workflow.
@@ -11,12 +19,16 @@ While `roar` captures your work locally, connecting it to a GLaaS (Global Lineag
 ## Installation
 
 ```bash
-pip install roar-cli
-# or with uv
+# Recommended: install the `roar` command in an isolated tool environment
+uv tool install roar-cli
+# or: pipx install roar-cli
+
+# Into an existing environment (e.g. to use roar alongside Ray in the same venv)
 uv pip install roar-cli
+# or: pip install roar-cli
 ```
 
-Requires Python 3.10+.
+Requires Python 3.10+. (A single stable-ABI wheel covers every Python 3.10+.)
 
 > For the full prereqs, platform support matrix, tracer-backend setup,
 > macOS SIP notes, and sdist build steps, see the canonical
@@ -34,44 +46,17 @@ Requires Python 3.10+.
 
 PyPI wheels are published for Linux (`x86_64`, `aarch64`) and macOS (`x86_64`, `arm64`).
 
-If a matching wheel isn't available, `pip install` falls through to the
-source distribution. The sdist ships the Rust tracer source but no
-pre-built binaries, so it requires a C toolchain (`gcc` / `clang`), Rust
-(`rustup`), and a few minutes to compile the tracers on first install.
+On platforms without a published wheel (e.g. musl/Alpine, Windows, or glibc
+older than the manylinux baseline), `pip install` falls through to the
+source distribution, which ships the Rust tracer source but no pre-built
+binaries — so it needs a C toolchain (`gcc` / `clang`), Rust (`rustup`),
+and a few minutes to compile the tracers on first install.
 
 ### Development Installation
 
-```bash
-# Clone the repository
-git clone https://github.com/treqs/roar.git
-cd roar
-
-# One-shot dev install: Python package + Rust tracer binaries
-bash scripts/install-dev.sh
-```
-
-`scripts/install-dev.sh` runs `pip install -e ".[dev]"` (preferring `uv`
-when available) and then builds the Rust tracer binaries
-(`roar-tracer`, `roar-tracer-preload`, `roar-tracer-ebpf`, `roard`,
-`roar-proxy`) and stages them into `roar/bin/`. A bare
-`pip install -e .` does _not_ build the tracer binaries because they
-live in separate cargo crates outside the maturin manifest, so
-`roar run` would fail with "No tracer binary found" until the script
-runs. See [Building from source](#building-from-source) below for
-details and the manual flow.
-
-## Quick Start
-
-```bash
-# Initialize roar in your project
-cd my-ml-project
-roar init
-
-# Run commands with provenance tracking
-roar run python preprocess.py --input data.csv --output features.parquet
-roar run python train.py --data features.parquet --output model.pt
-roar run python evaluate.py --model model.pt --output metrics.json
-```
+Installing from source (editable Python package + Rust tracer binaries) is
+covered under [Development → Building from source](#building-from-source).
+The fast path is `bash scripts/install-dev.sh`.
 
 ## Product Telemetry
 
@@ -113,8 +98,8 @@ roar config set telemetry.enabled false
 Environment opt-outs always win over saved config:
 
 ```bash
-DO_NOT_TRACK=1 roar run python train.py
-ROAR_NO_TELEMETRY=1 roar run python train.py
+DO_NOT_TRACK=1 roar run python3 train.py
+ROAR_NO_TELEMETRY=1 roar run python3 train.py
 ```
 
 Telemetry is also suppressed automatically in CI, pytest, and Roar-managed
@@ -209,7 +194,7 @@ Run a command with provenance tracking. Roar captures:
 - Command arguments
 
 ```bash
-roar run python train.py --epochs 10 --lr 0.001
+roar run python3 train.py --epochs 10 --lr 0.001
 roar run ./scripts/preprocess.sh
 roar run torchrun --nproc_per_node=4 train.py
 
@@ -562,9 +547,9 @@ Named groups of artifacts, used for downloaded datasets or upload bundles.
 
 ```bash
 # Record your pipeline
-roar run python preprocess.py
-roar run python train.py --epochs 10
-roar run python evaluate.py
+roar run python3 preprocess.py
+roar run python3 train.py --epochs 10
+roar run python3 evaluate.py
 
 # Later, reproduce an artifact
 roar reproduce <model-hash> --run
@@ -590,40 +575,21 @@ Add `.roar/` to your `.gitignore` (roar offers to do this during `roar init`).
 
 ## GLaaS Server
 
-Roar can register sessions, jobs, steps, and artifacts with a GLaaS (Global Lineage-as-a-Service) server using the `roar register` command.
-
-### Server Setup
-
-```bash
-# Install with server dependencies
-uv pip install -e ".[server]"
-# or without uv
-pip install -e ".[server]"
-
-# Run the server
-glaas-server
-
-# Or with custom host/port
-GLAAS_HOST=0.0.0.0 GLAAS_PORT=8080 glaas-server
-```
-
-The server provides:
-
-- REST API for artifact and job registration
-- Web UI at `/` with artifact and job browsers
-- Search and filtering by command, GPU, file type, etc.
-
-### Client Configuration
+GLaaS (Global Lineage-as-a-Service) is the shared registry roar publishes to
+with `roar register` and `roar put`. It's hosted at
+[glaas.ai](https://glaas.ai) (default API endpoint `https://api.glaas.ai`),
+so there's nothing to run yourself — sign in and publish.
 
 ```bash
-# Set the GLaaS server URL
-roar config set glaas.url http://localhost:8000
+# Sign in (browser/device flow) for attributed, private, or project publishing
+roar login
 
-# Show your SSH key (copy to GLaaS web UI)
-roar auth register
+# Or register an SSH key for programmatic auth
+roar auth register      # show your public key to paste at glaas.ai
+roar auth test          # verify the connection
 
-# Test authentication
-roar auth test
+# Point roar at a different GLaaS deployment if needed
+roar config set glaas.url https://api.glaas.ai
 ```
 
 > [!TIP]
@@ -702,13 +668,13 @@ Verify the install with `roar tracer`; every backend listed should be
 ruff check .
 
 # Format check
-ruff format --check
+ruff format --check .
 
 # Type checking
 mypy roar
 
 # Run all checks at once
-ruff check . && ruff format --check && mypy roar
+ruff check . && ruff format --check . && mypy roar
 ```
 
 ### Running Tests

{roar_cli-0.3.4 → roar_cli-0.3.6}/pyproject.toml

@@ -5,7 +5,7 @@ build-backend = "maturin"
 
 [project]
 name = "roar-cli"
-version = "0.3.4"
+version = "0.3.6"
 description = "Reproducibility and provenance tracker for ML training pipelines"
 authors = [
     { name="TReqs Team", email="info@treqs.ai" }

{roar_cli-0.3.4 → roar_cli-0.3.6}/roar/application/get/transfer.py

@@ -11,6 +11,8 @@ or roar register.
 
 from __future__ import annotations
 
+import threading
+from concurrent.futures import ThreadPoolExecutor, as_completed
 from dataclasses import dataclass, field
 from pathlib import Path
 
@@ -20,6 +22,8 @@ from ...integrations.download.base import DownloadBackend, Source
 from ...presenters.spinner import Spinner
 from .results import GetDownloadedFile, GetDryRunItem
 
+_DEFAULT_DOWNLOAD_WORKERS = 8
+
 
 def _download_progress_message(done: int, total: int, downloaded_bytes: int) -> str:
     """Status line for the download spinner, e.g. ``Downloading 47/100 · 4.31 GB``."""
@@ -288,11 +292,36 @@ class GetService:
             # Downloads are the long pole of a get (multi-GB datasets); show a live
             # N/M + cumulative-bytes counter so the terminal isn't dead for minutes.
             downloaded_bytes = 0
+            workers = min(_DEFAULT_DOWNLOAD_WORKERS, total)
             with Spinner(_download_progress_message(0, total, 0)) as spin:
-                for index, pending in enumerate(pending_downloads, start=1):
-                    self._download_to_tmp(pending)
-                    downloaded_bytes += pending.tmp_path.stat().st_size
-                    spin.update(_download_progress_message(index, total, downloaded_bytes))
+                if workers <= 1:
+                    for index, pending in enumerate(pending_downloads, start=1):
+                        self._download_to_tmp(pending)
+                        downloaded_bytes += pending.tmp_path.stat().st_size
+                        spin.update(_download_progress_message(index, total, downloaded_bytes))
+                else:
+                    lock = threading.Lock()
+                    done = 0
+                    errors: list[BaseException] = []
+                    with ThreadPoolExecutor(max_workers=workers) as executor:
+                        futures = {
+                            executor.submit(self._download_to_tmp, pending): pending
+                            for pending in pending_downloads
+                        }
+                        for future in as_completed(futures):
+                            exc = future.exception()
+                            if exc is not None:
+                                errors.append(exc)
+                            else:
+                                pending = futures[future]
+                                with lock:
+                                    done += 1
+                                    downloaded_bytes += pending.tmp_path.stat().st_size
+                                    spin.update(
+                                        _download_progress_message(done, total, downloaded_bytes)
+                                    )
+                    if errors:
+                        raise errors[0]
 
             with Spinner(f"Hashing {total} file(s)..."):
                 hashes_by_tmp_path = self._hash_files_batch(

{roar_cli-0.3.4 → roar_cli-0.3.6}/roar/application/git.py

@@ -3,12 +3,13 @@
 from __future__ import annotations
 
 import subprocess
-from dataclasses import dataclass
+from dataclasses import dataclass, replace
 from pathlib import Path
 
 from ..core.interfaces.logger import ILogger
 from ..core.interfaces.registration import GitContext
 from ..integrations.git import GitVCSProvider, resolve_git_context
+from ..utils.git_url import is_shareable_remote
 
 
 @dataclass(frozen=True)
@@ -68,6 +69,17 @@ def resolve_roar_git_context(
     """
     logger.debug("Resolving git context from %s", path)
     ctx = resolve_git_context(path, git_commit, configured_remote=configured_remote)
+    # A repo with no real remote records its own ``file://`` path as the URL.
+    # That resolves only on this machine, so publishing it both leaks the
+    # user's local filesystem layout to GLaaS and is useless to anyone else.
+    # This resolver is publish-only (register/put/package prep), so drop the
+    # non-shareable URL here — the publish record then honestly shows "no
+    # remote", matching the reproducibility checklist. (Local recording uses
+    # ``resolve_git_context`` directly and keeps the ``file://`` URI, which
+    # in-place reproduce relies on.)
+    if ctx.repo and not is_shareable_remote(ctx.repo):
+        logger.debug("Dropping non-shareable git repo URL from publish context: %s", ctx.repo)
+        ctx = replace(ctx, repo=None)
     logger.debug(
         "Git context resolved: repo=%s, commit=%s, branch=%s",
         ctx.repo,

{roar_cli-0.3.4 → roar_cli-0.3.6}/roar/application/publish/git_remote.py

@@ -60,7 +60,8 @@ def _git_check_output(repo_root: Path | str, *args: str, capture_stderr: bool) -
     )
 
 
-def _list_remote_names(repo_root: Path | str) -> list[str]:
+def list_remote_names(repo_root: Path | str) -> list[str]:
+    """Return the names of git remotes configured in this repo (empty if none)."""
     try:
         raw = _git_check_output(repo_root, "remote", capture_stderr=False)
     except subprocess.CalledProcessError:
@@ -68,6 +69,10 @@ def _list_remote_names(repo_root: Path | str) -> list[str]:
     return [line.strip() for line in raw.splitlines() if line.strip()]
 
 
+# Back-compat alias for internal callers.
+_list_remote_names = list_remote_names
+
+
 def resolve_canonical_remote(repo_root: Path | str, configured_remote: str | None) -> str:
     """Return the name of the remote roar should push tags to.
 

{roar_cli-0.3.4 → roar_cli-0.3.6}/roar/application/publish/register_execution.py

@@ -469,8 +469,18 @@ class RegisterService:
 
         composite_registered = sum(1 for item in composite_registrations if item.get("registered"))
         composite_failed = sum(1 for item in composite_registrations if not item.get("registered"))
-        total_artifacts_registered = batch_result.artifacts_registered + composite_registered
         total_artifacts_failed = batch_result.artifacts_failed + composite_failed
+        # Report DISTINCT artifacts, matching `register --dry-run`'s
+        # len(lineage.artifacts). The coordinator's running tally double-counts
+        # (artifacts are tallied in both the staging and the link phase, and the
+        # server's success count is per content-hash) — when everything
+        # registered, the distinct figure is simply the lineage's artifact count.
+        # The success gate below keys off *_failed, not this display number, so
+        # this is safe. On partial failure, fall back to the coordinator's tally.
+        if total_artifacts_failed == 0:
+            total_artifacts_registered = len(lineage.artifacts)
+        else:
+            total_artifacts_registered = batch_result.artifacts_registered + composite_registered
 
         success = (
             batch_result.jobs_failed == 0 and total_artifacts_failed == 0 and not finalize_failed

{roar_cli-0.3.4 → roar_cli-0.3.6}/roar/application/publish/register_tag_push.py

@@ -33,6 +33,7 @@ from ...core.interfaces.logger import ILogger
 from ..git import build_roar_git_tag_name, create_roar_git_tag
 from .git_remote import (
     GitRemoteError,
+    list_remote_names,
     push_roar_tags,
     resolve_canonical_remote,
     warn_if_ssh_passphrase_prompt_likely,
@@ -145,6 +146,21 @@ def ensure_roar_tags_pushed(
             push_skipped_reason="never_config",
         )
 
+    # No remote at all (and none configured): degrade to a local-only register
+    # instead of blocking. The common "does this work" loop shouldn't be gated on
+    # having a remote — and the dry-run never blocks, so the real run shouldn't
+    # contradict it. Tags exist locally; the reproducibility checklist surfaces
+    # that the commit isn't reachable on a remote. (An *invalid* configured
+    # remote or ambiguous multi-remote setup still errors below — those mean the
+    # user wants a push but roar can't safely pick where.)
+    if not configured_remote and not list_remote_names(repo_root):
+        logger.debug("No git remote configured — registering local-only (tags not pushed).")
+        return RegisterTagSummary(
+            session_tag=session_tag_name,
+            job_tags=job_tags,
+            push_skipped_reason="no_remote",
+        )
+
     try:
         remote = resolve_canonical_remote(repo_root, configured_remote)
     except GitRemoteError as exc:

{roar_cli-0.3.4 → roar_cli-0.3.6}/roar/application/publish/registration_package.py

@@ -134,6 +134,9 @@ def build_registration_package(
         git_context=git_context,
         cwd=cwd,
     )
+    redacted_lineage, redacted_git_context = _drop_local_remotes(
+        redacted_lineage, redacted_git_context
+    )
 
     registration_jobs = order_jobs_for_registration(
         normalize_jobs_for_registration(redacted_lineage.jobs)
@@ -263,6 +266,27 @@ def _apply_redaction(
     )
 
 
+def _drop_local_remotes(
+    lineage: LineageData, git_context: GitContext
+) -> tuple[LineageData, GitContext]:
+    """Don't publish non-shareable (``file://`` / local-path) git repos to GLaaS.
+
+    A repo with no real remote records its own ``file://`` path as ``git_repo``;
+    publishing that leaks the local filesystem path and is useless to anyone else.
+    Replace such repos with "" so the GLaaS record honestly shows no remote — the
+    reproducibility checklist already flags this as "commit reachable on a remote".
+    """
+    from ...utils.git_url import is_shareable_remote
+
+    if git_context.repo and not is_shareable_remote(git_context.repo):
+        git_context = GitContext(repo="", commit=git_context.commit, branch=git_context.branch)
+    for job in lineage.jobs:
+        repo = job.get("git_repo")
+        if isinstance(repo, str) and repo and not is_shareable_remote(repo):
+            job["git_repo"] = ""
+    return lineage, git_context
+
+
 def _filter_git_context(
     git_context: GitContext,
     omit_filter: OmitFilter | None,

{roar_cli-0.3.4 → roar_cli-0.3.6}/roar/application/publish/results.py

@@ -49,6 +49,11 @@ class RegisterLineageResponse:
     # the CLI surfaces a notice so the user knows it can't be reproduced from
     # source. Defaults True so existing/normal registrations are unaffected.
     reproducible: bool = True
+    # False when the session's steps span more than one git commit (the user
+    # committed between runs). Computed from the session's commit span — the
+    # SAME source `roar reproduce` uses — so the two checklists never disagree.
+    # Defaults True so single-commit/normal registrations are unaffected.
+    single_commit: bool = True
 
 
 @dataclass(frozen=True)
@@ -94,3 +99,8 @@ class PutResponse:
     git_tag: str | None = None
     warnings: list[str] = field(default_factory=list)
     error: str | None = None
+    # Reproducibility-checklist inputs, mirroring RegisterLineageResponse so
+    # `roar put` can render the same receipt as `roar register`.
+    reproducible: bool = True  # the published run has a git commit
+    single_commit: bool = True  # the session's steps share one commit
+    commit_on_remote: bool = False  # the commit is reachable on a shareable remote