Explain the problem and the focused changes that address it.
Describe the resulting behavior, including before/after examples when useful.
List checks actually performed and their results. Report failures, skipped checks, and unperformed checks with reasons. Choose checks appropriate to the changed files and existing repository tooling; documentation-only changes do not require runtime or device tests.
Link the source Issue and any related Issues. Use Closes #... only when this PR fully addresses that Issue; describe any intentional partial scope.
List genuinely required post-merge checks separately, marked pending until performed, or state that none are required. Do not claim deployment or publication succeeded based on pre-merge validation.