flaky-smoke-tests

Use `az devops invoke` with the build timeline resource and filter records whose names contain `Smoke test iteration`. Treat `succeededWithIssues`, `failed`, and tasks with error issues as failed iterations, since `continueOnError: true` masks failures in the overall build result.

Use `az pipelines runs artifact download` for platform-scoped `logs-*` artifacts and `az devops invoke` with the `logs` resource (not `buildLog`) for individual task logs. Convert the JSON `value` array to plain text using `jq` or PowerShell `ConvertFrom-Json`.

The Flaky Smoke Tests pipeline uses `continueOnError: true` on iteration tasks, so failed iterations report as `succeededWithIssues` and later iterations still run. You must inspect every iteration task in the timeline rather than the overall build or job result.

Copilot runtime process logs are captured at `copilot-runtime-logs/process-*.log` inside each suite directory by `dumpFailureDiagnostics`. Agent Host sessions write full trace logs there, while Chat Sessions and Local sessions write only minimal startup logs.

Yes, use `az pipelines run --id 700` with the `iterations` parameter as a JSON array like `[1,2,3,4,5,6]`. Enable only relevant platforms via `VSCODE_BUILD_MACOS`, `VSCODE_BUILD_LINUX`, and `VSCODE_BUILD_WIN32` parameters, and cancel obsolete runs on the same branch first.

The task log is iteration-scoped and authoritative for the failure summary and time range. The platform logs artifact is job-scoped and shared across iterations, so later iterations can overwrite files. Use a one-iteration diagnostic run when detailed per-iteration diagnostics are required.