@oriro/orirocli 0.1.11 → 0.3.1

package/skills/craft/vercel-optimize/references/support-topics/astro-output-mode-and-isr.md

@@ -1,31 +1,31 @@
----
-id: astro-output-mode-and-isr
-title: Astro output mode and ISR
-status: active
-candidateKinds: ["uncached_route", "rendering_candidate"]
-frameworks: ["astro@*"]
-priority: 90
-citations:
-  [
-    "https://vercel.com/docs/frameworks/frontend/astro",
-    "https://docs.astro.build/en/guides/on-demand-rendering/",
-    "https://docs.astro.build/en/reference/configuration-reference/",
-  ]
-maxBriefChars: 850
----
-
-## Investigation Brief
-
-Astro defaults to static output; `server` output makes pages render on demand unless route-level prerendering changes that. First decide whether the hot route truly needs SSR.
-
-## Evidence To Check
-
-Inspect `astro.config`, adapter options, `output`, route-level `prerender`, dynamic params, middleware, and whether the content is shared across visitors. Compare route cache result and request volume.
-
-## Do Not Recommend When
-
-Do not prerender or cache personalized, preview, cart, checkout, or auth-gated pages. Do not change output mode for the whole app when one route-level flag is enough.
-
-## Verification
-
-Name the Astro output mode, route-level prerender state, observed route signal, and exact config or page line.
+---
+id: astro-output-mode-and-isr
+title: Astro output mode and ISR
+status: active
+candidateKinds: ["uncached_route", "rendering_candidate"]
+frameworks: ["astro@*"]
+priority: 90
+citations:
+  [
+    "https://vercel.com/docs/frameworks/frontend/astro",
+    "https://docs.astro.build/en/guides/on-demand-rendering/",
+    "https://docs.astro.build/en/reference/configuration-reference/",
+  ]
+maxBriefChars: 850
+---
+
+## Investigation Brief
+
+Astro defaults to static output; `server` output makes pages render on demand unless route-level prerendering changes that. First decide whether the hot route truly needs SSR.
+
+## Evidence To Check
+
+Inspect `astro.config`, adapter options, `output`, route-level `prerender`, dynamic params, middleware, and whether the content is shared across visitors. Compare route cache result and request volume.
+
+## Do Not Recommend When
+
+Do not prerender or cache personalized, preview, cart, checkout, or auth-gated pages. Do not change output mode for the whole app when one route-level flag is enough.
+
+## Verification
+
+Name the Astro output mode, route-level prerender state, observed route signal, and exact config or page line.

package/skills/craft/vercel-optimize/references/support-topics/auth-preserving-parallelization.md

@@ -1,30 +1,30 @@
----
-id: auth-preserving-parallelization
-title: Authorization-preserving parallelization
-status: active
-candidateKinds: ["slow_route"]
-frameworks: ["*"]
-priority: 90
-citations:
-  [
-    "vercel-react-best-practices:async-parallel",
-    "vercel-react-best-practices:server-parallel-fetching",
-  ]
-maxBriefChars: 900
----
-
-## Investigation Brief
-
-Parallelizing awaits is safe only when it does not move private data access ahead of the auth, ownership, tenant, or permission check protecting that data.
-
-## Evidence To Check
-
-List every awaited operation being reordered. If a private lookup currently runs after `getSession()`, an ownership query, a tenant check, or a redirect guard, prove the lookup itself enforces the same predicate before recommending `Promise.all`.
-
-## Do Not Recommend When
-
-Do not parallelize a private record fetch with the ownership check that authorizes that fetch. Instead, recommend combining the guard and data lookup into one query constrained by the authenticated user, tenant, or ownership key.
-
-## Verification
-
-The fix must preserve the sequential guard or replace it with a single authorized query. Do not promise a latency drop equal to a helper unless that helper duration was measured.
+---
+id: auth-preserving-parallelization
+title: Authorization-preserving parallelization
+status: active
+candidateKinds: ["slow_route"]
+frameworks: ["*"]
+priority: 90
+citations:
+  [
+    "vercel-react-best-practices:async-parallel",
+    "vercel-react-best-practices:server-parallel-fetching",
+  ]
+maxBriefChars: 900
+---
+
+## Investigation Brief
+
+Parallelizing awaits is safe only when it does not move private data access ahead of the auth, ownership, tenant, or permission check protecting that data.
+
+## Evidence To Check
+
+List every awaited operation being reordered. If a private lookup currently runs after `getSession()`, an ownership query, a tenant check, or a redirect guard, prove the lookup itself enforces the same predicate before recommending `Promise.all`.
+
+## Do Not Recommend When
+
+Do not parallelize a private record fetch with the ownership check that authorizes that fetch. Instead, recommend combining the guard and data lookup into one query constrained by the authenticated user, tenant, or ownership key.
+
+## Verification
+
+The fix must preserve the sequential guard or replace it with a single authorized query. Do not promise a latency drop equal to a helper unless that helper duration was measured.

