max / quasi

Place a residual's spans where an emission could have placed them A guard's markup is located by diffing the full render against one with that guard off, and when what is deleted shares a boundary with what follows it, several placements rebuild the render exactly. `placed` took the latest and repaired only the ones that straddled a neighbour. That covers the pair that overlaps and misses the one that does not: a span read late but landing clear of everything else is a tree, and it is the wrong tree, so nothing refuses it. MNW's /c/{username}/{slug} is the site. A guarded description paragraph and an unguarded item count both render as <p class="text"> around a value, so the span was read 16 bytes late, into the second paragraph's sentinel. Nothing straddled it, the residual built, and the served page carried ZQH00000003HQZ where the description belonged. What tells the placements apart is what an emission can place. A guard places an emission and a loop places a body, so the run is a whole element or a run of them: a placement starting inside a tag, closing an element it did not open, or cutting a sentinel in half is markup no emission produced, however exactly it rebuilds the render. `placeable` takes the latest placement that is none of those, and the straddle repair runs after it on what is left. Exact on both known sites: /fan-plus's two guarded siblings, 22 bytes late into the next <section id=">, and this one. Only ever narrows the choices, so a genuine overlap still reaches `build`'s assertion.