@octanejs/mcp-server 0.2.25 → 0.2.27

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@octanejs/mcp-server",
-  "version": "0.2.25",
+  "version": "0.2.27",
   "type": "module",
   "engines": {
     "node": ">=22.22.2"

package/skills/react-divergences.md

@@ -32,6 +32,40 @@ recompute after every render.
 (`[state, update, getState]`) that reads the latest scheduled hook-cell value.
 Ordinary two-item destructures keep the allocation-free React shape.
 
+## Strong mode reads render snapshots
+
+In a module with `"use strong"` or application-wide Strong enabled, reading a
+`useRef` object's `current` while rendering is a compiler error
+(`OCTANE_STRONG_RENDER_REF_READ`). Calling a known third-tuple state getter
+while rendering is also an error (`OCTANE_STRONG_RENDER_STATE_GETTER_CALL`): it
+can read scheduled state that differs from the render snapshot. Reading a
+reassigned module-scope `let` or `var` during render is an error too
+(`OCTANE_STRONG_RENDER_MODULE_STATE_READ`), since the variable can change
+without a witnessed render input. Pass the ref directly to a `ref` prop and
+render from the state tuple's first member. Move changing module values into
+state or context, or pass an immutable snapshot as a prop. Read the ref or call
+the getter in an event, effect, or deferred callback.
+Compatibility modules keep their existing behavior.
+
+Reading unshadowed `window`, `document`, `localStorage`, `sessionStorage`,
+`navigator`, `location`, or `matchMedia` while rendering reports
+`OCTANE_STRONG_RENDER_AMBIENT_READ`. This includes `typeof` guards, constant
+browser handle aliases, and `globalThis` property reads except known standard
+language builtins. Computed `globalThis` properties whose names are unknown also
+report the error. Local shadowing, scalar module snapshots, the `globalThis`
+object itself, and standard language builtins such as `globalThis.JSON` remain valid.
+The analysis does not generally prove aliases obtained through defaults,
+returned values, containers, arbitrary deeper properties, or imports. Those
+values still have to satisfy the render-snapshot contract.
+
+Use `useSyncExternalStore` with a server snapshot for changing browser state;
+browser reads inside its snapshot callbacks remain legal. Events, effects,
+deferred callbacks, and lazy `useState` or `useReducer` initializers may also
+read browser state. Lazy initialization still runs during server rendering:
+guard unavailable browser APIs there and ensure server and client initial
+output agrees. A guard in an ordinary render calculation still reads ambient
+state and is rejected.
+
 ## Controlled inputs match React — on native events
 
 Controlled `value`/`checked` follow React's semantics exactly: the prop drives

package/src/index.js

@@ -108,6 +108,12 @@ export const BENCHMARK_SUITES = [
 	'universal-leaf-update',
 	'universal-object-teardown',
 	'universal-template-events',
+	'universal-native-hover',
+	'universal-owner-drafts',
+	'universal-hook-slot',
+	'universal-draft-lookup',
+	'scoped-descriptor-shapes',
+	'memo-wrapper-shapes',
 	'universal-external-store',
 	'lynx-render',
 	'lynx-table',