package/skills/craft/vercel-optimize/references/support-topics/bot-protection-product-guardrails.md

@@ -1,32 +1,32 @@
----
-id: bot-protection-product-guardrails
-title: Bot Protection product guardrails
-status: active
-candidateKinds: ["platform_bot_protection"]
-frameworks: ["*"]
-priority: 90
-citations:
-  [
-    "https://vercel.com/docs/bot-management",
-    "https://vercel.com/docs/vercel-firewall/vercel-waf/managed-rulesets",
-    "https://vercel.com/docs/vercel-firewall/vercel-waf/custom-rules",
-    "https://vercel.com/docs/botid",
-  ]
-maxBriefChars: 800
----
-
-## Investigation Brief
-
-Bot Protection recommendations must be grounded in observed automated traffic or meaningful edge-request scale.
-
-## Evidence To Check
-
-Check bot bandwidth share, edge request volume, existing WAF managed rules, and whether BotID or Bot Protection is already enabled. Prefer a staged Log to Challenge or Deny path for rules whose false-positive risk is not proven.
-
-## Do Not Recommend When
-
-Do not recommend disabling Vercel security products to reduce cost. Do not recommend Bot Protection for quiet projects with no bot evidence.
-
-## Verification
-
-State the observed bot share or scale signal, current protection state, and any existing log, challenge, deny, or BotID check.
+---
+id: bot-protection-product-guardrails
+title: Bot Protection product guardrails
+status: active
+candidateKinds: ["platform_bot_protection"]
+frameworks: ["*"]
+priority: 90
+citations:
+  [
+    "https://vercel.com/docs/bot-management",
+    "https://vercel.com/docs/vercel-firewall/vercel-waf/managed-rulesets",
+    "https://vercel.com/docs/vercel-firewall/vercel-waf/custom-rules",
+    "https://vercel.com/docs/botid",
+  ]
+maxBriefChars: 800
+---
+
+## Investigation Brief
+
+Bot Protection recommendations must be grounded in observed automated traffic or meaningful edge-request scale.
+
+## Evidence To Check
+
+Check bot bandwidth share, edge request volume, existing WAF managed rules, and whether BotID or Bot Protection is already enabled. Prefer a staged Log to Challenge or Deny path for rules whose false-positive risk is not proven.
+
+## Do Not Recommend When
+
+Do not recommend disabling Vercel security products to reduce cost. Do not recommend Bot Protection for quiet projects with no bot evidence.
+
+## Verification
+
+State the observed bot share or scale signal, current protection state, and any existing log, challenge, deny, or BotID check.

package/skills/craft/vercel-optimize/references/support-topics/build-minutes-monorepo-fanout.md

