Evolution Advisory

What Changed in Your Codebase

We've detected 7 changes that differ from your project's normal patterns. Each change shows what typically happens versus what we observed this time.

0 of 7 resolved

🚀

Release Cadence

Deployment

What this means: Longer time between releases than usual.

Typical:

0.0008

This Time:

142.8

694167.3x above typical range

Trigger: main

↘ Returned to baseline

Supporting Evidence

⚠️ Action Required

when deployments and code changes happen together, code spread and release frequency tend to move together.

What this means: Changes are spreading across unrelated parts of the codebase. This makes reviews harder and increases the chance of unexpected side effects. Escalated from Worth Monitoring — multiple correlated patterns converge on the same signal families.

Recommendation: Review recent PRs for scope creep. Consider breaking large changes into focused commits.

⚠️ Action Required

when deployments and code changes happen together, file count and release frequency tend to move together.

What this means: Commits are touching more files than usual, increasing review burden and risk of regressions. Escalated from Worth Monitoring — multiple correlated patterns converge on the same signal families.

Recommendation: Monitor PR sizes. If this persists, investigate whether large refactors need better decomposition.

👁️ Worth Monitoring

when dependency changes and deployments happen together, dependency count and release frequency tend to move together.

What this means: The dependency count is growing, expanding the supply-chain attack surface and potential for version conflicts.

Recommendation: Audit new dependencies for necessity, maintenance status, and known vulnerabilities.

Drift Investigation Prompt

