chore(docs): test docs fix

docs/broken_links_false_positives.json

@@ -0,0 +1,5 @@
+{"filename": "deployment/bring-your-own-endpoint/hosted-services.md", "lineno": 158, "uri": "https://platform.openai.com/docs/models", "reason": "OpenAI platform uses bot protection that returns 403 for automated link checkers, but the link is valid"}
+{"filename": "nemo-fw/evaluation-hf.md", "lineno": 26, "uri": "https://github.com/nvidia-nemo/export-deploy?tab=readme-ov-file#install-tensorrt-llm-vllm-or-trt-onnx-backend", "reason": "Valid section anchor in Export-Deploy README that link checker may not find due to GitHub's dynamic anchor generation"}
+{"filename": "nemo-fw/evaluation-doc.md", "lineno": 154, "uri": "https://github.com/nvidia-nemo/evaluator/blob/main/scripts/evaluation_with_nemo_run.py#L235", "reason": "Internal repo link that will be valid once changes are merged to main branch"}
+{"filename": "nemo-fw/evaluation-doc.md", "lineno": 154, "uri": "https://github.com/nvidia-nemo/evaluator/blob/main/scripts/evaluation_with_nemo_run.py#L270", "reason": "Internal repo link that will be valid once changes are merged to main branch"}
+

docs/get-started/quickstart/index.md

@@ -17,7 +17,7 @@ All paths require:
 | List benchmarks | `nemo-evaluator-launcher ls tasks` |
 | Run evaluation | `nemo-evaluator-launcher run --config-dir packages/nemo-evaluator-launcher/examples --config-name <config>` |
 | Check status | `nemo-evaluator-launcher status <invocation_id>` |
-| Debug job | `nemo-evaluator-launcher debug <invocation_id>` |
+| Job info | `nemo-evaluator-launcher info <invocation_id>` |
 | Export results | `nemo-evaluator-launcher export <invocation_id> --dest local --format json` |
 | Dry run | Add `--dry-run` to any run command |
 | Test with limited samples | Add `-o +config.params.limit_samples=3` |

docs/libraries/nemo-evaluator-launcher/cli.md

@@ -21,6 +21,8 @@ nemo-evaluator-launcher --version                 # Show version information
   - Run evaluations with specified configuration
 * - `status`
   - Check status of jobs or invocations
+* - `info`
+  - Show detailed job(s) information
 * - `kill`
   - Kill a job or invocation
 * - `ls`
@@ -29,8 +31,6 @@ nemo-evaluator-launcher --version                 # Show version information
   - Export evaluation results to various destinations
 * - `version`
   - Show version information
-* - `debug`
-  - Show detailed job(s) information
 ```
 
 ## run - Run Evaluations
@@ -156,6 +156,62 @@ abc12345.1   | success  | container124  | <output_dir>/task2/...
 ]
 ```
 
+## info - Job information and navigation
+
+Display detailed job information, including metadata, configuration, and paths to logs/artifacts with descriptions of key result files. Supports copying results locally from both local and remote jobs.
+
+### Basic usage
+```bash
+# Show job info for one or more IDs (job or invocation)
+nemo-evaluator-launcher info <job_or_invocation_id>
+nemo-evaluator-launcher info <inv1> <inv2>
+```
+
+### Show configuration
+```bash
+nemo-evaluator-launcher info <id> --config
+```
+
+### Show paths
+```bash
+# Show artifact locations
+nemo-evaluator-launcher info <id> --artifacts
+# Show log locations
+nemo-evaluator-launcher info <id> --logs
+```
+
+### Copy files locally
+```bash
+# Copy logs (defaults to current dir if no path provided)
+nemo-evaluator-launcher info <id> --copy-logs [DIR]
+
+# Copy artifacts (defaults to current dir if no path provided)
+nemo-evaluator-launcher info <id> --copy-artifacts [DIR]
+```
+
+### Example (Slurm)
+```text
+nemo-evaluator-launcher info <inv_id>
+
+Job <inv_id>.0
+├── Executor: slurm
+├── Created: <timestamp>
+├── Task: <task_name>
+├── Artifacts: user@host:/shared/.../4245adf6071cd199/task_name/artifacts (remote)
+│   └── Key files:
+│       ├── results.yml - Benchmark scores, task results and resolved run configuration.
+│       ├── eval_factory_metrics.json - Response + runtime stats (latency, tokens count, memory)
+│       ├── metrics.json - Harness/benchmark metric and configuration
+│       ├── report.html - Request-Response Pairs samples in HTML format (if enabled)
+│       ├── report.json - Report data in json format, if enabled
+├── Logs: user@host:/shared/.../4245adf6071cd199/task_name/logs (remote)
+│   └── Key files:
+│       ├── client-{SLURM_JOB_ID}.out - Evaluation container/process output
+│       ├── slurm-{SLURM_JOB_ID}.out - SLURM scheduler stdout/stderr (batch submission, export steps).
+│       ├── server-{SLURM_JOB_ID}.out - Model server logs when a deployment is used.
+├── Slurm Job ID: <SLURM_JOB_ID>
+```
+
 ## kill - Kill Jobs
 
 Stop running evaluations.
