Bright Data CI Contract Lane

Overview

Keep pull-request verification credential-free and deterministic. Test the Bright Data adapter against fixtures by default, then place any necessary live probe in an independent protected job with a dedicated credential, approved target, and one-operation budget.

Prerequisites

• A repository test command and representative sanitized success and failure fixtures
• The CI workflow and Bright Data adapter paths
• Maintainer approval before creating an optional live lane

Instructions

Step 1: Audit the workflow boundary

Read the workflow and Grep for secrets, direct provider calls, artifact uploads, and execution from untrusted forks. Map every test to either the offline contract lane or the protected live lane.

Step 2: Add the required offline lane