<!-- SPDX-FileCopyrightText: Copyright (c) 2026 NVIDIA CORPORATION & AFFILIATES. All rights reserved. --> <!-- SPDX-License-Identifier: Apache-2.0 -->

Run Maintainer E2E

Route the Request

Request	Procedure
Run working-tree source or a selected local commit	Local Runs
Run the latest PR commit on GitHub, including failure-triggered comparison with its exact base	Manual PR Runs
Run the current main commit on GitHub	Main Runs and the Launchable boundary below
Inspect existing evidence for a release decision	Report the Release Context
Triage, diagnose, debug, or repair an E2E failure	Load Audit E2E Assertions; this skill still owns dispatch and run-level reporting.
Classify one failed GitHub Actions job	For E2E failures, use the assertion-audit route above. For other jobs, load nemoclaw-maintainer-classify-ci-failure.

A new GitHub candidate run tests the latest PR commit or the current main commit. Manual PR runs may replay the PR base after a candidate failure, as described in their procedure. Report arbitrary historical candidate selection as unsupported. Preserve the workflow's identity and trust checks.

Push runs select change-relevant E2E and publish Relevant E2E; they do not always run the full suite. Only a full manual run publishes Release qualification. That aggregate reports the full suite; it does not decide whether a tag can proceed. A generic E2E request does not authorize Exact staging Brev Launchable.

Use .github/workflows/e2e.yaml from trusted main for GitHub runs. Do not substitute local live E2E unless the maintainer explicitly requests local execution. Do not load a dispatch reference for a release inspection unless the maintainer requests a new run.

Staging Brev Launchable Boundary