@@ -303,64 +359,6 @@ nemo-evaluator-launcher version
 nemo-evaluator-launcher --version
 ```
 
-## debug - Job Information and Debugging helper functionalities
-
-Display detailed job information including metadata, configuration, and locations of logs and artifacts. The debug command is useful for troubleshooting job issues, inspecting configurations, and retrieving artifacts from both local and remote jobs.
-
-### Basic Usage
-
-```bash
-# Show job metadata and information for a single or multiple jobs
-nemo-evaluator-launcher debug <invocation_id>
-
-nemo-evaluator-launcher debug  <invocation_id1>  <invocation_id2>
-```
-
-### Show Configuration
-
-```bash
-# Display the job configuration in YAML format
-nemo-evaluator-launcher debug <invocation_id> --config
-```
-
-### Show Paths
-
-```bash
-# Show only artifact locations
-nemo-evaluator-launcher debug <invocation_id> --artifacts
-
-# Show only log locations
-nemo-evaluator-launcher debug <invocation_id> --logs
-```
-
-For remote jobs (Slurm), paths are shown in the format `user@host:/path`.
-
-### Copy Files Locally
-
-```bash
-# Copy logs to local directory (works for both local and remote jobs)
-nemo-evaluator-launcher debug <invocation_id> --copy-logs [destination_dir]
-
-# Copy artifacts to local directory (works for both local and remote jobs)
-nemo-evaluator-launcher debug <invocation_id> --copy-artifacts [destination_dir]
-
-# If no destination is specified, defaults to current directory
-nemo-evaluator-launcher debug <invocation_id> --copy-logs
-```
-
-
-### Debug example for a slurm job
-
-```bash
-# Shows remote paths and Slurm job ID
-nemo-evaluator-launcher debug abc12345
-# Output includes:
-# ├── Artifacts: user@host:/shared/results/artifacts (remote)
-# ├── Logs: user@host:/shared/results/logs (remote)
-# ├── Slurm Job ID: 12345678
-
-```
-
 ## Environment Variables
 
 The CLI respects environment variables for logging and task-specific authentication:
@@ -474,9 +472,9 @@ nemo-evaluator-launcher run --config-dir packages/nemo-evaluator-launcher/exampl
 ```bash
 # Command-specific help
 nemo-evaluator-launcher run --help
-nemo-evaluator-launcher export --help
+nemo-evaluator-launcher info --help
 nemo-evaluator-launcher ls --help
-nemo-evaluator-launcher debug --help
+nemo-evaluator-launcher export --help
 
 # General help
 nemo-evaluator-launcher --help

docs/nemo-fw/evaluation-doc.md

@@ -151,7 +151,7 @@ This section explains how to run evaluations with NeMo Run. For detailed informa
 
 The [evaluation_with_nemo_run.py](https://github.com/NVIDIA-NeMo/Evaluator/blob/main/scripts/evaluation_with_nemo_run.py) script serves as a reference for launching evaluations with NeMo Run. This script demonstrates how to use NeMo Run with both local executors (your local workstation) and Slurm-based executors like clusters. In this setup, the deploy and evaluate processes are launched as two separate jobs with NeMo Run. The evaluate method waits until the PyTriton server is accessible and the model is deployed before starting the evaluations.
 
-> **Note:** Please make sure to update HF_TOKEN in the NeMo Run script's [local_executor env_vars](https://github.com/nvidia-nemo/evaluator/blob/main/scripts/evaluation_with_nemo_run.py#l267) with your HF_TOKEN if using local executor or in the [slurm_executor's env_vars](https://github.com/nvidia-nemo/evaluator/blob/main/scripts/evaluation_with_nemo_run.py#l232) if using slurm_executor.
+> **Note:** Please make sure to update HF_TOKEN in the NeMo Run script's [local_executor env_vars](https://github.com/nvidia-nemo/evaluator/blob/main/scripts/evaluation_with_nemo_run.py#L270) with your HF_TOKEN if using local executor or in the [slurm_executor's env_vars](https://github.com/nvidia-nemo/evaluator/blob/main/scripts/evaluation_with_nemo_run.py#L235) if using slurm_executor.
 
 ### Run Locally with NeMo Run
 

docs/nemo-fw/evaluation-hf.md

@@ -23,14 +23,14 @@ python \
   --use_vllm_backend
 ```
 
-The `--model_path` can refer to either a local checkpoint path or a Hugging Face model ID, as shown in the example above. In the example above, checkpoint deployment uses the `vLLM` backend. To enable accelerated inference, install `vLLM` in your environment. To install `vLLM` inside the NeMo Framework container, follow the steps below as shared in [Export-Deploy's README](https://github.com/nvidia-nemo/export-deploy?tab=readme-ov-file#install-tensorrt-llm-vllm-or-trt-onnx-backend:~:text=cd%20/opt/export%2ddeploy%0auv%20sync%20%2d%2dinexact%20%2d%2dlink%2dmode%20symlink%20%2d%2dlocked%20%2d%2dextra%20vllm%20%24(cat%20/opt/uv_args.txt)):
+The `--model_path` can refer to either a local checkpoint path or a Hugging Face model ID, as shown in the example above. In the example above, checkpoint deployment uses the `vLLM` backend. To enable accelerated inference, install `vLLM` in your environment. To install `vLLM` inside the NeMo Framework container, follow the steps below as shared in [Export-Deploy's README](https://github.com/nvidia-nemo/export-deploy?tab=readme-ov-file#install-tensorrt-llm-vllm-or-trt-onnx-backend):
 
 ```shell
 cd /opt/Export-Deploy
 uv sync --inexact --link-mode symlink --locked --extra vllm $(cat /opt/uv_args.txt)
 ```
 
-To install `vLLM` outside of the NeMo Framework container, follow the steps mentioned [here](https://github.com/nvidia-nemo/export-deploy?tab=readme-ov-file#install-tensorrt-llm-vllm-or-trt-onnx-backend:~:text=install%20transformerengine%20%2b%20vllm).
+To install `vLLM` outside of the NeMo Framework container, follow the steps mentioned [here](https://github.com/nvidia-nemo/export-deploy?tab=readme-ov-file#install-tensorrt-llm-vllm-or-trt-onnx-backend).
 
 If you prefer to evaluate the Automodel checkpoint without using the `vLLM` backend, remove the `--use_vllm_backend` flag from the command above.