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

Add a Managed Runtime Provider

Add one provider through the repository's runtime-provider contract. Keep generic orchestration independent of provider implementations and provider names.

Confirm Product Scope

Apply the product scope gate in AGENTS.md before implementation or approval. Require an accepted issue or accepted design decision that defines ownership, lifecycle, compatibility, security, and validation. A valid bundle or passing test does not establish a supported surface.

Keep the portable experimental profile independent. Do not change portable selection, lifecycle, or compatibility behavior as part of a native managed-provider change.

Load Current Authority

Before planning, editing, or reviewing:

1. Read src/lib/onboard/runtime-provider/contract.ts and registry.ts.
2. Read activation.ts, current.ts, and native-qualification-authority.ts.
3. Read the candidate provider factory and its provider-owned helpers.
4. Trace SandboxEntry.openshellDriver through onboarding and every lifecycle action in scope.
5. Read the focused contract, activation, provider, architecture, and E2E-support tests.

Use checked-in source and tests as behavior authority. Use these references for interpretation:

• Read Bundle API Contract before changing a provider bundle.
• Read Activation and Qualification before making a provider production-selectable.
• Read Implementation and Review before editing generic orchestration, planning validation, or reviewing a provider PR.

Choose the Delivery State

Name the intended state before coding: