sbuilder-document-model

Many document writes fail silently: the save and publish succeed while the page is wrong. Common causes include bindings outside the specials namespace, stuck styles with no pinned host, and state writes landing in a path nothing reads. This Skill catalogs each measured case and its guard.

Satellites are nodes attached to their owner by parent alone via a config key, deliberately absent from the owner's data.nodes — for example list-empty, quantity-button, and product-variant-label. Walks of child lists miss them, so validation checks attachment rather than reachability.

A plain image inside a repeater reads specials.src from the document, so every card gets one picture. Only elements whose renderer reads a bound special can show a record; sb_review reports the mistake as static_in_dataset with the element swap as the fix.

No. Historically it skipped overlays and never walked satellites, so drawer content and element chrome were invisible to it. It also reads one page at a time, so site-wide issues like per-page headers instead of global sections require the siteChrome readiness check.

Edit nodes inside the composed master with sb_set on the page; overlay and global content is written through the page save, not the overlays API. Saves carry expectRev fencing, and PageSession.save re-stamps revisions so later edits in the session are not dropped.

A refused write once left its patches in the draft, and the next successful save committed them. applyAndSave now refuses before applying whenever the write would leave the page unstorable, while a write that repairs inherited damage still passes.