Explain changes

Produce a detailed written explanation of everything on this branch, as an HTML page, and open it.

The page has one job: let the reader understand the change well enough to review it. Those two things are not separate. Nobody can review code they do not understand, and explaining code properly is what surfaces the problems in it.

So write the explanation, and when writing it reveals something wrong, say so. You cannot write "this is correct because the guard above catches the null case" without going to look at whether that guard exists. When it does not, you have found a real bug, and it came from understanding rather than from a checklist. If you cannot explain why a line is correct, that inability is itself the finding.

Do not fix anything and do not approve anything. Do not run a systematic bug hunt over the diff either; that is a separate task with its own checklists. Explain the change, and report what the explaining turned up.

Scope

Everything on this branch that is not in the default branch, committed and uncommitted: