Updates and Redraw

Status: implemented Core model.

Sercrod requests redraw through Custom Elements lifecycle handling, whole data assignment, directives, event handlers, *update, or explicit update(). Directly mutating a nested JavaScript object is not a general redraw trigger.

sercrod-change can notify code of an observed change; it is not the render scheduler. This is not Proxy- or MutationObserver-based general change detection. *input writes a control value; *lazy changes refresh timing without discarding it; *eager is the explicit live-refresh form.

Timing-mode boundary

Choose one timing mode deliberately. Do not combine *lazy and *eager as an application contract: their interaction is not a documented portable behavior.

Evidence

Status: implemented.

Evidence: docs/spec/runtime.md Sections 1, 4, 9, 10, and 17, dist/sercrod.js, and canonical manual dist/man.json.