CLOSED 2026-09-23 (claude-code, 075ddc4): Html web part dedents a Body before Markdown (9e12113).
CORRECTED 2026-09-22, and the correction is the useful part. This row originally read "an Html web part renders its HTML as escaped source" and called it a pre-existing renderer defect. That was wrong. WebPart Type=Html takes MARKDOWN - HtmlWebPartInvoker runs the body through IMarkdownRenderer and Page.xslt emits the result raw with disable-output-escaping. The body I wrote was HTML indented fourteen spaces inside CDATA, and an indented line in Markdown is a CODE BLOCK, so the renderer did precisely the right thing with what it was given. The Hub's own home page carries the identical authoring error, which is why it looked like a platform defect rather than two people making the same mistake. WHAT IS ACTUALLY WRONG is the NAME. A web part called Html that accepts Markdown and silently renders indented content as source will keep catching every author who reads the name and believes it. Rename the type to Markdown and keep Html as an accepted alias so no existing declaration breaks, or teach the invoker to detect a body that starts with an HTML tag and pass it through unrendered. The first is more honest and is the SharePoint instinct - a Content Editor web part takes markup and says so. THIS ROW IS ALSO THE PROOF THAT SPF.24 IS FIXED: correcting it required the seed applier to be able to UPDATE a row rather than only create one, which is exactly the defect SPF.24 describes, and it was fixed in the same cycle in order to make this correction possible.