| 1 | <!-- |
| 2 | Read CONTRIBUTING.md before opening a PR. Review capacity is limited, and meeting |
| 3 | the requirements does not guarantee review or merging. Solve one underlying problem. |
| 4 | The same requirements apply to drafts. Draft status does not defer triage or closure. |
| 5 | Use a conventional commit title in plain language, such as "fix(web): new threads no longer spike CPU". |
| 6 | --> |
| 7 | |
| 8 | ## Problem |
| 9 | |
| 10 | <!-- Explain the problem in a sentence or two. Include expected behavior and |
| 11 | reproduction steps or environment where relevant. --> |
| 12 | |
| 13 | ## Change |
| 14 | |
| 15 | <!-- Explain how this fixes the problem. If it spans components or clients, |
| 16 | explain why those changes are needed for the same fix. Split independent fixes. --> |
| 17 | |
| 18 | ## Scope and approval |
| 19 | |
| 20 | <!-- Link the triaged bug issue or the discussion with explicit maintainer approval |
| 21 | of direction and scope, including the approval comment. For a very small, focused |
| 22 | fix of an obvious bug, explain why it qualifies without a prior issue or discussion. |
| 23 | For focused configuration of an established capability, explain what already exists, |
| 24 | what the option controls, and why its effects stay within that capability. Adding a |
| 25 | setting alone is not a new feature or an approval exemption; broader workflow or |
| 26 | behavior changes still need approval. Scope and verification requirements still apply. |
| 27 | There is no line-count or file-count cutoff. --> |
| 28 | |
| 29 | ## Verification |
| 30 | |
| 31 | <!-- Describe the focused tests or manual checks you ran and the observed results |
| 32 | for the changed behavior. State anything you could not check. "Tests pass" alone |
| 33 | is insufficient; broad repo-wide checks are not required. |
| 34 | |
| 35 | For UI changes, include clear before/after screenshots. Include a short recording |
| 36 | when motion, timing, transitions, or interaction details are needed to demonstrate |
| 37 | the change. Upload evidence to GitHub and embed or link it here. Never commit PR-only assets. --> |
| 38 | |
| 39 | <!-- If you used an agent, end with the model and harness that did the work. --> |