chore: generate daily Jules orchestration report

artifacts/jules-orchestration-report.json

@@ -7,7 +7,6 @@
     "adapters": {
       "branches": [
         "origin/codex/adapters-tests-fix-17147935552049199599",
-        "origin/feat-external-adapters-3267603025843827203",
         "origin/feat-external-adapters-9733759582368835911",
         "origin/feat/adapters-1144079942606232902",
         "origin/feat/adapters-11642089546824360047",
@@ -16,9 +15,8 @@
         "origin/feat/adapters-external-framework-support-11607098031212450418",
         "origin/feat/adapters-external-framework-support-15010148583076995848",
         "origin/feat/adapters-external-framework-support-4749774228548555690",
-        "origin/feat/agent-adapters-process-input-5684793405977170593",
         "origin/feat/expand-agent-adapters-12161969340909101809",
-        "origin/feat/external-agent-adapters-13715469629108022676",
+        "origin/feat/summit-adapters-11704903399368226114",
         "origin/jules-adapters-feature-12232237172160885155"
       ],
       "drift_details": [],
@@ -51,12 +49,9 @@
       "branches": [
         "origin/codex/implement-cac-registry-and-leaderboard",
         "origin/codex/implement-cac-registry-and-leaderboard-dgsvpc",
-        "origin/feat-leaderboard-17082338829991401739",
         "origin/feat-leaderboard-aggregation-16941054294671755273",
-        "origin/feat/leaderboard-14902444431531774320",
         "origin/feat/leaderboard-9662354552377997420",
         "origin/feat/leaderboard-infrastructure-17439300743604331882",
-        "origin/feat/leaderboard-infrastructure-2227927009890021255",
         "origin/feat/leaderboard-infrastructure-3414495734972084023",
         "origin/feat/leaderboard-infrastructure-5546749211519961205",
         "origin/feat/leaderboard-infrastructure-9637387970699399937",
@@ -77,7 +72,10 @@
       "branches": [
         "origin/codex/add-vendor-risk-monitoring-for-sdk-compatibility",
         "origin/codex/add-vendor-risk-monitoring-for-sdk-compatibility-8ksej6",
+        "origin/codex/define-consistency-slas-and-monitoring",
         "origin/codex/define-integration-and-monitoring-protocols",
+        "origin/codex/document-digital-experience-monitoring-workflow",
+        "origin/codex/implement-digital-experience-monitoring-workflow",
         "origin/codex/implement-watchlist-and-monitoring-service",
         "origin/codex/integrate-data-quality-monitoring-features",
         "origin/comprehensive-monitoring-13502136200912441147",
@@ -89,7 +87,6 @@
         "origin/feature/data-quality-monitoring-642339245539517222",
         "origin/feature/election-integrity-monitoring-16407447073282820411",
         "origin/monitoring-automation-fixes-5062672001959632732",
-        "origin/monitoring-workflows-7656515262318334662",
         "origin/otel-monitoring-fix-13162280351825968459",
         "origin/summit-monitoring-observability-8737461972222487444",
         "origin/summit-monitoring-observability-9207129870017144176"
@@ -114,8 +111,7 @@
         "origin/feat/fs-researcher-subsumption-15476375057602099060",
         "origin/research/agent-ecosystem-benchmarks-11617083115510894602",
         "origin/research/agent-ecosystem-report-and-benchmarks-5584588839440822424",
-        "origin/research/ai-agent-ecosystem-benchmark-expansion-4522012131210320029",
-        "origin/update-agent-ecosystem-research-17318094725690245322"
+        "origin/research/ai-agent-ecosystem-benchmark-expansion-4522012131210320029"
       ],
       "drift_details": [],
       "duplicate_prs_detected": true,

plan.md

@@ -1,8 +1,21 @@
-1. The CI is failing across many jobs during `pnpm/action-setup@v4` and `actions/setup-node@v4` with `ERR_PNPM_OUTDATED_LOCKFILE`.
-2. The root cause is that our changes in the previous step modified `.github/workflows` to include `fetch-depth: 0` and `fetch-tags: true`, but we didn't touch `pnpm-lock.yaml`.
-3. Wait, the error message says: `Cannot install with "frozen-lockfile" because pnpm-lock.yaml is not up to date with <ROOT>/agents/governance/package.json`.
-4. Ah, the `agents/governance/package.json` was probably updated in the base branch or by another PR, and the `pnpm-lock.yaml` is out of sync.
-5. The memory guidelines state: "When modifying workspace `package.json` files, ensure the root `pnpm-lock.yaml` is synchronized (e.g., using `pnpm install --no-frozen-lockfile` or `pnpm install --lockfile-only` and committing the result) to prevent `ERR_PNPM_OUTDATED_LOCKFILE` failures in CI pipelines that enforce `--frozen-lockfile`."
-6. Let's fix the lockfile issue by resolving the `pnpm-lock.yaml` locally. Wait, running `pnpm install --lockfile-only` locally failed due to missing `@react-navigation/bottom-tabs@7.2.2` and `detox@20.28.7` because these versions don't exist in the registry (maybe they are private or were yanked).
-7. Actually, the error in CI is about `agents/governance/package.json` specifiers `{"typescript":"^5.9.3","@types/node":"^20.10.0","vitest":"^1.0.0"}` not matching the lockfile.
-8. If I just look at `agents/governance/package.json` and revert any unintended changes or fix the lockfile just for that package.
+1. *Understand the Goal*
+   - Act as the Summit orchestration supervisor for scheduled Jules sessions.
+   - Monitor active sessions (monitoring, benchmark expansion, adapters, leaderboard, research) for scope drift and duplicate PRs.
+   - Detect deterministic artifact violations across sessions.
+   - Generate a daily summary report.
+   - Output: `artifacts/jules-orchestration-report.json`
+
+2. *Identify the existing orchestrator script*
+   - Based on earlier exploration, the main GitHub action workflow for this task is `.github/workflows/jules-orchestration.yml`.
+   - It runs `python3 scripts/monitoring/jules_orchestrator.py`.
+   - `scripts/monitoring/jules_orchestrator.py` correctly handles finding branches by session and checks for duplicate PRs, scope drift, and deterministic artifact violations (timestamps, etc.).
+   - Running `python3 scripts/monitoring/jules_orchestrator.py` outputs exactly `artifacts/jules-orchestration-report.json`.
+
+3. *Verify output*
+   - The user requests: Deliverable "Scheduled report surface and artifacts." Output `artifacts/jules-orchestration-report.json`
+   - Since I've already run the `python3 scripts/monitoring/jules_orchestrator.py` script which generates this exact artifact successfully, and we have the artifact.
+
+4. *Check Pre-commit*
+   - Follow standard pre-commit instructions as stated by `pre_commit_instructions`.
+
+5. *Commit and Submit*