docs: add compiler-smoke-e2e to architecture tree and ado-script.md

AGENTS.md

@@ -270,6 +270,7 @@ fail-closed and only pauses when the agent actually proposed a reviewed output.
 │           ├── github-app-token/ # GitHub App token minter (bundled to github-app-token.js; mints installation token in Agent + Detection when engine.github-app-token is set)
 │           ├── executor-e2e/ # Stage 3 safe-output E2E test harness (not a bundle; runs deterministic scenarios against a real ADO project and files a GitHub issue on failure)
 │           ├── prepare-pr-base/ # create-pull-request preparer (bundled to prepare-pr-base.js): Agent mode uses ADO diff metadata + bounded dual-ref fallback to make the merge-base reachable; SafeOutputs mode fetches only the target worktree tip
+│           ├── compiler-smoke-e2e/ # Compiler candidate E2E orchestrator (not a bundle; stages the compiler candidate as a supply-chain.pipeline-artifact source, pushes to a mirror branch, queues the five smoke-suite pipeline definitions, and asserts they all go green)
 │           ├── trigger-e2e/ # Test-only gate-spec / trigger-evaluation harness (not a bundle): mirrors Rust `Fact::ALL` in `gate-spec.ts`; `fact-catalog.gen.json` is generated by `export-fact-catalog` and drift-guarded by CI
 │           └── shared/   # Shared modules across bundles (auth, ado-client, env-facts, types.gen.ts)
 ├── tests/                # Integration tests and fixtures

docs/ado-script.md

@@ -101,6 +101,16 @@ pipeline** as runtime helpers. Today it produces thirteen bundles:
 > `NON_BUNDLE_DIRS` in `src/__tests__/bundle-coverage.test.ts` so the
 > shipped-bundle guard ignores it. The compiler never references it.
 
+> **Test-only, not shipped: `compiler-smoke-e2e`.** The workspace also contains a
+> `src/compiler-smoke-e2e/` harness that orchestrates the compiler candidate
+> smoke suite: it stages the compiler candidate as a
+> `supply-chain.pipeline-artifact` source across the five real smoke fixtures,
+> pushes to a short-lived mirror branch, queues the registered pipeline
+> definitions, and asserts they all go green. It is **not** a runtime bundle
+> and is listed in `NON_BUNDLE_DIRS` in
+> `src/__tests__/bundle-coverage.test.ts` so the shipped-bundle guard ignores
+> it. The compiler never references it directly.
+
 > **Test-only, not shipped: `trigger-e2e`.** The workspace also contains a
 > `src/trigger-e2e/` harness (with its own `__tests__/` subdirectory) that
 > provides the `FACT_META` gate-spec table and end-to-end trigger-evaluation
@@ -564,6 +574,7 @@ scripts/ado-script/
 │   │   ├── gate-spec.ts         # FACT_META mirror of Rust Fact::ALL; drift-guarded by export-fact-catalog + fact-catalog.gen.json
 │   │   ├── fact-catalog.gen.json # generated by `cargo run -- export-fact-catalog`; deep-compared by gate-spec.test.ts
 │   │   └── __tests__/           # gate-spec drift tests and trigger-evaluation scenario tests
+│   ├── compiler-smoke-e2e/      # test-only: compiler candidate E2E orchestrator (not a bundle; stages candidate, queues smoke-suite pipelines, asserts green)
 │   └── executor-e2e/            # test-only: Stage 3 safe-output E2E harness (not a bundle; built to test-bin/executor-e2e.js)
 ├── test/                        # End-to-end smoke tests (gate, import, exec-context-pr)
 ├── gate.js                      # ncc bundle output (gitignored)