@@ -1,32 +1,32 @@
----
-id: build-minutes-monorepo-fanout
-title: Build Minutes monorepo fanout
-status: active
-candidateKinds: ["build_minutes_fanout"]
-frameworks: ["*"]
-scannerPatterns: ["turbo-force-bypass"]
-priority: 90
-citations:
-  [
-    "https://vercel.com/docs/monorepos",
-    "https://vercel.com/docs/builds",
-    "https://turborepo.dev/docs/crafting-your-repository/caching",
-  ]
-maxBriefChars: 900
----
-
-## Investigation Brief
-
-Build Minutes climbs when commits rebuild unchanged work. Common causes: `TURBO_FORCE`, `cache: false`, missing outputs, or disabled build-skip settings.
-
-## Evidence To Check
-
-Confirm Build Minutes share and scanner subtype. Inspect `package.json`, `turbo.json`, outputs, `.gitignore`, `vercel.json`, and project settings. If `build` runs migrations, split them into an uncached step before recommending Turbo build caching.
-
-## Do Not Recommend When
-
-Skip under 5% bill share with no scanner finding. Skip single-project repos and intentional CI-only force flags. Do not recommend `ignoreCommand` from repo grep alone; dashboard-only skip-unaffected may be better.
-
-## Verification
-
-Name the offending file and pattern. Recommend only the verified fix: cache a pure build task, add generated `outputs`, enable skip-unaffected builds, or add `ignoreCommand` only when needed.
+---
+id: build-minutes-monorepo-fanout
+title: Build Minutes monorepo fanout
+status: active
+candidateKinds: ["build_minutes_fanout"]
+frameworks: ["*"]
+scannerPatterns: ["turbo-force-bypass"]
+priority: 90
+citations:
+  [
+    "https://vercel.com/docs/monorepos",
+    "https://vercel.com/docs/builds",
+    "https://turborepo.dev/docs/crafting-your-repository/caching",
+  ]
+maxBriefChars: 900
+---
+
+## Investigation Brief
+
+Build Minutes climbs when commits rebuild unchanged work. Common causes: `TURBO_FORCE`, `cache: false`, missing outputs, or disabled build-skip settings.
+
+## Evidence To Check
+
+Confirm Build Minutes share and scanner subtype. Inspect `package.json`, `turbo.json`, outputs, `.gitignore`, `vercel.json`, and project settings. If `build` runs migrations, split them into an uncached step before recommending Turbo build caching.
+
+## Do Not Recommend When
+
+Skip under 5% bill share with no scanner finding. Skip single-project repos and intentional CI-only force flags. Do not recommend `ignoreCommand` from repo grep alone; dashboard-only skip-unaffected may be better.
+
+## Verification
+
+Name the offending file and pattern. Recommend only the verified fix: cache a pure build task, add generated `outputs`, enable skip-unaffected builds, or add `ignoreCommand` only when needed.

package/skills/craft/vercel-optimize/references/support-topics/cache-components-static-shell-boundaries.md

@@ -1,31 +1,31 @@
----
-id: cache-components-static-shell-boundaries
-title: Cache Components static shell boundaries
-status: active
-candidateKinds: ["rendering_candidate"]
-frameworks: ["next@>=16.0.0"]
-priority: 94
-citations:
-  [
-    "https://nextjs.org/docs/app/api-reference/config/next-config-js/cacheComponents",
-    "https://nextjs.org/docs/app/getting-started/caching",
-    "https://nextjs.org/docs/app/guides/migrating-to-cache-components",
-  ]
-maxBriefChars: 900
----
-
-## Investigation Brief
-
-On Next.js 16 with Cache Components, avoid older segment-config advice. The right question is whether the route can keep a static shell while dynamic data moves behind explicit cached or runtime boundaries.
-
-## Evidence To Check
-
-Check `cacheComponents`, `use cache`, `cacheLife`, request-time APIs, Suspense boundaries, and scanner evidence such as `force-dynamic` or `headers-in-page`.
-
-## Do Not Recommend When
-
-Do not suggest `dynamic`, `revalidate`, or `fetchCache` as the primary fix when Cache Components is enabled. Do not cache request-personalized content.
-
-## Verification
-
-Name the Next.js version, Cache Components state, dynamic trigger, and the exact boundary or directive that can change.
+---
+id: cache-components-static-shell-boundaries
+title: Cache Components static shell boundaries
+status: active
+candidateKinds: ["rendering_candidate"]
+frameworks: ["next@>=16.0.0"]
+priority: 94
+citations:
+  [
+    "https://nextjs.org/docs/app/api-reference/config/next-config-js/cacheComponents",
+    "https://nextjs.org/docs/app/getting-started/caching",
+    "https://nextjs.org/docs/app/guides/migrating-to-cache-components",
+  ]
+maxBriefChars: 900
+---
+
+## Investigation Brief
+
+On Next.js 16 with Cache Components, avoid older segment-config advice. The right question is whether the route can keep a static shell while dynamic data moves behind explicit cached or runtime boundaries.
+
+## Evidence To Check
+
+Check `cacheComponents`, `use cache`, `cacheLife`, request-time APIs, Suspense boundaries, and scanner evidence such as `force-dynamic` or `headers-in-page`.
+
+## Do Not Recommend When
+
+Do not suggest `dynamic`, `revalidate`, or `fetchCache` as the primary fix when Cache Components is enabled. Do not cache request-personalized content.
+
+## Verification
+
+Name the Next.js version, Cache Components state, dynamic trigger, and the exact boundary or directive that can change.

