[OPIK-5682] [FE] Wire agent config to sandbox run via mask_id

[miguelgrc]

Details

Wire up agent configuration changes to the sandbox Run flow using the mask_id mechanism.

Previously, clicking Run in the Agent Sandbox ignored any configuration edits — the job was created without config context. Now, when the user edits configuration values and clicks Run, the system:

1. Validates all config fields (scalar + prompt)
2. Saves any dirty prompt versions to get commit IDs
3. Creates a MASK (temporary config overlay) via PATCH /blueprints/ with type: "mask"
4. Passes the mask_id to the job creation request

This keeps the version history clean — masks are internal-only and don't appear in the blueprint history. The existing "Save as new version" flow continues to create permanent BLUEPRINTs.

Key changes:

• useAgentConfigurationSave — extracted shared validation/payload logic into validateAndBuildPayload(), added buildMaskPayload() and hasChanges()
• AgentConfigurationEditView — converted to forwardRef with imperative handle exposing hasChanges + buildMaskPayload
• AgentRunnerConnectedState — handleRun checks for config changes, creates mask if needed, blocks run if validation fails

Data flow: Edit config → click Run → hasChanges() → buildMaskPayload() (validates + returns payload) → parent calls mutation → gets mask_id → passes to job creation

Change checklist

• User facing
• Documentation update

Issues

• OPIK-5682

Testing

• npx tsc --noEmit — passes
• npx eslint on all changed files — passes
• Existing tests (4/4) — pass

Manual verification:

1. Open Agent Sandbox, connect agent
2. Run without config changes → no mask_id in job payload ✓
3. Edit config, Run → PATCH creates mask, job includes mask_id ✓
4. Edit config with invalid values, Run → validation blocks, no requests ✓
5. "Save as new version" → creates BLUEPRINT, appears in history ✓
6. Config changes don't pollute version history (masks are invisible) ✓

Documentation

N/A

[github-actions]

🔄 Test environment deployment process has started

Phase 1: Deploying base version 1.10.59-4802 (from main branch) if environment doesn't exist
Phase 2: Building new images from PR branch miguelg/OPIK-5682-agent-sandbox-e2e-journey
Phase 3: Will deploy newly built version after build completes

You can monitor the progress here.

[CometActions]

✅ Test environment is now available!

To configure additional Environment variables for your environment, run [Deploy Opik AdHoc Environment workflow] (https://github.com/comet-ml/comet-deployment/actions/workflows/deploy_opik_adhoc_env.yaml)

Access Information

• URL: https://pr-6082.dev.comet.com
• Cluster: comet-ml-development
• Namespace: pr-6082
• Version: 1.10.59-6082-merge-1768
• Application logs: View in Grafana

The deployment has completed successfully and the version has been verified.

[CometActions]

🌙 Nightly cleanup: The test environment for this PR (pr-6082) has been cleaned up to free cluster resources. PVCs are preserved — re-deploy to restore the environment.

[github-actions]

🔄 Test environment deployment process has started

Phase 1: Deploying base version 1.10.59-4802 (from main branch) if environment doesn't exist
Phase 2: Building new images from PR branch miguelg/OPIK-5682-agent-sandbox-e2e-journey
Phase 3: Will deploy newly built version after build completes

You can monitor the progress here.

[CometActions]

✅ Test environment is now available!

To configure additional Environment variables for your environment, run [Deploy Opik AdHoc Environment workflow] (https://github.com/comet-ml/comet-deployment/actions/workflows/deploy_opik_adhoc_env.yaml)

Access Information

• URL: https://pr-6082.dev.comet.com
• Cluster: comet-ml-development
• Namespace: pr-6082
• Version: 1.10.59-6082-merge-1773
• Application logs: View in Grafana

The deployment has completed successfully and the version has been verified.

[aadereiko]

LGTM, thanks!