V4.1.0 - Bounds channel & scroll re-render fix

js.foresight v4.1.0

• New: element geometry moved to a dedicated bounds channel -> ForesightRegisterResult now has getBounds() and subscribeToBounds() for position/size updates (fired on every scroll/resize tick while visible) (#120)
• Changed: subscribe()/getSnapshot() now only fire/change on logical state changes, never on scroll/resize —> state snapshots are referentially stable while scrolling (#120)
• Breaking-ish: ForesightElementState.elementBounds removed; hitSlop now lives directly on the state snapshot; new exported ElementBounds type (#120)

js.foresight-devtools v2.1.0

• Performance: log tab rewritten around a dedicated log store, element tab render optimizations, cheaper/batched overlay updates (#119)
• Element overlays read geometry from the new core bounds channel (#120)

@foresightjs/react v0.2.0

• Performance: useForesights coalesces store notifications to one snapshot check per microtask instead of one per element per scroll tick (#120)
• Components no longer re-render on scroll/resize —> only on logical state changes, thanks to the core bounds split (#120)

@foresightjs/vue v0.2.0

• No functional changes; peer dependency bumped to js.foresight ^4.1.0