package/skills/craft/vercel-optimize/references/support-topics/cache-components-suspense-dedupe-pitfall.md

@@ -1,32 +1,32 @@
----
-id: cache-components-suspense-dedupe-pitfall
-title: Cache Components Suspense dedupe pitfall
-status: active
-candidateKinds: ["cache_components_suspense_dedupe"]
-frameworks: ["next@>=16.0.0"]
-scannerPatterns: ["cache-components-suspense-dedupe"]
-priority: 87
-citations:
-  [
-    "https://nextjs.org/docs/app/api-reference/directives/use-cache",
-    "https://nextjs.org/docs/app/api-reference/config/next-config-js/cacheComponents",
-    "https://nextjs.org/docs/app/guides/migrating-to-cache-components",
-  ]
-maxBriefChars: 900
----
-
-## Investigation Brief
-
-Default `'use cache'` does not dedupe identical calls across separate `<Suspense>` boundaries on the same render. Each boundary re-invokes the cached function, multiplying function-duration and ISR write churn.
-
-## Evidence To Check
-
-Confirm the scanner finding's repeated fetch URL or helper name. Verify the call sites are within the same route segment and inside distinct `<Suspense>` boundaries. Cross-reference `fnDurationP95ByRoute` and `isrWritesByRoute` for the owning route.
-
-## Do Not Recommend When
-
-Skip if the repeated call is intentional (different parameters, different intent). Skip if the duplicate is in a single component body where in-request memoization already applies.
-
-## Verification
-
-Name the duplicated call, count, and either: (a) the page-level promise to hoist or (b) the function to move to `'use cache: remote'`.
+---
+id: cache-components-suspense-dedupe-pitfall
+title: Cache Components Suspense dedupe pitfall
+status: active
+candidateKinds: ["cache_components_suspense_dedupe"]
+frameworks: ["next@>=16.0.0"]
+scannerPatterns: ["cache-components-suspense-dedupe"]
+priority: 87
+citations:
+  [
+    "https://nextjs.org/docs/app/api-reference/directives/use-cache",
+    "https://nextjs.org/docs/app/api-reference/config/next-config-js/cacheComponents",
+    "https://nextjs.org/docs/app/guides/migrating-to-cache-components",
+  ]
+maxBriefChars: 900
+---
+
+## Investigation Brief
+
+Default `'use cache'` does not dedupe identical calls across separate `<Suspense>` boundaries on the same render. Each boundary re-invokes the cached function, multiplying function-duration and ISR write churn.
+
+## Evidence To Check
+
+Confirm the scanner finding's repeated fetch URL or helper name. Verify the call sites are within the same route segment and inside distinct `<Suspense>` boundaries. Cross-reference `fnDurationP95ByRoute` and `isrWritesByRoute` for the owning route.
+
+## Do Not Recommend When
+
+Skip if the repeated call is intentional (different parameters, different intent). Skip if the duplicate is in a single component body where in-request memoization already applies.
+
+## Verification
+
+Name the duplicated call, count, and either: (a) the page-level promise to hoist or (b) the function to move to `'use cache: remote'`.

package/skills/craft/vercel-optimize/references/support-topics/cdn-cache-auth-safety.md