Development pattern shift detected in Deployment.\n\nSIGNAL: Release Cadence is 694167.3x above the typical baseline (observed: 142.8, typical: 0.0008).\nTRIGGER COMMIT: main — \n\nRECENT COMMITS (20 total, showing top 5):\n  e574ef3e — chore(deps): bump the workerd-and-workers-types group with 2 (5 files)\n  bf97065e — refactor handling of Node built-in modules (#11845)

 (3 files)\n  10aa2f98 — feat: update CI workflow for other Node versions (#11833)

* (1 files)\n  5e89bd16 — refactor: consistenly import expect from vitest (#11851)

*  (36 files)\n  0f8d69d3 — containers: users can set multiple tiers for constraints (#1 (9 files)\n  ... and 15 more commits\n\nCORRELATED PATTERNS:\n  [CRITICAL] when deployments and code changes happen together, code spread and release frequency tend to move together.\n    → Review recent PRs for scope creep. Consider breaking large changes into focused commits.\n  [CRITICAL] when deployments and code changes happen together, file count and release frequency tend to move together.\n    → Monitor PR sizes. If this persists, investigate whether large refactors need better decomposition.\n  [WATCH] when dependency changes and deployments happen together, dependency count and release frequency tend to move together.\n    → Audit new dependencies for necessity, maintenance status, and known vulnerabilities.\n\nINVESTIGATE:\n1. Was this change intentional or did the AI drift from goals?\n2. Review commit main — what specifically caused the deviation?\n3. Suggest a course correction (not a bug fix — a realignment).\n\nAFTER FIX:\nRun `evo analyze . --verify` to re-analyze and compare against this run.\nIf the change was intentional, no fix needed — accept it in the report.

Use with: Cursor — paste in chat Claude Code — paste in terminal Copilot — paste in chat panel

After investigation:

AI suggests fixes → apply the changes to your code
Run evo analyze . --verify to re-analyze and compare against this run
If the change was intentional, click Accept above to dismiss it

📝

Co-change Novelty

Version Control

What this means: Unusually low novelty — changes are more repetitive than normal, touching only well-known file combinations.

Typical:

1.00

This Time:

0.0000

105.3x below typical range

Trigger: 331d4de9 Revert "Bump the workerd-and-workers-types group with 2 upda

↘ Returned to baseline

Supporting Evidence

⚠️ Action Required

when CI builds and code changes happen together, novelty of file pairings and build time tend to move together.

What this means: File co-change novelty is unusually low. While familiar patterns reduce risk, this could indicate repetitive or mechanical changes rather than normal development. Escalated from Needs Attention — multiple correlated patterns converge on the same signal families.

Recommendation: Review whether recent commits are routine maintenance or a sign of narrow, repetitive modifications that lack expected variety.

ℹ️ Informational

when deployments and code changes happen together, novelty of file pairings tends to move in opposite directions.

What this means: File co-change novelty is unusually low. While familiar patterns reduce risk, this could indicate repetitive or mechanical changes rather than normal development.

Recommendation: Review whether recent commits are routine maintenance or a sign of narrow, repetitive modifications that lack expected variety.

ℹ️ Informational

when dependency changes and code changes happen together, novelty of file pairings tends to move in opposite directions.

What this means: File co-change novelty is unusually low. While familiar patterns reduce risk, this could indicate repetitive or mechanical changes rather than normal development.

Recommendation: Review whether recent commits are routine maintenance or a sign of narrow, repetitive modifications that lack expected variety.

Drift Investigation Prompt

Development pattern shift detected in Version Control.\n\nSIGNAL: Co-change Novelty is 105.3x below the typical baseline (observed: 0.0000, typical: 1.00).\nTRIGGER COMMIT: 331d4de9 — Revert "Bump the workerd-and-workers-types group with 2 updates" (#12776)\n\nFILES CHANGED IN TRIGGER (5):\n  - .changeset/dependabot-update-12768.md\n  - packages/miniflare/package.json\n  - packages/wrangler/package.json\n  - pnpm-lock.yaml\n  - pnpm-workspace.yaml\n\nRECENT COMMITS (20 total, showing top 5):\n  e574ef3e — chore(deps): bump the workerd-and-workers-types group with 2 (5 files)\n  bf97065e — refactor handling of Node built-in modules (#11845)

 (3 files)\n  10aa2f98 — feat: update CI workflow for other Node versions (#11833)

* (1 files)\n  5e89bd16 — refactor: consistenly import expect from vitest (#11851)

*  (36 files)\n  0f8d69d3 — containers: users can set multiple tiers for constraints (#1 (9 files)\n  ... and 15 more commits\n\nCORRELATED PATTERNS:\n  [CRITICAL] when CI builds and code changes happen together, novelty of file pairings and build time tend to move together.\n    → Investigate which files are being combined unexpectedly. Prioritize testing these changes.\n  [INFO] when deployments and code changes happen together, novelty of file pairings tends to move in opposite directions.\n    → Review whether recent commits are routine maintenance or a sign of narrow, repetitive modifications that lack expected variety.\n  [INFO] when dependency changes and code changes happen together, novelty of file pairings tends to move in opposite directions.\n    → Review whether recent commits are routine maintenance or a sign of narrow, repetitive modifications that lack expected variety.\n\nINVESTIGATE:\n1. Was this change intentional or did the AI drift from goals?\n2. Review commit 331d4de9 — what specifically caused the deviation?\n3. Suggest a course correction (not a bug fix — a realignment).\n\nAFTER FIX:\nRun `evo analyze . --verify` to re-analyze and compare against this run.\nIf the change was intentional, no fix needed — accept it in the report.

Use with: Cursor — paste in chat Claude Code — paste in terminal Copilot — paste in chat panel

After investigation:

AI suggests fixes → apply the changes to your code
Run evo analyze . --verify to re-analyze and compare against this run
If the change was intentional, click Accept above to dismiss it

⚙️

Build Duration

CI / Build

What this means: Build took longer than usual.

Typical:

33.50

This Time:

3,637.0

74.8x above typical range

Trigger: 56e09288

↘ Returned to baseline

Supporting Evidence

⚠️ Action Required

when CI builds and code changes happen together, change focus and build time tend to move together.

What this means: Builds are taking longer. Slower CI feedback loops reduce developer productivity and delay catching issues. Escalated from Worth Monitoring — multiple correlated patterns converge on the same signal families. Changes span files that don't normally change together, suggesting cross-cutting concerns that may be harder to test. Escalated from Worth Monitoring — multiple correlated patterns converge on the same signal families.

Recommendation: Profile the build pipeline to identify bottlenecks. Check for newly added expensive tests or build steps. Review whether these cross-cutting changes have adequate test coverage.

⚠️ Action Required

when CI builds and code changes happen together, file count and build time tend to move together.

Recommendation: Monitor PR sizes. If this persists, investigate whether large refactors need better decomposition.

⚠️ Action Required

when CI builds and code changes happen together, novelty of file pairings and build time tend to move together.

What this means: Files that don't normally change together are being modified in the same commits. This indicates novel, untested interactions that may introduce bugs. Escalated from Needs Attention — multiple correlated patterns converge on the same signal families.

Recommendation: Investigate which files are being combined unexpectedly. Prioritize testing these changes.

Show 1 more supporting evidence

👁️ Worth Monitoring

when CI builds and dependency changes happen together, dependency count and build time tend to move in opposite directions.

What this means: The dependency count is growing, expanding the supply-chain attack surface and potential for version conflicts.

Recommendation: Audit new dependencies for necessity, maintenance status, and known vulnerabilities.

Drift Investigation Prompt

Development pattern shift detected in CI / Build.\n\nSIGNAL: Build Duration is 74.8x above the typical baseline (observed: 3,637.0, typical: 33.50).\nTRIGGER COMMIT: 56e09288 — \n\nRECENT COMMITS (20 total, showing top 5):\n  e574ef3e — chore(deps): bump the workerd-and-workers-types group with 2 (5 files)\n  bf97065e — refactor handling of Node built-in modules (#11845)

 (3 files)\n  10aa2f98 — feat: update CI workflow for other Node versions (#11833)

* (1 files)\n  5e89bd16 — refactor: consistenly import expect from vitest (#11851)

*  (36 files)\n  0f8d69d3 — containers: users can set multiple tiers for constraints (#1 (9 files)\n  ... and 15 more commits\n\nCORRELATED PATTERNS:\n  [CRITICAL] when CI builds and code changes happen together, change focus and build time tend to move together.\n    → Profile the build pipeline to identify bottlenecks. Check for newly added expensive tests or build steps.\n    → Review whether these cross-cutting changes have adequate test coverage.\n  [CRITICAL] when CI builds and code changes happen together, file count and build time tend to move together.\n    → Monitor PR sizes. If this persists, investigate whether large refactors need better decomposition.\n  [CRITICAL] when CI builds and code changes happen together, novelty of file pairings and build time tend to move together.\n    → Investigate which files are being combined unexpectedly. Prioritize testing these changes.\n  [INFO] when CI builds and dependency changes happen together, dependency count and build time tend to move in opposite directions.\n    → Confirm test coverage hasn't decreased alongside faster builds.\n\nINVESTIGATE:\n1. Was this change intentional or did the AI drift from goals?\n2. Review commit 56e09288 — what specifically caused the deviation?\n3. Suggest a course correction (not a bug fix — a realignment).\n\nAFTER FIX:\nRun `evo analyze . --verify` to re-analyze and compare against this run.\nIf the change was intentional, no fix needed — accept it in the report.

Use with: Cursor — paste in chat Claude Code — paste in terminal Copilot — paste in chat panel

After investigation:

AI suggests fixes → apply the changes to your code
Run evo analyze . --verify to re-analyze and compare against this run
If the change was intentional, click Accept above to dismiss it

Show technical details

The run duration for this change was 3,637.0. Historically, similar changes had a value of 33.50 ± 32.50.

📝

Files Changed

Version Control

What this means: More files changed than usual in this commit.

Typical:

5.00

This Time:

237

52.2x above typical range

Trigger: ead6246a Use vitest#expect from the local context (#12385)

↘ Returned to baseline

Supporting Evidence

⚠️ Action Required

when CI builds and code changes happen together, file count and build time tend to move together.

Recommendation: Monitor PR sizes. If this persists, investigate whether large refactors need better decomposition.

⚠️ Action Required

when deployments and code changes happen together, file count and release frequency tend to move together.

Recommendation: Monitor PR sizes. If this persists, investigate whether large refactors need better decomposition.

👁️ Worth Monitoring

when code changes occur, file count tends to increase.

What this means: Commits are touching more files than usual, increasing review burden and risk of regressions.

Recommendation: Monitor PR sizes. If this persists, investigate whether large refactors need better decomposition.

Drift Investigation Prompt

Development pattern shift detected in Version Control.\n\nSIGNAL: Files Changed is 52.2x above the typical baseline (observed: 237, typical: 5.00).\nTRIGGER COMMIT: ead6246a — Use vitest#expect from the local context (#12385)\n\nFILES CHANGED IN TRIGGER (237):\n  - fixtures/additional-modules/eslint.config.mjs\n  - fixtures/additional-modules/package.json\n  - fixtures/additional-modules/test/index.test.ts\n  - fixtures/browser-rendering/eslint.config.mjs\n  - fixtures/browser-rendering/package.json\n  - fixtures/browser-rendering/test/index.spec.ts\n  - fixtures/d1-read-replication-app/eslint.config.mjs\n  - fixtures/d1-read-replication-app/package.json\n  - fixtures/d1-read-replication-app/tests/index.test.ts\n  - fixtures/d1-worker-app/eslint.config.mjs\n  - fixtures/d1-worker-app/package.json\n  - fixtures/d1-worker-app/tests/index.test.ts\n  - fixtures/dev-registry/eslint.config.mjs\n  - fixtures/dev-registry/package.json\n  - fixtures/dev-registry/tests/dev-registry.test.ts\n  ... and 222 more\n\nRECENT COMMITS (20 total, showing top 5):\n  e574ef3e — chore(deps): bump the workerd-and-workers-types group with 2 (5 files)\n  bf97065e — refactor handling of Node built-in modules (#11845)

 (3 files)\n  10aa2f98 — feat: update CI workflow for other Node versions (#11833)

* (1 files)\n  5e89bd16 — refactor: consistenly import expect from vitest (#11851)

*  (36 files)\n  0f8d69d3 — containers: users can set multiple tiers for constraints (#1 (9 files)\n  ... and 15 more commits\n\nCORRELATED PATTERNS:\n  [CRITICAL] when CI builds and code changes happen together, file count and build time tend to move together.\n    → Monitor PR sizes. If this persists, investigate whether large refactors need better decomposition.\n  [CRITICAL] when deployments and code changes happen together, file count and release frequency tend to move together.\n    → Monitor PR sizes. If this persists, investigate whether large refactors need better decomposition.\n  [WATCH] when code changes occur, file count tends to increase.\n    → Monitor PR sizes. If this persists, investigate whether large refactors need better decomposition.\n\nINVESTIGATE:\n1. Was this change intentional or did the AI drift from goals?\n2. Review commit ead6246a — what specifically caused the deviation?\n3. Suggest a course correction (not a bug fix — a realignment).\n\nAFTER FIX:\nRun `evo analyze . --verify` to re-analyze and compare against this run.\nIf the change was intentional, no fix needed — accept it in the report.

Use with: Cursor — paste in chat Claude Code — paste in terminal Copilot — paste in chat panel

After investigation:

AI suggests fixes → apply the changes to your code
Run evo analyze . --verify to re-analyze and compare against this run
If the change was intentional, click Accept above to dismiss it

Show technical details

The files touched for this change was 237. Historically, similar changes had a value of 5.00 ± 3.00.

📦

Total Dependencies

Dependencies

What this means: Dependency count increased.

Typical:

1,448.0

This Time:

1,493

30.4x above typical range

Trigger: c648dc52

↘ Returned to baseline

Supporting Evidence

👁️ Worth Monitoring

when dependency changes and deployments happen together, dependency count and release frequency tend to move together.

What this means: The dependency count is growing, expanding the supply-chain attack surface and potential for version conflicts.

Recommendation: Audit new dependencies for necessity, maintenance status, and known vulnerabilities.

👁️ Worth Monitoring

when CI builds and dependency changes happen together, dependency count and build time tend to move in opposite directions.

What this means: The dependency count is growing, expanding the supply-chain attack surface and potential for version conflicts.

Recommendation: Audit new dependencies for necessity, maintenance status, and known vulnerabilities.

Drift Investigation Prompt

Development pattern shift detected in Dependencies.\n\nSIGNAL: Total Dependencies is 30.4x above the typical baseline (observed: 1,493, typical: 1,448.0).\nTRIGGER COMMIT: c648dc52 — \n\nRECENT COMMITS (20 total, showing top 5):\n  e574ef3e — chore(deps): bump the workerd-and-workers-types group with 2 (5 files)\n  bf97065e — refactor handling of Node built-in modules (#11845)

 (3 files)\n  10aa2f98 — feat: update CI workflow for other Node versions (#11833)

* (1 files)\n  5e89bd16 — refactor: consistenly import expect from vitest (#11851)

*  (36 files)\n  0f8d69d3 — containers: users can set multiple tiers for constraints (#1 (9 files)\n  ... and 15 more commits\n\nCORRELATED PATTERNS:\n  [WATCH] when dependency changes and deployments happen together, dependency count and release frequency tend to move together.\n    → Audit new dependencies for necessity, maintenance status, and known vulnerabilities.\n  [INFO] when CI builds and dependency changes happen together, dependency count and build time tend to move in opposite directions.\n    → Confirm test coverage hasn't decreased alongside faster builds.\n\nINVESTIGATE:\n1. Was this change intentional or did the AI drift from goals?\n2. Review commit c648dc52 — what specifically caused the deviation?\n3. Suggest a course correction (not a bug fix — a realignment).\n\nAFTER FIX:\nRun `evo analyze . --verify` to re-analyze and compare against this run.\nIf the change was intentional, no fix needed — accept it in the report.

Use with: Cursor — paste in chat Claude Code — paste in terminal Copilot — paste in chat panel

After investigation:

AI suggests fixes → apply the changes to your code
Run evo analyze . --verify to re-analyze and compare against this run
If the change was intentional, click Accept above to dismiss it

Show technical details

The dependency count for this change was 1,493. Historically, similar changes had a value of 1,448.0 ± 1.00.

📝

Change Locality

Version Control

What this means: The changed files frequently change together, suggesting a focused modification.

Typical:

0.0833

This Time:

1.00

7.4x above typical range

Trigger: 37a86071 Version Packages (#11890)

↘ Returned to baseline

Supporting Evidence

⚠️ Action Required

when CI builds and code changes happen together, change focus and build time tend to move together.

Recommendation: Profile the build pipeline to identify bottlenecks. Check for newly added expensive tests or build steps. Review whether these cross-cutting changes have adequate test coverage.

Drift Investigation Prompt

Development pattern shift detected in Version Control.\n\nSIGNAL: Change Locality is 7.4x above the typical baseline (observed: 1.00, typical: 0.0833).\nTRIGGER COMMIT: 37a86071 — Version Packages (#11890)\n\nFILES CHANGED IN TRIGGER (7):\n  - .changeset/fix-pages-deploy-command-injection.md\n  - packages/vite-plugin-cloudflare/CHANGELOG.md\n  - packages/vite-plugin-cloudflare/package.json\n  - packages/vitest-pool-workers/CHANGELOG.md\n  - packages/vitest-pool-workers/package.json\n  - packages/wrangler/CHANGELOG.md\n  - packages/wrangler/package.json\n\nRECENT COMMITS (19 total, showing top 5):\n  e574ef3e — chore(deps): bump the workerd-and-workers-types group with 2 (5 files)\n  bf97065e — refactor handling of Node built-in modules (#11845)

 (3 files)\n  10aa2f98 — feat: update CI workflow for other Node versions (#11833)

* (1 files)\n  5e89bd16 — refactor: consistenly import expect from vitest (#11851)

*  (36 files)\n  0f8d69d3 — containers: users can set multiple tiers for constraints (#1 (9 files)\n  ... and 14 more commits\n\nCORRELATED PATTERNS:\n  [CRITICAL] when CI builds and code changes happen together, change focus and build time tend to move together.\n    → Profile the build pipeline to identify bottlenecks. Check for newly added expensive tests or build steps.\n    → Review whether these cross-cutting changes have adequate test coverage.\n\nINVESTIGATE:\n1. Was this change intentional or did the AI drift from goals?\n2. Review commit 37a86071 — what specifically caused the deviation?\n3. Suggest a course correction (not a bug fix — a realignment).\n\nAFTER FIX:\nRun `evo analyze . --verify` to re-analyze and compare against this run.\nIf the change was intentional, no fix needed — accept it in the report.

Use with: Cursor — paste in chat Claude Code — paste in terminal Copilot — paste in chat panel

After investigation:

AI suggests fixes → apply the changes to your code
Run evo analyze . --verify to re-analyze and compare against this run
If the change was intentional, click Accept above to dismiss it

Show technical details

The change locality for this change was 1.00. Historically, similar changes had a value of 0.0833 ± 0.0833.

📝

Change Dispersion

Version Control

What this means: Changes spread across unrelated areas of the codebase.

Typical:

0.8648

This Time:

2.00

5.4x above typical range

Trigger: f63ab988 Migrate to Codeowners Plus for AND-based ownership enforceme

↘ Returned to baseline

Supporting Evidence

⚠️ Action Required

when deployments and code changes happen together, code spread and release frequency tend to move together.

Recommendation: Review recent PRs for scope creep. Consider breaking large changes into focused commits.

👁️ Worth Monitoring

when dependency changes and code changes happen together, code spread tends to move together.

What this means: Changes are spreading across unrelated parts of the codebase. This makes reviews harder and increases the chance of unexpected side effects.

Recommendation: Review recent PRs for scope creep. Consider breaking large changes into focused commits.

Drift Investigation Prompt

Development pattern shift detected in Version Control.\n\nSIGNAL: Change Dispersion is 5.4x above the typical baseline (observed: 2.00, typical: 0.8648).\nTRIGGER COMMIT: f63ab988 — Migrate to Codeowners Plus for AND-based ownership enforcement (#12729)\n\nFILES CHANGED IN TRIGGER (4):\n  - .codeowners\n  - .github/workflows/codeowners.yml\n  - CODEOWNERS.md\n  - codeowners.toml\n\nRECENT COMMITS (20 total, showing top 5):\n  e574ef3e — chore(deps): bump the workerd-and-workers-types group with 2 (5 files)\n  bf97065e — refactor handling of Node built-in modules (#11845)

 (3 files)\n  10aa2f98 — feat: update CI workflow for other Node versions (#11833)

* (1 files)\n  5e89bd16 — refactor: consistenly import expect from vitest (#11851)

*  (36 files)\n  0f8d69d3 — containers: users can set multiple tiers for constraints (#1 (9 files)\n  ... and 15 more commits\n\nCORRELATED PATTERNS:\n  [CRITICAL] when deployments and code changes happen together, code spread and release frequency tend to move together.\n    → Review recent PRs for scope creep. Consider breaking large changes into focused commits.\n  [WATCH] when dependency changes and code changes happen together, code spread tends to move together.\n    → Review recent PRs for scope creep. Consider breaking large changes into focused commits.\n\nINVESTIGATE:\n1. Was this change intentional or did the AI drift from goals?\n2. Review commit f63ab988 — what specifically caused the deviation?\n3. Suggest a course correction (not a bug fix — a realignment).\n\nAFTER FIX:\nRun `evo analyze . --verify` to re-analyze and compare against this run.\nIf the change was intentional, no fix needed — accept it in the report.

Use with: Cursor — paste in chat Claude Code — paste in terminal Copilot — paste in chat panel

After investigation:

AI suggests fixes → apply the changes to your code
Run evo analyze . --verify to re-analyze and compare against this run
If the change was intentional, click Accept above to dismiss it

Show technical details

The dispersion for this change was 2.00. Historically, similar changes had a value of 0.8648 ± 0.1429.

Next Steps

Investigate

Copy the prompt below and paste it into your AI assistant (Claude Code, Cursor, Copilot, ChatGPT). It will identify root causes and suggest fixes.

Fix

Apply the suggested changes. If a deviation was intentional, click Accept on its card above instead.

Verify

Run evo analyze . --verify to re-analyze and compare. A verification banner will show which deviations resolved, improved, or persist.

Investigation Prompt

Development drift analysis for cloudflare/workers-sdk (Feb 07, 2022 at 12:26 PM to Mar 13, 2026 at 05:30 PM). DEVIATIONS FROM BASELINE: - Deployment: Release Cadence — 0.0008 -> 142.8 - Version Control: Co-change Novelty — 1.00 -> 0.0000 - CI / Build: Build Duration — 33.50 -> 3,637.0 - Version Control: Files Changed — 5.00 -> 237 - Dependencies: Total Dependencies — 1,448.0 -> 1,493 - Version Control: Change Locality — 0.0833 -> 1.00 - Version Control: Change Dispersion — 0.8648 -> 2.00 Click "Show Full Prompt" to see the complete investigation prompt with evidence...

Development drift analysis for cloudflare/workers-sdk (Feb 07, 2022 at 12:26 PM to Mar 13, 2026 at 05:30 PM).

DEVIATIONS FROM BASELINE:

- Deployment / Release Cadence: 142.8 (typical: 0.0008, 694167.3x above)
- Version Control / Co-change Novelty: 0.0000 (typical: 1.00, 105.3x below)
- CI / Build / Build Duration: 3,637.0 (typical: 33.50, 74.8x above)
- Version Control / Files Changed: 237 (typical: 5.00, 52.2x above)
- Dependencies / Total Dependencies: 1,493 (typical: 1,448.0, 30.4x above)
- Version Control / Change Locality: 1.00 (typical: 0.0833, 7.4x above)
- Version Control / Change Dispersion: 2.00 (typical: 0.8648, 5.4x above)

RISK PATTERNS (actionable only):

- [Action Required] 3 patterns:
    * when deployments and code changes happen together, novelty of file pairings tends to move together.
    * when CI builds and code changes happen together, novelty of file pairings and build time tend to move together.
    * when CI builds and code changes happen together, novelty of file pairings tends to move together.
  Impact: Files that don't normally change together are being modified in the same commits. This indicates novel, untested interactions that may introduce bugs. Escalated from Needs Attention — multiple correlated patterns converge on the same signal families.
  Action: Investigate which files are being combined unexpectedly. Prioritize testing these changes.

- [Action Required] when deployments and code changes happen together, change focus and release frequency tend to move together.
  Impact: Time between releases is increasing. This could indicate a bottleneck in the release process or accumulating risk in larger releases. Escalated from Worth Monitoring — multiple correlated patterns converge on the same signal families.
  Action: Check if process changes or staffing issues are delaying releases.

- [Action Required] when CI builds and code changes happen together, change focus and build time tend to move together.
  (2 independent confirmations)
  Impact: Builds are taking longer. Slower CI feedback loops reduce developer productivity and delay catching issues. Escalated from Worth Monitoring — multiple correlated patterns converge on the same signal families.
  Action: Profile the build pipeline to identify bottlenecks. Check for newly added expensive tests or build steps.

- [Action Required] 4 patterns:
    * when deployments and code changes happen together, code spread and release frequency tend to move together.
    * when CI builds and code changes happen together, code spread and build time tend to move together.
    * when deployments and code changes happen together, code spread tends to move together.
    * when CI builds and code changes happen together, code spread tends to move together.
  Impact: Changes are spreading across unrelated parts of the codebase. This makes reviews harder and increases the chance of unexpected side effects. Escalated from Worth Monitoring — multiple correlated patterns converge on the same signal families.
  Action: Review recent PRs for scope creep. Consider breaking large changes into focused commits.

- [Action Required] 4 patterns:
    * when deployments and code changes happen together, file count tends to move together.
    * when CI builds and code changes happen together, file count and build time tend to move together.
    * when deployments and code changes happen together, file count and release frequency tend to move together.
    * when CI builds and code changes happen together, file count tends to move together.
  Impact: Commits are touching more files than usual, increasing review burden and risk of regressions. Escalated from Worth Monitoring — multiple correlated patterns converge on the same signal families.
  Action: Monitor PR sizes. If this persists, investigate whether large refactors need better decomposition.

- [Action Required] when CI builds and code changes happen together, change focus tends to move in opposite directions.
  Impact: Changes span files that don't normally change together, suggesting cross-cutting concerns that may be harder to test. Escalated from Worth Monitoring — multiple correlated patterns converge on the same signal families.
  Action: Review whether these cross-cutting changes have adequate test coverage.

- [Worth Monitoring] when dependency changes and deployments happen together, dependency count and release frequency tend to move together.
  (2 independent confirmations)
  Impact: The dependency count is growing, expanding the supply-chain attack surface and potential for version conflicts.
  Action: Audit new dependencies for necessity, maintenance status, and known vulnerabilities.

- [Worth Monitoring] when dependency changes and code changes happen together, change focus tends to move in opposite directions.
  Impact: Changes span files that don't normally change together, suggesting cross-cutting concerns that may be harder to test.
  Action: Review whether these cross-cutting changes have adequate test coverage.

- [Worth Monitoring] when dependency changes and code changes happen together, code spread tends to move together.
  Impact: Changes are spreading across unrelated parts of the codebase. This makes reviews harder and increases the chance of unexpected side effects.
  Action: Review recent PRs for scope creep. Consider breaking large changes into focused commits.

- [Worth Monitoring] when code changes occur, file count tends to increase.
  Impact: Commits are touching more files than usual, increasing review burden and risk of regressions.
  Action: Monitor PR sizes. If this persists, investigate whether large refactors need better decomposition.


COMMITS (20):

  e574ef3e — chore(deps): bump the workerd-and-workers-types group with 2 updates (#11844) (5 files)
  bf97065e — refactor handling of Node built-in modules (#11845) (3 files)
  10aa2f98 — feat: update CI workflow for other Node versions (#11833) (1 files)
  5e89bd16 — refactor: consistenly import expect from vitest (#11851) (36 files)
  0f8d69d3 — containers: users can set multiple tiers for constraints (#11755) (9 files)
  b6148ed7 — chore(deps): bump the workerd-and-workers-types group with 2 updates (#11872) (5 files)
  2203af44 — Add Node.js 24 and 25 compatibility to the test suites for Miniflare, Wrangler,  (10 files)
  b0e54b26 — [wrangler] Add AI agent detection to analytics events (#11820) (7 files)
  8ceea62e — fix(miniflare): fix flaky Durable Object eviction tests on Windows (#11874) (1 files)
  fe3e9552 — [C3] Bump create-vue from 3.18.3 to 3.18.5 in /packages/create-cloudflare/src/fr (2 files)
  ... and 10 more

SOURCE FILES CHANGED (50):

  - .changeset/dependabot-update-11844.md (modified)
  - packages/miniflare/package.json (modified)
  - packages/wrangler/package.json (modified)
  - pnpm-lock.yaml (modified)
  - pnpm-workspace.yaml (modified)
  - .changeset/purple-eggs-relate.md (modified)
  - packages/unenv-preset/src/index.ts (modified)
  - packages/vite-plugin-cloudflare/src/plugins/nodejs-compat.ts (modified)
  - .github/workflows/test-and-check-other-node.yml (modified)
  - fixtures/d1-read-replication-app/tests/index.test.ts (modified)
  - fixtures/durable-objects-app/tests/index.test.ts (modified)
  - fixtures/node-app-pages/tests/index.test.ts (modified)
  - fixtures/node-env/tests/node-env.test.ts (modified)
  - fixtures/nodejs-als-app/tests/index.test.ts (modified)
  - fixtures/pages-d1-shim/tests/index.test.ts (modified)
  - fixtures/pages-functions-app/tests/index.test.ts (modified)
  - fixtures/pages-functions-unenv-alias/tests/index.test.ts (modified)
  - fixtures/pages-functions-wasm-app/tests/index.test.ts (modified)
  - fixtures/pages-functions-with-config-file-app/tests/index.test.ts (modified)
  - fixtures/pages-functions-with-routes-app/tests/index.test.ts (modified)
  ... and 30 more

TASKS:

1. ROOT CAUSE: For each deviation, identify the commit(s) that caused it.
   Focus on [Action Required] and [Needs Attention] items first.

2. FIXES: Provide concrete fixes with file paths and code changes.
   Goal: bring metrics back toward baseline without disrupting velocity.

3. PRIORITY: Rank fixes by urgency (immediate vs. next sprint).

4. AFTER FIXING: Run `evo analyze . --verify` to confirm deviations decreased.
   If a change was intentional, accept it: `evo accept . <N>`.

5. FINDING SUMMARIES: At the end, include a section like this:
   ## Finding Summaries
   - [family/metric]: One plain-English sentence for a non-technical reader.
   (This lets the user run `evo enrich . --from response.txt` to store friendly descriptions.)

Executive Summary

What EE Can See

Key Findings

What Changed in Your Codebase

Next Steps

Investigation Prompt

Expand Your Coverage

Available Adapters

How to Connect an Adapter