test(executor-e2e): queue-build never smoke-tested — E2E_QUEUE_PIPELINE_ID unset in 'executor e2e' definition #1422

Summary

In the deterministic executor E2E smoke suite, the queue-build scenario is skipped because E2E_QUEUE_PIPELINE_ID is not set in the pipeline definition, so this safe output is never exercised end-to-end.

• Build: msazuresphere/AgentPlayground #619303 (executor e2e, 20260708.4)

[SKIP] queue-build (skipped: queue-build: E2E_QUEUE_PIPELINE_ID is not set; supply it to enable this scenario)

Details

scripts/ado-script/src/executor-e2e/scenarios/build.ts queueBuild throws SkipError when E2E_QUEUE_PIPELINE_ID is unset. The executor e2e pipeline definition does not provide it, so queue-build is silently skipped on every run.

Suggested action

Provision a safe, cancel-on-assert target pipeline id in the executor e2e definition (a no-op/self pipeline in AgentPlayground) and set E2E_QUEUE_PIPELINE_ID so queue-build is smoke-tested like the other write safe outputs. The scenario already cancels the queued build in cleanup, so the only requirement is a low-cost queue target.

Low priority relative to the add-build-tag 411 bug and the upload-attachment harness gap, but tracking it so queue-build doesn't stay perpetually unverified.