@@ -1,31 +1,31 @@
----
-id: cdn-cache-auth-safety
-title: CDN cache auth safety
-status: active
-candidateKinds: ["uncached_route", "cache_header_gap"]
-frameworks: ["*"]
-priority: 100
-citations:
-  [
-    "https://vercel.com/docs/caching/cdn-cache",
-    "https://vercel.com/docs/caching/cache-control-headers",
-    "https://vercel.com/docs/project-configuration",
-  ]
-maxBriefChars: 900
----
-
-## Investigation Brief
-
-Treat edge caching as a safety question first. The route must be a public, cacheable GET path before a shared-cache recommendation is allowed.
-
-## Evidence To Check
-
-Use `methodDistribution`, `cacheBreakdown`, and headers. Before `s-maxage`, rule out cookies, sessions, authorization, draft state, and user-specific data.
-
-## Do Not Recommend When
-
-Do not cache mutations, dashboards, account data, request-personalized responses, or routes whose value changes per viewer. Do not mix `private` with shared-cache directives.
-
-## Verification
-
-Name GET share, cache mix, file line, and policy: mechanism, scope, TTL/freshness, and `Vary`. If the right policy is `no-store`, emit no-change/observation.
+---
+id: cdn-cache-auth-safety
+title: CDN cache auth safety
+status: active
+candidateKinds: ["uncached_route", "cache_header_gap"]
+frameworks: ["*"]
+priority: 100
+citations:
+  [
+    "https://vercel.com/docs/caching/cdn-cache",
+    "https://vercel.com/docs/caching/cache-control-headers",
+    "https://vercel.com/docs/project-configuration",
+  ]
+maxBriefChars: 900
+---
+
+## Investigation Brief
+
+Treat edge caching as a safety question first. The route must be a public, cacheable GET path before a shared-cache recommendation is allowed.
+
+## Evidence To Check
+
+Use `methodDistribution`, `cacheBreakdown`, and headers. Before `s-maxage`, rule out cookies, sessions, authorization, draft state, and user-specific data.
+
+## Do Not Recommend When
+
+Do not cache mutations, dashboards, account data, request-personalized responses, or routes whose value changes per viewer. Do not mix `private` with shared-cache directives.
+
+## Verification
+
+Name GET share, cache mix, file line, and policy: mechanism, scope, TTL/freshness, and `Vary`. If the right policy is `no-store`, emit no-change/observation.

package/skills/craft/vercel-optimize/references/support-topics/cold-start-initialization-bundle.md

@@ -1,31 +1,31 @@
----
-id: cold-start-initialization-bundle
-title: Cold-start initialization and bundle weight
-status: active
-candidateKinds: ["cold_start"]
-frameworks: ["*"]
-priority: 92
-citations:
-  [
-    "https://vercel.com/docs/functions/debug-slow-functions",
-    "https://vercel.com/docs/functions/limitations",
-    "https://vercel.com/docs/functions/runtimes",
-  ]
-maxBriefChars: 850
----
-
-## Investigation Brief
-
-Cold-start candidates need a code-path check, not only a project-setting check. First prove whether cold requests are paying for imports, module-scope setup, runtime choice, or dependency weight.
-
-## Evidence To Check
-
-Use `startTypeSplit`, `coldVsWarmLatencyP95`, and `coldByDeployment`. In source, inspect module-scope SDK setup, database/client construction, top-level network calls, heavy dependencies, runtime exports, and deployment-local changes.
-
-## Do Not Recommend When
-
-Do not blame cold starts when warm requests are similarly slow. Do not recommend keep-warm traffic or more memory before proving initialization or runtime pressure.
-
-## Verification
-
-Name the cold-start share, cold-vs-warm gap, and exact initialization, dependency, or runtime line that explains it.
+---
+id: cold-start-initialization-bundle
+title: Cold-start initialization and bundle weight
+status: active
+candidateKinds: ["cold_start"]
+frameworks: ["*"]
+priority: 92
+citations:
+  [
+    "https://vercel.com/docs/functions/debug-slow-functions",
+    "https://vercel.com/docs/functions/limitations",
+    "https://vercel.com/docs/functions/runtimes",
+  ]
+maxBriefChars: 850
+---
+
+## Investigation Brief
+
+Cold-start candidates need a code-path check, not only a project-setting check. First prove whether cold requests are paying for imports, module-scope setup, runtime choice, or dependency weight.
+
+## Evidence To Check
+
+Use `startTypeSplit`, `coldVsWarmLatencyP95`, and `coldByDeployment`. In source, inspect module-scope SDK setup, database/client construction, top-level network calls, heavy dependencies, runtime exports, and deployment-local changes.
+
+## Do Not Recommend When
+
+Do not blame cold starts when warm requests are similarly slow. Do not recommend keep-warm traffic or more memory before proving initialization or runtime pressure.
+
+## Verification
+
+Name the cold-start share, cold-vs-warm gap, and exact initialization, dependency, or runtime line that explains it.

package/skills/craft/vercel-optimize/references/support-topics/core-web-vitals-client-bottlenecks.md

