## Summary

**{One-sentence TL;DR: this PR &lt;verb&gt; &lt;behavior&gt; so that &lt;why&gt;.}**

{2-4 bullets covering: what changed in user-visible or runtime behavior, what scope is affected, and what a reviewer should pay extra attention to. Include specific config values, flag names (with a brief definition on first use), and migration phases when present. Do not list files here.}

### Behavior changes

{Plain-language description of before vs after. When multiple flags or modes interact, render as a small table. Name internal flags or services on first use. Omit this subsection entirely for pure refactors and docs-only PRs.}

## What to look at first

- {Pointer to a decision, tradeoff, or risk the reviewer should weight. 2-4 bullets max. This is not a file list — it is a "here is where the interesting decisions live" guide.}

## How this was tested

- ✅ {Scenario the author already verified, past tense.}

## Files of interest

- `{path}` — {one phrase about why this file matters for review}

## Test scenario changes

- {Behavioral scenario described in plain language, e.g., "Covers the case where the feature flag is on but the user is unauthenticated."}
