fix(highlighter): clean up stale rough-notation instances on prop changes

[Yeom-JinHo]

Description

This PR fixes the Highlighter bug reported in #836 where changing the annotation color could leave the previous rough-notation markup in the DOM, causing multiple highlights to stack.

The Highlighter lifecycle now cleans up the exact annotation instance created by each render, and the annotation setup runs in a layout effect so stale markup is removed before repaint. The related registry artifacts were also regenerated to keep the published output in sync.

Fixes #836.

Changes

• Switched the Highlighter lifecycle from useEffect to useLayoutEffect.
• Replaced shared ref-based cleanup with effect-local annotation cleanup so each render removes its own rough-notation instance reliably.
• Kept the existing ResizeObserver behavior while binding it only to the current annotation instance.
• Regenerated the registry output files for the updated Highlighter implementation.
• Verified the change with pnpm --filter=www typecheck and pnpm --filter=www build:registry.

Motivation

When the Highlighter color changed, especially during theme updates, the previous annotation was not always cleaned up before a new one was drawn. This resulted in duplicated highlight strokes and inconsistent visual output.

This change makes the cleanup deterministic and prevents stale annotations from remaining in the DOM across prop updates.

Breaking Changes

None.

[vercel]

@Yeom-JinHo is attempting to deploy a commit to the product-studio Team on Vercel.

A member of the Team first needs to authorize it.