componentDidUpdate is not called on initial mount — only componentDidMount is. This means onClear is never called when:

1. Switching compositions: the old (errored) boundary unmounts without clearing the error (no componentWillUnmount handler), and the new boundary's first render triggers componentDidMount, not componentDidUpdate. The stale error persists in Editor's state until the new boundary happens to re-render.
2. HMR recovery: React Fast Refresh remounts error boundaries in an error state, creating a fresh instance. Same issue — componentDidMount fires, not componentDidUpdate.

In practice the gap may be very short (the next child re-render triggers componentDidUpdate → onClear), but the error overlay will flash briefly in the canvas between mount and the first update.

Fix: also call onClear in componentDidMount.

componentDidMount(): void {
	if (!this.state.hasError) {
		this.props.onClear();
	}
}

This is cheap (it's a no-op setRenderError(null) when there's no error) and closes the gap.

Calling onClear on every update when hasError is false (not just the error→clear transition) is noisy — every prop/child re-render triggers it. It's technically harmless since setRenderError(null) bails out when already null, but the previous prevState.hasError && !this.state.hasError check was more precise. Was there a specific reason for broadening this? If it was to handle the HMR recovery case, componentDidMount (see above) would be a more targeted fix.