@@ -1,33 +1,33 @@
----
-id: core-web-vitals-client-bottlenecks
-title: Core Web Vitals client bottlenecks
-status: active
-candidateKinds: ["cwv_poor"]
-frameworks: ["*"]
-priority: 90
-citations:
-  [
-    "https://vercel.com/docs/speed-insights",
-    "https://web.dev/articles/vitals",
-    "https://web.dev/articles/optimize-lcp",
-    "https://web.dev/articles/optimize-inp",
-    "https://web.dev/articles/optimize-cls",
-  ]
-maxBriefChars: 850
----
-
-## Investigation Brief
-
-Core Web Vitals candidates need metric-specific investigation. LCP, INP, and CLS usually have different causes and fixes.
-
-## Evidence To Check
-
-Use the poor metric in the deep dive first. For LCP, inspect server response and critical media. For INP, inspect heavy client JavaScript and interaction handlers. For CLS, inspect dimensions, fonts, and injected content.
-
-## Do Not Recommend When
-
-Do not emit a generic “improve Web Vitals” recommendation. Do not optimize a metric that is not poor for this route.
-
-## Verification
-
-Name the poor p75 metric, its value, and the exact source mechanism behind that metric.
+---
+id: core-web-vitals-client-bottlenecks
+title: Core Web Vitals client bottlenecks
+status: active
+candidateKinds: ["cwv_poor"]
+frameworks: ["*"]
+priority: 90
+citations:
+  [
+    "https://vercel.com/docs/speed-insights",
+    "https://web.dev/articles/vitals",
+    "https://web.dev/articles/optimize-lcp",
+    "https://web.dev/articles/optimize-inp",
+    "https://web.dev/articles/optimize-cls",
+  ]
+maxBriefChars: 850
+---
+
+## Investigation Brief
+
+Core Web Vitals candidates need metric-specific investigation. LCP, INP, and CLS usually have different causes and fixes.
+
+## Evidence To Check
+
+Use the poor metric in the deep dive first. For LCP, inspect server response and critical media. For INP, inspect heavy client JavaScript and interaction handlers. For CLS, inspect dimensions, fonts, and injected content.
+
+## Do Not Recommend When
+
+Do not emit a generic “improve Web Vitals” recommendation. Do not optimize a metric that is not poor for this route.
+
+## Verification
+
+Name the poor p75 metric, its value, and the exact source mechanism behind that metric.

package/skills/craft/vercel-optimize/references/support-topics/database-egress-pooling-region.md

@@ -1,32 +1,32 @@
----
-id: database-egress-pooling-region
-title: Database region and connection pressure
-status: active
-candidateKinds: ["slow_route"]
-frameworks: ["*"]
-priority: 60
-citations:
-  [
-    "https://vercel.com/docs/regions",
-    "https://vercel.com/docs/functions",
-    "https://vercel.com/docs/functions/functions-api-reference/vercel-functions-package",
-    "https://vercel.com/docs/functions/limitations",
-  ]
-maxBriefChars: 800
----
-
-## Investigation Brief
-
-Only recommend database or region changes when source and metrics both point to downstream I/O rather than in-process compute.
-
-## Evidence To Check
-
-Compare `cpu.p95` with `latency.p95`, then inspect database awaits, query fan-out, connection creation, pool lifecycle handling, and configured regions in project files.
-
-## Do Not Recommend When
-
-Do not name a database provider, pooling product, or region change unless the repo and project config prove it applies.
-
-## Verification
-
-Tie the finding to the observed wall-clock gap and the exact query, pool, or region configuration line.
+---
+id: database-egress-pooling-region
+title: Database region and connection pressure
+status: active
+candidateKinds: ["slow_route"]
+frameworks: ["*"]
+priority: 60
+citations:
+  [
+    "https://vercel.com/docs/regions",
+    "https://vercel.com/docs/functions",
+    "https://vercel.com/docs/functions/functions-api-reference/vercel-functions-package",
+    "https://vercel.com/docs/functions/limitations",
+  ]
+maxBriefChars: 800
+---
+
+## Investigation Brief
+
+Only recommend database or region changes when source and metrics both point to downstream I/O rather than in-process compute.
+
+## Evidence To Check
+
+Compare `cpu.p95` with `latency.p95`, then inspect database awaits, query fan-out, connection creation, pool lifecycle handling, and configured regions in project files.
+
+## Do Not Recommend When
+
+Do not name a database provider, pooling product, or region change unless the repo and project config prove it applies.
+
+## Verification
+
+Tie the finding to the observed wall-clock gap and the exact query, pool, or region configuration line.