@octanejs/cli 0.0.3 → 0.0.5

package/README.md

@@ -19,6 +19,7 @@ pnpm dlx @octanejs/cli doctor
 
 | Command | What it does |
 | --- | --- |
+| `octane create [dir]` | Create an Octane app in a new directory. This is what `npm create octane` runs. |
 | `octane init` | Wire Octane into the project in this directory: bundler plugin, tsconfig, scripts, dependencies. |
 | `octane doctor` | Check the project for the mistakes that break Octane quietly. `--fix` repairs the mechanical ones. |
 | `octane analyze` | Compile the project and report every Octane compiler diagnostic, with its code and suggested edit. |

package/package.json

@@ -1,9 +1,9 @@
 {
   "name": "@octanejs/cli",
-  "version": "0.0.3",
+  "version": "0.0.5",
   "type": "module",
   "engines": {
-    "node": ">=22"
+    "node": ">=22.22.2"
   },
   "description": "The Octane command line: diagnose, configure, and extend an Octane project.",
   "license": "MIT",

package/src/commands/init/index.js

@@ -12,8 +12,12 @@ import {
 	VITE_SCRIPTS,
 	appComponent,
 	clientEntry,
+	counterComponent,
+	globalStyles,
+	healthRoute,
 	indexHtml,
 	integrationFor,
+	layoutComponent,
 	octaneConfig,
 	prettierConfig,
 	tsconfig,
@@ -221,7 +225,7 @@ function plan(project, mode, integration) {
 		if (mode === 'fullstack' && !project.octaneConfigPath) {
 			changes.push({
 				file: 'octane.config.ts',
-				summary: 'create, with one route at /',
+				summary: 'create, with routes for /, /counter, and GET /api/health',
 				apply: writeFile(at('octane.config.ts'), octaneConfig),
 			});
 		}
@@ -262,21 +266,98 @@ function plan(project, mode, integration) {
 			}
 		}
 
-		// fullstack always needs it, because octane.config.ts names it as the
-		// route entry. spa needs it only alongside the entry that imports it, so a
+		// The pages belong to the routes this run declares, so they follow the
+		// octane.config.ts written above and are not written into a project that
+		// brought its own. That config names its own entries, which may not be
+		// these files at all; writing them there produces components nothing
+		// routes to, and a shared layout whose nav links 404 because the routes
+		// behind them were never declared. A missing entry in someone's own config
+		// is a real problem, but it is `octane doctor`'s to report, not this
+		// command's to paper over with a page they did not ask for.
+		const scaffoldsRoutes = mode === 'fullstack' && !project.octaneConfigPath;
+		// spa needs the component only alongside the entry that imports it, so a
 		// project with its own page does not collect an orphan component. That is
 		// the entry this run writes, not the shell: keeping someone's src/main.ts
 		// means keeping whatever it imports, which is not this file.
-		if ((mode === 'fullstack' || writesClientEntry) && !existsSync(at('src/App.tsrx'))) {
-			changes.push({
+		const writesApp = (scaffoldsRoutes || writesClientEntry) && !existsSync(at('src/App.tsrx'));
+		const writesCounter = scaffoldsRoutes && !existsSync(at('src/Counter.tsrx'));
+		// Both fullstack pages import the layout, so it follows whichever of them
+		// this run writes: writing one of those pages without it would scaffold an
+		// app whose own import does not resolve.
+		const writesLayout =
+			mode === 'fullstack' && (writesApp || writesCounter) && !existsSync(at('src/Layout.tsrx'));
+
+		// The components this run scaffolds, in the order the app reads: the entry,
+		// the frame it renders through, then the second page. Collected as a list
+		// rather than pushed one `if` at a time because the stylesheet below is
+		// derived from it — every one of these reads the theme tokens, and a
+		// second enumeration saying which ones do has been wrong every time it was
+		// written. Adding a page here cannot forget to bring the tokens with it.
+		const pages = [];
+		if (writesApp) {
+			pages.push({
 				file: 'src/App.tsrx',
 				summary:
 					mode === 'fullstack'
 						? 'create the route entry referenced by octane.config.ts'
 						: 'create the entry component',
-				apply: writeFile(at('src/App.tsrx'), appComponent),
+				body: appComponent(mode),
+			});
+		}
+		if (writesLayout) {
+			pages.push({
+				file: 'src/Layout.tsrx',
+				summary: 'create the frame both pages share',
+				body: layoutComponent,
+			});
+		}
+		if (writesCounter) {
+			pages.push({
+				file: 'src/Counter.tsrx',
+				summary: 'create the route entry for /counter',
+				body: counterComponent,
+			});
+		}
+		for (const page of pages) {
+			changes.push({
+				file: page.file,
+				summary: page.summary,
+				apply: writeFile(at(page.file), page.body),
 			});
 		}
+
+		// Not a page: it renders nothing and reads no tokens, so it is deliberately
+		// outside the list above.
+		if (scaffoldsRoutes && !existsSync(at('src/server/health.ts'))) {
+			changes.push({
+				file: 'src/server/health.ts',
+				summary: 'create the handler for GET /api/health',
+				apply: writeFile(at('src/server/health.ts'), healthRoute),
+			});
+		}
+		// The reset and theme tokens, which two separate things depend on: the
+		// shell links the file, and every component above reads the tokens in it.
+		// Either one alone is enough to need it, and they do not imply each other —
+		// this command writes pages without a shell when the project has its own
+		// `index.html`, and writes a shell without pages when the project has its
+		// own routing. Tying the stylesheet to just one of them leaves the other
+		// side broken: a page whose every colour, border and surface resolves to
+		// nothing, or a shell linking a file that was never created.
+		if ((writesShell || pages.length > 0) && !existsSync(at('src/styles.css'))) {
+			changes.push({
+				file: 'src/styles.css',
+				summary: 'create the reset and the theme tokens',
+				apply: writeFile(at('src/styles.css'), globalStyles),
+			});
+			// The shell this command writes carries the tag. When the project
+			// brought its own, splicing one into it is the same guesswork as
+			// rewriting their bundler config, so state the line instead.
+			if (!writesShell) {
+				manual.push(
+					'In index.html, add <link rel="stylesheet" href="/src/styles.css" />: the scaffolded pages read their theme tokens from it.',
+				);
+			}
+		}
 	}
 
 	const scripts = project.manifest.scripts ?? {};

package/src/commands/init/templates.js

@@ -83,31 +83,473 @@ export default defineConfig({
 });
 `;
 
-/** One route, naming its export so a typo fails loudly instead of rendering the wrong component. */
-export const octaneConfig = `import { defineConfig, RenderRoute } from "@octanejs/vite-plugin";
+/**
+ * The routes, each naming its export so a typo fails loudly instead of
+ * rendering the wrong component. The health endpoint is a `ServerRoute`: it
+ * returns a `Response` rather than a component, which is the other half of the
+ * app layer and the piece that has no equivalent in the `spa` template.
+ */
+export const octaneConfig = `import { defineConfig, RenderRoute, ServerRoute } from "@octanejs/vite-plugin";
+import { health } from "./src/server/health.ts";
 
 export default defineConfig({
   router: {
-    routes: [new RenderRoute({ path: "/", entry: ["App", "/src/App.tsrx"] })],
+    routes: [
+      new RenderRoute({ path: "/", entry: ["App", "/src/App.tsrx"] }),
+      new RenderRoute({ path: "/counter", entry: ["Counter", "/src/Counter.tsrx"] }),
+      new ServerRoute({ path: "/api/health", handler: health }),
+    ],
   },
 });
 `;
 
-/** The component both templates start from. */
-export const appComponent = `export function App() @{
-  <main>
-    <h1>Hello from Octane</h1>
-    <p>Edit src/App.tsrx and save.</p>
+/**
+ * The Octane mark, as markup rather than an asset.
+ *
+ * Inline because the wordmark is two colors with different jobs: the glyph
+ * takes `currentColor` so it follows the page's light/dark text, and the flame
+ * keeps the brand red at every theme. An `<img>` can do neither, and a second
+ * file to keep in step with the stylesheet is not worth it for one logo.
+ */
+const LOGO = `<svg class="mark" viewBox="0 0 84 108" fill="none" aria-hidden="true">
+        <path
+          d="M71.0265 37.6009L65.8601 32.48C57.4266 24.1187 52.5193 13.6179 49.6691 1.55156C49.1892 -0.480713 46.2849 -0.534311 45.796 1.49572C43.135 12.5571 39.0884 21.441 31.9122 28.5539L29.1656 31.2763L32.1217 32.6051C34.5258 33.686 36.646 34.9098 38.604 36.3458C40.1609 37.487 41.4587 38.751 42.5898 40.0798L46.9068 35.8031L59.8758 48.6555C67.025 55.7439 67.025 67.2742 59.8758 74.3626L47.0622 87.0609C43.5969 90.4957 38.9915 92.385 34.0932 92.385C29.1949 92.385 24.5895 90.4935 21.1242 87.0609C13.975 79.9726 13.975 68.4422 21.1242 61.3539L26.4529 56.0722C27.6921 53.5084 29.6118 50.1138 31.1844 45.7858C32.4101 42.4136 31.8266 38.8649 29.4653 36.0733L27.1198 33.3041L9.97348 50.2992C-3.32449 63.4822 -3.32449 84.9304 9.97348 98.1133C16.6225 104.706 25.3578 108 34.0932 108C42.8286 108 51.564 104.704 58.213 98.1133L71.0265 85.415C84.3245 72.2321 84.3245 50.7838 71.0265 37.5986V37.6009Z"
+          fill="currentColor"
+        />
+        <path
+          d="M53.682 51.4605C56.0095 56.1079 55.4237 66.6802 46.9654 65.3715C45.0232 65.07 43.2928 64.0941 42.7183 61.8943C42.3578 60.5097 43.3131 58.2697 43.7705 56.9387C46.481 49.0441 43.0923 42.4136 37.2657 38.1413C35.5736 36.9019 33.6314 35.7384 31.1913 34.6396C34.0595 38.0274 34.8684 42.3801 33.2732 46.6277C32.3224 48.9481 31.0606 51.3958 29.9543 53.6514C27.9671 57.7047 26.3178 62.504 27.575 69.1591C28.1879 72.4063 30.2743 75.0706 32.2503 76.9532C26.4259 77.6522 24.1886 73.811 23.0305 72.1986C21.7935 70.4767 20.9328 66.0973 22.7173 62.935C16.4491 69.1502 16.4491 79.2669 22.7173 85.4843C25.759 88.4969 29.7989 90.154 34.0933 90.154C38.3878 90.154 42.4276 88.4969 45.4694 85.4843L56.6562 74.3984C63.0663 67.8527 61.0543 58.7722 53.6798 51.4628L53.682 51.4605Z"
+          fill="#FF415A"
+        />
+      </svg>`;
+
+/**
+ * The documentation cards, matching the card treatment on octanejs.dev: the
+ * same radius, the same subtle surface, and the same accent-tinted hover rather
+ * than a plain border swap.
+ */
+const LINK_STYLES = `      .links {
+        display: grid;
+        grid-template-columns: repeat(auto-fit, minmax(15rem, 1fr));
+        gap: 0.75rem;
+        width: 100%;
+        max-width: 42rem;
+        margin: 0;
+        padding: 0;
+        list-style: none;
+      }
+      .link {
+        display: block;
+        padding: 1rem;
+        border: 1px solid var(--border);
+        border-radius: 0.9rem;
+        background: var(--surface-subtle);
+        color: var(--text);
+        text-align: left;
+        text-decoration: none;
+        transition:
+          background 0.15s,
+          border-color 0.15s,
+          transform 0.15s;
+      }
+      .link:hover {
+        border-color: var(--card-hover-border);
+        background: var(--card-hover-bg);
+        transform: translateY(-1px);
+      }
+      .link-title {
+        display: block;
+        font-size: 0.95rem;
+        font-weight: 600;
+      }
+      .link-body {
+        display: block;
+        margin-top: 0.15rem;
+        color: var(--text-secondary);
+        font-size: 0.82rem;
+        line-height: 1.4;
+      }`;
+
+/** Where the landing page sends people next. */
+const DOC_LINKS = `const LINKS = [
+  {
+    href: "https://octanejs.dev/docs/quick-start",
+    title: "Quick start",
+    body: "Scaffold an app, mount a component, and the .tsrx essentials.",
+  },
+  {
+    href: "https://octanejs.dev/docs/core-apis",
+    title: "Core APIs",
+    body: "State, events, context, effects, async UI, and server rendering.",
+  },
+  {
+    href: "https://octanejs.dev/docs/tsrx-vs-tsx",
+    title: "TSRX vs TSX",
+    body: "What the .tsrx dialect adds on top of ordinary JSX.",
+  },
+  {
+    href: "https://octanejs.dev/docs/differences-from-react",
+    title: "Differences from React",
+    body: "The deliberate divergences. Everything else matching is the point.",
+  },
+];`;
+
+/**
+ * The landing page: the mark, the name, and the way into the documentation.
+ *
+ * `fullstack` renders it through the shared layout, so the two pages carry one
+ * header between them; `spa` has a single page and owns the frame itself.
+ *
+ * @param {keyof typeof MODES} mode
+ * @returns {string}
+ */
+export const appComponent = (mode) =>
+	mode === 'fullstack'
+		? `import { Layout } from "./Layout.tsrx";
+
+${DOC_LINKS}
+
+export function App() @{
+  <Layout>
+    <section class="hero">
+      ${LOGO}
+      <h1 class="title">octane</h1>
+      <p class="lede">
+        React’s programming model, compiled. Edit src/App.tsrx and save — the page
+        updates without a reload.
+      </p>
+      <ul class="links">
+        @for (const link of LINKS; key link.href) {
+          <li>
+            <a class="link" href={link.href} target="_blank" rel="noreferrer">
+              <span class="link-title">{link.title as string}</span>
+              <span class="link-body">{link.body as string}</span>
+            </a>
+          </li>
+        }
+      </ul>
+    </section>
+
+    <style>
+      .hero {
+        display: flex;
+        flex-direction: column;
+        align-items: center;
+        gap: 1.25rem;
+        text-align: center;
+      }
+      .mark {
+        width: 5rem;
+        height: auto;
+      }
+      .title {
+        margin: 0;
+        font-size: 3rem;
+        line-height: 1.1;
+        letter-spacing: -0.03em;
+      }
+      .lede {
+        max-width: 34rem;
+        margin: 0;
+        color: var(--text-secondary);
+        font-size: 1.25rem;
+      }
+${LINK_STYLES}
+    </style>
+  </Layout>
+}
+`
+		: `${DOC_LINKS}
+
+export function App() @{
+  <main class="page">
+    ${LOGO}
+    <h1 class="title">octane</h1>
+    <p class="lede">
+      React’s programming model, compiled. Edit src/App.tsrx and save — the page
+      updates without a reload.
+    </p>
+    <ul class="links">
+      @for (const link of LINKS; key link.href) {
+        <li>
+          <a class="link" href={link.href} target="_blank" rel="noreferrer">
+            <span class="link-title">{link.title as string}</span>
+            <span class="link-body">{link.body as string}</span>
+          </a>
+        </li>
+      }
+    </ul>
+
+    <style>
+      .page {
+        display: flex;
+        min-height: 100dvh;
+        flex-direction: column;
+        align-items: center;
+        justify-content: center;
+        gap: 1.25rem;
+        padding: 3rem 1.5rem;
+        text-align: center;
+      }
+      .mark {
+        width: 5rem;
+        height: auto;
+      }
+      .title {
+        margin: 0;
+        font-size: 3rem;
+        line-height: 1.1;
+        letter-spacing: -0.03em;
+      }
+      .lede {
+        max-width: 34rem;
+        margin: 0;
+        color: var(--text-secondary);
+        font-size: 1.25rem;
+      }
+${LINK_STYLES}
+    </style>
   </main>
 }
 `;
 
+/**
+ * The frame the fullstack pages share. `children` is an ordinary prop, typed as
+ * `OctaneNode` — the renderable type, never React's `ReactNode`.
+ */
+export const layoutComponent = `import type { OctaneNode } from "octane";
+
+interface LayoutProps {
+  children: OctaneNode;
+}
+
+export function Layout(props: LayoutProps) @{
+  <div class="shell">
+    <nav class="nav">
+      <a class="nav-link" href="/">Home</a>
+      <a class="nav-link" href="/counter">Counter</a>
+      <a class={["nav-link", "nav-endpoint"]} href="/api/health">/api/health</a>
+    </nav>
+    <main class="main">{props.children}</main>
+
+    <style>
+      .shell {
+        display: flex;
+        min-height: 100dvh;
+        flex-direction: column;
+      }
+      /* The site's header treatment: sticky, translucent over the page, and
+         separated by a hairline rather than a block of colour. */
+      .nav {
+        position: sticky;
+        top: 0;
+        z-index: 1;
+        display: flex;
+        align-items: center;
+        gap: 1.25rem;
+        height: 60px;
+        padding: 0 1.5rem;
+        border-bottom: 1px solid var(--border);
+        background: var(--header-bg);
+        backdrop-filter: blur(8px);
+      }
+      .nav-link {
+        color: var(--text-secondary);
+        font-size: 0.9rem;
+        font-weight: 500;
+      }
+      .nav-link:hover {
+        color: var(--accent-text);
+      }
+      .nav-endpoint {
+        font-family: "SF Mono", SFMono-Regular, ui-monospace, Menlo, Consolas,
+          monospace;
+        font-size: 0.82rem;
+      }
+      .main {
+        display: flex;
+        flex: 1;
+        align-items: center;
+        justify-content: center;
+        padding: 3rem 1.5rem;
+      }
+    </style>
+  </div>
+}
+`;
+
+/**
+ * The second page, and the reason the fullstack template has two.
+ *
+ * Its markup arrives from the server already rendered — view source and the
+ * count is in the HTML — and the button starts working once hydration reaches
+ * it. That is the whole difference from `spa` in one screen.
+ */
+export const counterComponent = `import { useState } from "octane";
+import { Layout } from "./Layout.tsrx";
+
+export function Counter() @{
+  const [count, setCount] = useState(0);
+
+  <Layout>
+    <section class="counter">
+      <h1 class="title">Server-rendered, then interactive</h1>
+      <p class="lede">
+        This page was rendered on the server and hydrated in the browser. View
+        source to see the markup arrive complete, then press the button.
+      </p>
+      <button class="button" onClick={() => setCount(count + 1)}>
+        {"Pressed " + count + " times"}
+      </button>
+
+      <style>
+        .counter {
+          display: flex;
+          flex-direction: column;
+          align-items: center;
+          gap: 1.25rem;
+          text-align: center;
+        }
+        .title {
+          margin: 0;
+          font-size: 2rem;
+          line-height: 1.1;
+          letter-spacing: -0.02em;
+        }
+        .lede {
+          max-width: 34rem;
+          margin: 0;
+          color: var(--text-secondary);
+          font-size: 1.25rem;
+        }
+        /* The site's primary action: an accent pill. */
+        .button {
+          padding: 0.7rem 1.4rem;
+          border: none;
+          border-radius: 9999px;
+          background: var(--accent);
+          color: var(--on-accent);
+          font: inherit;
+          font-weight: 600;
+          cursor: pointer;
+          transition: background 0.15s;
+        }
+        .button:hover {
+          background: var(--accent-hover);
+        }
+      </style>
+    </section>
+  </Layout>
+}
+`;
+
+/**
+ * A server route: a plain function from the request context to a `Response`,
+ * with no component and no rendering involved.
+ */
+export const healthRoute = `/**
+ * Handles GET /api/health, declared in octane.config.ts.
+ *
+ * A ServerRoute returns a Response, so this never renders and never ships to
+ * the browser — it is the place for an API endpoint, a webhook, or a form
+ * action.
+ */
+export function health(): Response {
+  return Response.json({ status: "ok" });
+}
+`;
+
+/**
+ * The reset and the theme tokens every component reads, taken from
+ * octanejs.dev so a scaffolded app and the documentation look like one thing.
+ *
+ * A stylesheet rather than a `<style>` in the shell. A component's own `<style>`
+ * is scoped — the compiler appends a scope hash to its selectors — so it can
+ * style that component's markup but never `body`, and these custom properties
+ * have to resolve for every component at once. Keeping them in a file the shell
+ * links, rather than inline in the shell, means `init` still has something to
+ * point at when the project brought its own `index.html` and kept it.
+ *
+ * Linked from the shell rather than imported by a component on purpose: a CSS
+ * import is injected by JavaScript in dev, so the tokens would arrive after the
+ * server-rendered markup that reads them and the first paint would flash.
+ */
+export const globalStyles = `:root {
+  --bg: #23272f;
+  --panel: #2b3138;
+  --text: #f4eee8;
+  --text-secondary: #99a1b3;
+  --accent: #ff415a;
+  --accent-hover: #ff5d72;
+  --accent-text: #ff5d72;
+  --on-accent: #16181d;
+  --border: rgba(255, 255, 255, 0.1);
+  --surface: rgba(255, 255, 255, 0.06);
+  --surface-subtle: rgba(255, 255, 255, 0.03);
+  --header-bg: rgba(35, 39, 47, 0.85);
+  /* Accent tints for the card hover, the same in both themes. */
+  --card-hover-border: rgba(255, 93, 114, 0.4);
+  --card-hover-bg: rgba(255, 65, 90, 0.07);
+  color-scheme: dark;
+}
+/* octanejs.dev defaults to dark and offers a toggle. A scaffold has no
+   toggle to offer, so the same palette follows the operating system
+   instead — and the values on both sides are the site's own. */
+@media (prefers-color-scheme: light) {
+  :root {
+    --bg: #ffffff;
+    --panel: #f4f5f7;
+    --text: #1c2027;
+    --text-secondary: #5c6473;
+    --accent-hover: #c81e37;
+    --accent-text: #d81f38;
+    --on-accent: #ffffff;
+    --border: rgba(0, 0, 0, 0.12);
+    --surface: rgba(0, 0, 0, 0.04);
+    --surface-subtle: rgba(0, 0, 0, 0.025);
+    --header-bg: rgba(255, 255, 255, 0.85);
+    color-scheme: light;
+  }
+}
+* {
+  box-sizing: border-box;
+}
+body {
+  margin: 0;
+  background: var(--bg);
+  color: var(--text);
+  font-family:
+    Inter, system-ui, -apple-system, "Segoe UI", Roboto, Helvetica, Arial,
+    sans-serif;
+  font-size: 16px;
+  line-height: 1.6;
+  -webkit-font-smoothing: antialiased;
+}
+code,
+pre,
+kbd,
+samp {
+  font-family: "SF Mono", SFMono-Regular, ui-monospace, Menlo, Consolas,
+    monospace;
+}
+a {
+  color: var(--accent-text);
+  text-decoration: none;
+}
+a:hover {
+  color: var(--accent-hover);
+}
+::selection {
+  background: rgba(255, 65, 90, 0.45);
+}
+`;
+
 const SPA_INDEX_HTML = `<!doctype html>
 <html lang="en">
   <head>
     <meta charset="utf-8" />
     <meta name="viewport" content="width=device-width, initial-scale=1" />
     <title>Octane app</title>
+    <link rel="stylesheet" href="/src/styles.css" />
   </head>
   <body>
     <div id="root"></div>
@@ -122,6 +564,7 @@ const SSR_INDEX_HTML = `<!doctype html>
     <meta charset="utf-8" />
     <meta name="viewport" content="width=device-width, initial-scale=1" />
     <title>Octane app</title>
+    <link rel="stylesheet" href="/src/styles.css" />
     <!--ssr-head-->
   </head>
   <body>
@@ -226,7 +669,7 @@ export const tsconfig = `{
       }
     ]
   },
-  "include": ["src/**/*", "vite.config.ts"]
+  "include": ["src/**/*", "vite.config.ts", "octane.config.ts"]
 }
 `;
 

package/src/data/octane-data.json

@@ -2,7 +2,7 @@
   "bindings": [
     {
       "name": "@octanejs/apollo-client",
-      "version": "0.1.18",
+      "version": "0.1.20",
       "category": "AI, data, and routing",
       "upstream": { "package": "@apollo/client", "version": "4.2.6" },
       "surface": "Complete published client adapter surface: all 18 @apollo/client/react runtime exports and their Apollo 4.2.6 TypeScript declarations, framework-neutral root/testing exports, an Octane MockedProvider, and the Octane-native /react/ssr prerenderStatic entry.",
@@ -16,7 +16,7 @@
     },
     {
       "name": "@octanejs/aria",
-      "version": "0.0.17",
+      "version": "0.0.19",
       "category": "UI and interaction",
       "upstream": { "package": "react-aria", "version": "3.50.0" },
       "surface": "Phases 0-5 + the Tree/Table follow-up complete. Phases 0-1: the utils foundation, SSR utilities, the complete interactions area (usePress, useHover, focus/keyboard family, useLongPress, useMove, Pressable/PressResponder), the focus area (FocusScope with containment/restore/focus managers, FocusRing, useFocusRing, useHasTabbableChild), the i18n area (I18nProvider, locale/collator/formatter/filter hooks), form validation (useFormValidation + stately useFormValidationState), and the leaf hooks: useButton/useToggleButton(+Group), useLabel/useField, useCheckbox(+Group/+Item), useRadio/useRadioGroup, useSwitch, useTextField, useSearchField, useProgressBar, useMeter, useSeparator, useLink, useDisclosure, useToolbar, VisuallyHidden. Phase 2 adds the collections + selection tier: the stately collections engine (CollectionBuilder/Item/Section/useCollection) and selection core (Selection/SelectionManager/useMultipleSelectionState), the stately state hooks (useListState/useSingleSelectListState, useTreeState, useMenuTriggerState/useSubmenuTriggerState, useOverlayTriggerState, useSelectState, useComboBoxState, useTabListState, useNumberFieldState, useSliderState), the aria selection area (useSelectableCollection/-Item/-List, useTypeSelect, ListKeyboardDelegate, DOMLayoutDelegate), and the aria hooks useListBox/useOption/useListBoxSection, useMenu/useMenuItem/useMenuSection/useMenuTrigger/useSubmenuTrigger, useTab/useTabList/useTabPanel, useSlider/useSliderThumb, useNumberField, useGridList(+Item/+Section/+SelectionCheckbox), useTag/useTagGroup, useBreadcrumbs/useBreadcrumbItem — plus the matching react-stately state hooks under `@octanejs/aria/stately`. Phase 3 adds the overlays hooks tier: the stately `useTooltipTriggerState` and the whole aria overlays area (usePreventScroll, ariaHideOutside, DismissButton, PortalProvider, useOverlay, useOverlayTrigger, useOverlayPosition + calculatePosition, Overlay/useOverlayFocusContain, useModal/ModalProvider/OverlayProvider/OverlayContainer, useModalOverlay, usePopover), plus the consumers useDialog, useTooltip/useTooltipTrigger, useSelect/useHiddenSelect/HiddenSelect, and useComboBox. Differential-verified byte-identical against the real react-aria (interactions + button/toggle/checkbox/switch/radio/textfield/progress + tabs + listbox + select + combobox fixtures); dialog/tooltip/overlay focus-trap/dismiss/scroll-lock paths are covered by behavioral tests (the differential rig shares one document, so focus/portal/positioning aren't rig-driveable). Autocomplete (useAutocomplete/useSearchAutocomplete) is deferred — useComboBox does not depend on it in 3.50.0. Phase 4 adds the react-aria-components foundation under `@octanejs/aria/components`: the collections engine re-hosted on a detached real-DOM store (BaseCollection/CollectionBuilder/createLeafComponent/createBranchComponent/Hidden/useCachedChildren + Collection/Section), the RAC plumbing (Provider, useContextProps, slotted contexts, useRenderProps/composeRenderProps with data-* state attributes), and the non-collection components: Button, ToggleButton(+Group), Checkbox(+Group/Field/Button), Switch(+Field/Button), RadioGroup(+Radio/Field/Button), TextField, SearchField, NumberField, Form, Label/Input/TextArea/FieldError, Group, Toolbar, Separator, Header, Heading, Link, ProgressBar, Meter, Slider(+Output/Track/Thumb/Fill), Disclosure(+Group/Panel), DialogTrigger/Dialog, Modal/ModalOverlay, Popover, TooltipTrigger/Tooltip, OverlayArrow, Text, Keyboard, SelectionIndicator, SharedElementTransition. Phase-4 differentials drive the REAL components on both sides byte-identical (Button hover+mid-press, ToggleButton, Checkbox, TextField typing, Disclosure expand/collapse). Phase 5 adds the RAC collection components over that engine: Autocomplete (full — aria useAutocomplete + stately useAutocompleteState now ported), ListBox(+Item/Section/LoadMoreItem), Menu(+MenuTrigger/SubmenuTrigger/MenuItem/MenuSection), Select(+SelectValue), ComboBox(+ComboBoxValue), Tabs(+TabList/Tab/TabPanels/TabPanel), TagGroup(+TagList/Tag), GridList(+Item/Section/Header/LoadMoreItem), Breadcrumbs(+Breadcrumb), and the DragAndDrop context layer (DropIndicator/contexts/DragAndDropHooks type; components' dnd branches are inert — the dnd engine and useDragAndDrop() itself arrive in a later phase, the stub throws). Phase-5 differentials drive the REAL react-aria-components byte-identical (ListBox selection + keyed reverse, Tabs switch, TagGroup multi-select, GridList row selection, Breadcrumbs, ComboBox typing); Menu/Select open-state (portal'd) carries behavioral coverage incl. keyboard-driven submenus. The Tree/Table follow-up adds the remaining collection verticals: stately grid (GridCollection/useGridState) + the full stately table area (TableCollection/useTableState/column-resize state/UNSTABLE_useTreeGridState), the aria tree hooks (useTree/useTreeItem) and the full aria table hook area (useTable family, TableKeyboardDelegate, useTableColumnResize, grid hooks it rides on), RAC Tree(+TreeItem/TreeItemContent/TreeSection/TreeHeader/TreeLoadMoreItem) and RAC Table(+TableHeader/TableBody/Column/Row/Cell/ColumnResizer/ResizableTableContainer/TableFooter/TableLoadMoreItem). Tree structure states and the interactive Table (sort cycling, row selection) are differential-verified byte-identical vs the real react-aria-components; chevron-driven Tree interaction carries behavioral coverage (the rig's virtual clicks cannot faithfully reproduce the focus-effect interplay on the React side). TableLayout lands with the Virtualizer; date/color families and the drag-and-drop engine are not started — see the migration plan.",
@@ -31,7 +31,7 @@
     },
     {
       "name": "@octanejs/base-ui",
-      "version": "0.1.21",
+      "version": "0.1.23",
       "category": "UI and interaction",
       "upstream": { "package": "@base-ui/react", "version": "1.6.0" },
       "surface": "Alpha, in progress: 34 of 43 upstream subpaths. The foundation, overlay infrastructure, hover/focus interaction layer, list-navigation/typeahead layer and popup viewport have landed, along with Dialog, AlertDialog, Popover, Tooltip, PreviewCard, the full form-control set, and the standalone Button/DirectionProvider/CSPProvider/useMediaQuery utilities — ported at full fidelity and differential-verified against the real `@base-ui/react`. Menu is COMPLETE at all 20 upstream parts — Root/Trigger/Portal/Positioner/Popup, the full item family (Item, LinkItem, CheckboxItem, RadioGroup/RadioItem and their indicators, Group/GroupLabel, Separator), Arrow, Backdrop, Viewport, and SubmenuRoot/SubmenuTrigger. Menubar and ContextMenu have landed too, so the whole menu family is complete. Toast is complete at all 11 parts, including the imperative toast manager, auto-dismiss timers with hover/focus pausing, and promise toasts; swipe-to-dismiss is covered too. Collapsible is complete at all 3 upstream parts (Root/Trigger/Panel), including upstream's <Activity> animation-resume suppression — octane's Activity has React's contract (hidden subtrees keep state and DOM while effects tear down and re-fire on reveal), so that path is ported rather than skipped and is the first component carrying a port of Base UI's OWN test file, under tests/upstream/ — 16 of its 35 upstream cases, being every case that does not require real layout measurement, CSS transition/keyframe sequencing, React.Activity, or find-in-page `beforematch`. Accordion is complete at all 5 upstream parts (Root/Item/Header/Trigger/Panel), built directly on Collapsible — each Item runs its own useCollapsibleRoot and provides CollapsibleRootContext, exactly as upstream does. It carries 18 tests: 15 ported from upstream's own suite plus 3 written to close a real gap — upstream only exercises single-vs-multiple toggling inside jsdom-skipped blocks, so removing the single-mode collapse branch passed every ported case.",
@@ -47,7 +47,7 @@
     },
     {
       "name": "@octanejs/cmdk",
-      "version": "0.1.6",
+      "version": "0.1.8",
       "category": "UI and interaction",
       "upstream": { "package": "cmdk", "version": "1.1.1" },
       "surface": "Complete against the published `cmdk@1.1.1` public surface: `Command` (the root itself) and the `CommandRoot` named export, `Command.Input`, `Command.List`, `Command.Item`, `Command.Group`, `Command.Separator`, `Command.Dialog`, `Command.Empty`, `Command.Loading`, the flat `CommandX` aliases, `useCommandState`, and `defaultFilter` — with the DOM-authoritative store and item/group registration, `useValue` text-content inference, `onInput`-driven search, score filtering plus item and group DOM sorting, keyboard navigation (arrows/Home/End/vim/Enter), controlled `value`/`onValueChange`/`loop`/`shouldFilter`/custom `filter`/`forceMount`, the `--cmdk-list-height` ResizeObserver, and a Radix-backed `Command.Dialog`. `asChild` is the one unsupported prop (see divergences).",
@@ -78,7 +78,7 @@
     },
     {
       "name": "@octanejs/devtools",
-      "version": "0.0.11",
+      "version": "0.0.13",
       "category": "Styling, tests, and devtools",
       "upstream": { "package": "octane", "version": "workspace" },
       "surface": "Octane-native DevTools plugin (not an upstream port): renders live runtime diagnostics into a TanStack Devtools host via @tanstack/devtools-event-client. P1 ships the Components tree + state inspector.",
@@ -88,7 +88,7 @@
     },
     {
       "name": "@octanejs/dexie",
-      "version": "0.1.16",
+      "version": "0.1.18",
       "category": "AI, data, and routing",
       "upstream": { "package": "dexie-react-hooks", "version": "4.4.0" },
       "surface": "Port of the public dexie-react-hooks surface: useObservable, useLiveQuery, useSuspendingObservable, useSuspendingLiveQuery, usePermissions, and useDocument, with Dexie's framework-neutral API re-exported from the package root.",
@@ -102,7 +102,7 @@
     },
     {
       "name": "@octanejs/dnd-kit",
-      "version": "0.1.18",
+      "version": "0.1.20",
       "category": "UI and interaction",
       "upstream": { "package": "@dnd-kit/react", "version": "0.5.0" },
       "surface": "Complete modern dnd-kit React-adapter surface: DragDropProvider, DragOverlay, useDraggable/useDroppable, manager/monitor/operation hooks, PointerSensor/KeyboardSensor re-exports, the public signal-hook utilities, useSortable, and all four upstream entry points.",
@@ -113,9 +113,27 @@
       "ssr": "Static SSR and hydration are covered; DOM plugins initialize only after client refs register.",
       "verified": "2026-07-15"
     },
+    {
+      "name": "@octanejs/electron",
+      "version": "0.0.3",
+      "category": "Desktop",
+      "upstream": { "package": "electron", "version": "43.2.0" },
+      "surface": "Process-split Electron bindings: ./main registers ipcMain handlers, ./main/native re-exports main-only Electron APIs (Menu, Tray, session, protocol, BrowserWindow, …), ./preload exposes Electron IPC and desktop helpers via contextBridge, and the renderer entry provides Octane hooks (useInvoke, useInvokeState, useIpcEvent, useNativeTheme, useWindowState) plus promise helpers for app/window/dialog/shell/clipboard/screen. Menu/Tray/session/protocol stay intentional main-only under contextIsolation.",
+      "divergences": [
+        "There is no React binding upstream; Electron is framework-agnostic, so this package mirrors the React Electron process layout rather than porting a React library.",
+        "Renderer code uses window.__OCTANE_ELECTRON__ because contextIsolation forbids importing electron in the page.",
+        "Menu, Tray, session, and protocol are re-exported from @octanejs/electron/main/native for main-process consumers and are intentionally not bridged into the renderer.",
+        "Hook call-site slots are forwarded through Octane's compiler binding ABI.",
+        "useInvoke integrates with Octane's use() rather than React's use().",
+        "useInvokeState returns to pending on refetch and does not implement stale-while-revalidate.",
+        "Built-in desktop helpers use octane:* IPC channels; apps may allowlist additional channels in preload."
+      ],
+      "ssr": "Server rendering performs no IPC. useInvokeState renders pending and issues the command on the client after hydration; useIpcEvent and reactive desktop hooks subscribe only on the client. useInvoke without a host rejects with ElectronUnavailableError.",
+      "verified": "2026-08-02"
+    },
     {
       "name": "@octanejs/floating-ui",
-      "version": "0.1.22",
+      "version": "0.1.24",
       "category": "UI and interaction",
       "upstream": { "package": "@floating-ui/react", "version": "0.27.19" },
       "surface": "Positioning (`useFloating`, ref-aware `arrow`, the `@floating-ui/dom` middleware re-exports, the floating tree), the full interaction-hook set (`useInteractions`, `useHover` + `safePolygon`, `useClick`, `useFocus`, `useDismiss`, `useRole`, `useClientPoint`, `useListNavigation`, `useTypeahead`), the component layer (`FloatingPortal`, `FloatingOverlay`, `FloatingFocusManager`, `FloatingArrow`, `FloatingList`, `Composite`), and transitions + `FloatingDelayGroup`.",
@@ -125,20 +143,20 @@
     },
     {
       "name": "@octanejs/hook-form",
-      "version": "0.1.20",
+      "version": "0.1.22",
       "category": "Forms and content",
       "upstream": { "package": "react-hook-form", "version": "7.81.0" },
-      "surface": "Complete port of react-hook-form 7.81.0 (upstream commit b7df98c2) with the upstream test suite ported: `useForm`, `useController`, `useFieldArray`, `useFormState`, `useWatch`, `useFormContext`/`FormProvider`, schema resolvers, and all validation modes.",
+      "surface": "Complete port of react-hook-form 7.81.0 (tag commit 46b217e034dd92f7aa3cb3a478815556b416b299). The automated parity check runs all 1,193 original tests against the pinned React package as a pristine baseline; the Octane port separately runs byte-locked, unfiltered DOM and server suites with exact collected/executed inventories containing 1,187 entries representing 1,178 unique file/full-name identities. The nine duplicate entries are repeated titles within the DOM inventory; the server inventory is disjoint. Coverage includes `useForm`, `useController`, `useFieldArray`, `useFormState`, `useWatch`, `useFormContext`/`FormProvider`, schema resolvers, and all validation modes.",
       "divergences": [
         "`register()` returns `onInput` (octane's native per-keystroke event) instead of React's synthetic `onChange`; mode names and `register` option keys keep the upstream spelling.",
-        "Ported tests directly assert Octane's documented microtask-flush commit granularity, eager `Object.is` setState bailout, and native input-event delivery; the suite contains no skipped or expected-failure cases."
+        "The structured parity ledger records native no-op input delivery, microtask batching, duplicate resolver notification, async act flush, reset render-count, and eager `Object.is` bailout differences with executable case identities, consumer impact, and migration guidance; the suite contains no skipped or expected-failure cases."
       ],
       "ssr": "Supported and tested — the upstream `*.server.test.tsx` suite runs via `octane/server` with byte-identical markup.",
-      "verified": "2026-07-14"
+      "verified": "2026-08-01"
     },
     {
       "name": "@octanejs/i18next",
-      "version": "0.1.18",
+      "version": "0.1.20",
       "category": "Forms and content",
       "upstream": { "package": "react-i18next", "version": "17.0.9" },
       "surface": "Complete runtime port of react-i18next 17.0.9: useTranslation, I18nextProvider/context, Trans/TransWithoutContext, IcuTrans/IcuTransWithoutContext, Translation, the withTranslation/withSSR HOCs, useSSR, namespace reporting, initialization/default helpers, and the root ICU helper exports over the unchanged i18next core.",
@@ -153,7 +171,7 @@
     },
     {
       "name": "@octanejs/jotai",
-      "version": "0.1.20",
+      "version": "0.1.22",
       "category": "Shared state",
       "upstream": { "package": "jotai", "version": "2.20.2" },
       "surface": "Complete 1:1 port: the framework-agnostic vanilla core (`jotai/vanilla`, `/vanilla/utils`, `/vanilla/internals`) is reused verbatim; the React layer (`Provider`, `useStore`, `useAtom`, `useAtomValue`, `useSetAtom`) and `react/utils` (`useResetAtom`, `useReducerAtom`, `useAtomCallback`, `useHydrateAtoms`) are ported onto octane hooks, preserving upstream's useReducer force-update + effect-subscription implementation, async atoms via octane's `use()`.",
@@ -163,7 +181,7 @@
     },
     {
       "name": "@octanejs/lexical",
-      "version": "0.1.22",
+      "version": "0.1.24",
       "category": "Forms and content",
       "upstream": { "package": "@lexical/react", "version": "0.46.0" },
       "surface": "35 of 39 `@lexical/react` modules ported: composer + contexts, the editable surface, plain/rich text, and the full plugin/menu set (history, lists + check-list, links, tables, markdown shortcuts, the typeahead/node-menu/context-menu family, draggable-block, character-limit, …) plus the `useLexical*` hooks.",
@@ -176,7 +194,7 @@
     },
     {
       "name": "@octanejs/lucide",
-      "version": "0.1.18",
+      "version": "0.1.20",
       "category": "UI and interaction",
       "upstream": { "package": "lucide-react", "version": "1.24.0" },
       "surface": "Complete against the published `lucide-react@1.24.0` runtime surface: every canonical icon and alias, the `icons` namespace, `Icon`, `createLucideIcon`, `LucideProvider`, `useLucideContext`, `DynamicIcon`, `iconNames`, `dynamicIconImports`, and per-icon subpath imports.",
@@ -189,7 +207,7 @@
     },
     {
       "name": "@octanejs/mantine-hooks",
-      "version": "0.1.4",
+      "version": "0.1.6",
       "category": "UI and interaction",
       "upstream": { "package": "@mantine/hooks", "version": "9.5.0" },
       "surface": "Complete @mantine/hooks 9.5.0 runtime export surface: state, timing, storage, viewport, input, focus, pointer, observer, hotkey, scrolling, collapse, drag, splitter, mask, and utility hooks.",
@@ -203,7 +221,7 @@
     },
     {
       "name": "@octanejs/mdx",
-      "version": "0.1.20",
+      "version": "0.1.22",
       "category": "Forms and content",
       "upstream": { "package": "@mdx-js/mdx", "version": "3.1.1" },
       "surface": "The full compile-don't-interpret pipeline: `.mdx`/`.md` → `@mdx-js/mdx` (reused verbatim) → octane compiler, via the `octaneMdx()` Vite plugin plus the `./compile` and `./server` entries; compiler warnings propagate through direct and Vite compile surfaces with authored `.mdx` ranges; `@mdx-js/react`'s provider layer (`MDXProvider`/`useMDXComponents`) is ported onto octane context. The octane website runs on it.",
@@ -215,7 +233,7 @@
     },
     {
       "name": "@octanejs/mobx",
-      "version": "0.1.4",
+      "version": "0.1.6",
       "category": "Shared state",
       "upstream": { "package": "mobx-react-lite", "version": "4.1.1", "core": "mobx@6.16.1" },
       "surface": "The framework-independent MobX core is re-exported verbatim. The function-component binding includes observer, Observer, useObserver, useLocalObservable, enableStaticRendering, isUsingStaticRendering, and the deprecated useStaticRendering alias.",
@@ -229,7 +247,7 @@
     },
     {
       "name": "@octanejs/motion",
-      "version": "0.1.22",
+      "version": "0.1.24",
       "category": "UI and interaction",
       "upstream": { "package": "motion", "version": "12.42.2" },
       "surface": "Core surface: `motion.<tag>` (animate, gestures, variants with propagation/stagger, drag, layout basics), `AnimatePresence`, `MotionConfig`, and the motion-value hooks (`useMotionValue`, `useScroll`, `useTransform`, `useSpring`, `useAnimate`, `useMotionValueEvent`); motion-dom's animation engine and gesture primitives are reused verbatim.",
@@ -242,7 +260,7 @@
     },
     {
       "name": "@octanejs/nuqs",
-      "version": "0.1.12",
+      "version": "0.1.14",
       "category": "AI, data, and routing",
       "upstream": { "package": "nuqs", "version": "2.9.1" },
       "surface": "Full vendored port: the framework-agnostic core (`parsers`/`parseAs*`/`createParser`, `createSerializer`, `createLoader`, `createStandardSchemaV1`, the throttle/debounce update queues, sync emitter and URL encoding) is vendored verbatim from nuqs 2.9.1; the React layer (`useQueryState`, `useQueryStates`, the `useSyncExternalStores` helper and the adapter context) is ported onto octane's hooks — same `useState`/`useEffect`/`useSyncExternalStore` implementation shape as upstream, so re-render and URL-reconciliation behaviour matches nuqs on React. Adapters ported: `@octanejs/nuqs/adapters/react` (`NuqsAdapter`, `enableHistorySync`), `/adapters/custom` (`unstable_createAdapterProvider`), `/adapters/testing` (`NuqsTestingAdapter`, `withNuqsTestingAdapter`). Server surface (`@octanejs/nuqs/server`) exposes `createLoader`/`createSerializer`/parsers/`createStandardSchemaV1`.",
@@ -257,7 +275,7 @@
     },
     {
       "name": "@octanejs/phosphor-icons",
-      "version": "0.0.3",
+      "version": "0.0.5",
       "category": "UI and interaction",
       "upstream": { "package": "@phosphor-icons/react", "version": "2.1.10" },
       "surface": "All 1,512 canonical icons from @phosphor-icons/core@2.1.1, including the upstream deprecated Icon-suffixed aliases, six weights, IconContext, IconBase, root exports, and per-icon imports.",
@@ -271,7 +289,7 @@
     },
     {
       "name": "@octanejs/radix",
-      "version": "0.1.22",
+      "version": "0.1.24",
       "category": "UI and interaction",
       "upstream": { "package": "radix-ui", "version": "1.6.4" },
       "surface": "Complete against the unified `radix-ui@1.6.4` component surface — all primitives (incl. Dialog, the Menu/DropdownMenu/ContextMenu family, Popover, Tooltip, Select, NavigationMenu, Toast, Menubar, Slider, the form controls, and OneTimePasswordField/PasswordToggleField) plus the composition/state/overlay foundations — verified by a differential suite (same fixtures through octane and the real radix-ui, byte-identical DOM).",
@@ -284,7 +302,7 @@
     },
     {
       "name": "@octanejs/rainbowkit",
-      "version": "0.0.3",
+      "version": "0.0.5",
       "category": "Web3",
       "upstream": { "package": "@rainbow-me/rainbowkit", "version": "2.2.11" },
       "surface": "Octane-native RainbowKitProvider, ConnectButton and ConnectButton.Custom, WalletButton, connect/account/chain modal hooks, connector selection, account/chain actions, native accessible dialogs, and light/dark/midnight themes.",
@@ -300,7 +318,7 @@
     },
     {
       "name": "@octanejs/react-error-boundary",
-      "version": "0.1.4",
+      "version": "0.1.6",
       "category": "UI and interaction",
       "upstream": { "package": "react-error-boundary", "version": "6.1.2" },
       "surface": "Complete against the published react-error-boundary 6.1.2 function/type surface adapted to Octane: ErrorBoundary, ErrorBoundaryContext, getErrorMessage, fallback variants, onError/onReset callbacks, resetKeys, useErrorBoundary (including error), withErrorBoundary, OnErrorCallback, and UseErrorBoundaryApi.",
@@ -314,7 +332,7 @@
     },
     {
       "name": "@octanejs/recharts",
-      "version": "0.1.20",
+      "version": "0.1.22",
       "category": "Data-heavy screens",
       "upstream": { "package": "recharts", "version": "3.9.2" },
       "surface": "Broad runtime support across cartesian, polar, hierarchical, tooltip, legend, responsive-container, shape, and chart-state surfaces. `Brush` and `Treemap` remain intentionally unsupported.",
@@ -326,7 +344,7 @@
     },
     {
       "name": "@octanejs/redux",
-      "version": "0.1.20",
+      "version": "0.1.22",
       "category": "Shared state",
       "upstream": { "package": "react-redux", "version": "9.3.0" },
       "surface": "The hooks + `Provider` surface of react-redux 9.3.0 (`useSelector`, `useDispatch`, `useStore`, and the custom-context factory variants) on octane's `useSyncExternalStore`; works with any Redux 5 / Redux Toolkit store. Export parity is pinned by test.",
@@ -339,7 +357,7 @@
     },
     {
       "name": "@octanejs/redux-toolkit",
-      "version": "0.1.18",
+      "version": "0.1.20",
       "category": "Shared state",
       "upstream": { "package": "@reduxjs/toolkit", "version": "2.12.0" },
       "surface": "Complete four-entry-point port: the framework-agnostic Toolkit and RTK Query core are re-exported verbatim; `/query/react` provides generated query, lazy-query, mutation, infinite-query, prefetch hooks and `ApiProvider`; `/react` provides the dynamic-middleware dispatch-hook integration.",
@@ -352,7 +370,7 @@
     },
     {
       "name": "@octanejs/remix-router",
-      "version": "0.1.19",
+      "version": "0.1.21",
       "category": "AI, data, and routing",
       "upstream": { "package": "react-router", "version": "8.2.0" },
       "surface": "COMPLETE port (all phases shipped — full export parity, EXPECTED_MISSING is empty): the framework-agnostic router core (lib/router/* + framework-free helpers, ~12k lines) is vendored byte-close and validated by 161 ported upstream router tests plus four focused v8.2 regression pins; the data-mode React layer (createMemoryRouter, RouterProvider incl. the /dom flushSync variant, Outlet, Await, RenderErrorBoundary/errorElement, Link + useLinkClickHandler, and the full read-hook family) and the declarative layer (MemoryRouter, Routes/Route in BOTH children forms — descriptor children walked upstream-style, .tsrx block children via a registration collector — Navigate, createRoutesFromChildren/Elements, the UNSAFE_With*Props wrappers) and the DOM layer (createBrowserRouter/createHashRouter with __staticRouterHydrationData parsing, BrowserRouter/HashRouter/unstable_HistoryRouter, Link + NavLink incl. the isActive/isPending render props, useLinkClickHandler, useSearchParams) and the mutation layer (Form on octane's native delegated submit event, useSubmit incl. JSON encTypes, useFormAction with ?index resolution, useFetcher/useFetchers incl. fetcher.Form/load/submit/reset and shared keys), the guard/scroll layer (useBlocker, unstable_usePrompt, ScrollRestoration/UNSAFE_useScrollRestoration, useBeforeUnload, useViewTransitionState, unstable_useRoute/unstable_useRouterState), static SSR (StaticRouter, StaticRouterProvider, createStaticHandler/createStaticRouter rendering through octane/server — markup byte-identical to react-dom/server after marker stripping, hydration payload identical), and the vendored cookie/session server runtime (createCookie/createSession/createCookieSessionStorage/createMemorySessionStorage) are transcribed onto octane and differential-verified against real react-router. Framework-mode + RSC names (Meta/Links/Scripts, createRequestHandler, UNSAFE_ internals) exist as THROWING STUBS so parity is honest.",
@@ -368,7 +386,7 @@
     },
     {
       "name": "@octanejs/rxjs",
-      "version": "0.1.2",
+      "version": "0.1.4",
       "category": "Shared state",
       "upstream": {
         "package": "@react-rxjs/core + @react-rxjs/utils",
@@ -384,13 +402,13 @@
     },
     {
       "name": "@octanejs/shadcn",
-      "version": "0.0.8",
+      "version": "0.0.10",
       "category": "UI and interaction",
       "upstream": {
         "package": "shadcn-ui/ui (radix base)",
         "version": "4baadbc6517070ae8f8feb2c97037adc2b305544 + shadcn@4.14.1"
       },
-      "surface": "Two primitive bases. RADIX base (default, reached at the bare subpaths): tiers 1-2 complete plus the first tier-3 composites — 40 component families. REACT ARIA base (@octanejs/shadcn/react-aria/<Family>): 33 families over @octanejs/aria/components, taken from upstream's aria-nova style and verified class-string identical to it; not ported are select and sonner (need input-group and next-themes), while hover-card, menubar and navigation-menu do not exist in upstream's aria base. Sources live at src/bases/<base>/ui/ with lib/hooks/styles shared. DISTRIBUTION is registry-first with per-family subpath exports; the monolithic root entry is removed. STYLING FLAVOR: the radix base is mid-migration from the pinned cn-* semantic-hook system to the default-Tailwind utilities-inlined flavor (user-directed); the react-aria base is uniformly the utilities-inlined aria-nova output. The shipped registry (packages/shadcn/registry) still emits the radix base only — the per-base registry namespace is decided when the first consumer needs it. BASE UI base (@octanejs/shadcn/base-ui/<Family>): STARTED, 21 of 44 families and PARTIAL. `accordion` is transcribed from upstream and runs on the @octanejs/base-ui accordion primitive — the first primitive-backed family in this base. The rest are primitive-free: `alert` is transcribed from upstream's Base UI source and verified byte-identical to it; `aspect-ratio`, `card`, `empty`, `native-select`, `skeleton` and `spinner` are DERIVED from the react-aria base and are NOT yet verified against upstream, which each file's header records. Nothing primitive-backed is ported: Base UI's primitive API is structurally different from React Aria's, so it cannot be derived and needs transcribed upstream sources. The foundations now run on real Base UI primitives: `button` (Button), `input` (Field.Control), `label` (Field.Label) and `separator` (Separator), alongside plain-host `textarea` and `kbd` — Base UI ships no textarea or Keyboard primitive, so those match the radix base's shape rather than the aria base's. `separator` deliberately takes the ARIA base's class string, not the radix one: Base UI emits `aria-orientation`, so radix's `data-horizontal:` utilities would never match and the separator would render with no thickness. `button` omits the aria base's data-variant/data-size, which upstream's Base UI base also omits, and ships no LinkButton because Base UI has no Link primitive — which is why `pagination` remains unported. `alert-dialog` is transcribed from upstream and is the first portalled family here (Overlay->Backdrop, Content->Popup, Cancel->Close); it drops upstream's `cn-font-heading` on the title, matching the react-aria base, because this package ships the utilities-inlined flavor and nothing defines that semantic hook. The form controls (`checkbox`, `switch`, `radio-group`) adapt their conditional utilities rather than copying them: Base UI publishes bare `data-checked`/`data-unchecked` where radix publishes `data-state=\"checked\"`, and every Root renders a `<span role=…>` that is never `:disabled`, so `disabled:` variants become `data-disabled:`. Both dialects are pinned by tests asserting the rendered DOM carries the attributes the class strings target. The overlays (`dialog`, `popover`, `tooltip`, plus `alert-dialog`) adapt positioning: Base UI inserts a Positioner layer (Portal > Positioner > Popup) and names its transform origin `--transform-origin`, not radix's `--radix-<part>-content-transform-origin`, so a copied radix class would reference a variable nothing sets and the popup would scale from the wrong corner. Tooltip also drops radix's `data-[state=delayed-open]` utilities, which have no Base UI counterpart. `PopoverAnchor` is absent because Base UI positions via the Positioner's `anchor` prop rather than an Anchor element — recorded in tests/cross-base.test.ts.",
+      "surface": "Two primitive bases. RADIX base (default, reached at the bare subpaths): tiers 1-2 complete plus the first tier-3 composites — 40 component families. REACT ARIA base (@octanejs/shadcn/react-aria/<Family>): 33 families over @octanejs/aria/components, taken from upstream's aria-nova style and verified class-string identical to it; not ported are select and sonner (need input-group and next-themes), while hover-card, menubar and navigation-menu do not exist in upstream's aria base. Sources live at src/bases/<base>/ui/ with lib/hooks/styles shared. DISTRIBUTION is registry-first with per-family subpath exports; the monolithic root entry is removed. STYLING FLAVOR: the radix base is mid-migration from the pinned cn-* semantic-hook system to the default-Tailwind utilities-inlined flavor (user-directed); the react-aria base is uniformly the utilities-inlined aria-nova output. THE REGISTRY NOW COVERS ALL THREE BASES, using shadcn's own mechanism rather than a namespace: base and visual style compose into components.json's single `style` field, which the CLI substitutes into the registry URL (`{style}` and `{name}` are the only placeholders shadcn@4.14.1 substitutes, and it never parses the style string). Emitted as registry/styles/<style>/<name>.json for base-nova (default, @octanejs/base-ui), radix-nova and aria-nova, plus an un-styled copy of the default so a URL without {style} still resolves. Base-agnostic items (utils/types/theme/use-mobile) are emitted into every style tree because registryDependencies resolve through the same templated URL. `registry:serve` serves it locally — the port the playground's components.json always referenced but which nothing previously served. Verified end to end by installing with the real shadcn CLI: each style yields its own primitive. BASE UI base (@octanejs/shadcn/base-ui/<Family>): STARTED, 21 of 44 families and PARTIAL. `accordion` is transcribed from upstream and runs on the @octanejs/base-ui accordion primitive — the first primitive-backed family in this base. The rest are primitive-free: `alert` is transcribed from upstream's Base UI source and verified byte-identical to it; `aspect-ratio`, `card`, `empty`, `native-select`, `skeleton` and `spinner` are DERIVED from the react-aria base and are NOT yet verified against upstream, which each file's header records. Nothing primitive-backed is ported: Base UI's primitive API is structurally different from React Aria's, so it cannot be derived and needs transcribed upstream sources. The foundations now run on real Base UI primitives: `button` (Button), `input` (Field.Control), `label` (Field.Label) and `separator` (Separator), alongside plain-host `textarea` and `kbd` — Base UI ships no textarea or Keyboard primitive, so those match the radix base's shape rather than the aria base's. `separator` deliberately takes the ARIA base's class string, not the radix one: Base UI emits `aria-orientation`, so radix's `data-horizontal:` utilities would never match and the separator would render with no thickness. `button` omits the aria base's data-variant/data-size, which upstream's Base UI base also omits, and ships no LinkButton because Base UI has no Link primitive — which is why `pagination` remains unported. `alert-dialog` is transcribed from upstream and is the first portalled family here (Overlay->Backdrop, Content->Popup, Cancel->Close); it drops upstream's `cn-font-heading` on the title, matching the react-aria base, because this package ships the utilities-inlined flavor and nothing defines that semantic hook. The form controls (`checkbox`, `switch`, `radio-group`) adapt their conditional utilities rather than copying them: Base UI publishes bare `data-checked`/`data-unchecked` where radix publishes `data-state=\"checked\"`, and every Root renders a `<span role=…>` that is never `:disabled`, so `disabled:` variants become `data-disabled:`. Both dialects are pinned by tests asserting the rendered DOM carries the attributes the class strings target. The overlays (`dialog`, `popover`, `tooltip`, plus `alert-dialog`) adapt positioning: Base UI inserts a Positioner layer (Portal > Positioner > Popup) and names its transform origin `--transform-origin`, not radix's `--radix-<part>-content-transform-origin`, so a copied radix class would reference a variable nothing sets and the popup would scale from the wrong corner. Tooltip also drops radix's `data-[state=delayed-open]` utilities, which have no Base UI counterpart. `PopoverAnchor` is absent because Base UI positions via the Positioner's `anchor` prop rather than an Anchor element — recorded in tests/cross-base.test.ts.",
       "divergences": [
         "No `\"use client\"` directives anywhere: octane has no Server Components, so the RSC axis does not exist here.",
         "Refs are props (octane has no forwardRef) — upstream v4 already dropped forwardRef, so component shapes match.",
@@ -407,11 +425,11 @@
         "The Base UI base's derived components carry unverified class strings. This is tracked rather than assumed safe: the bases genuinely diverge (the radix base's Skeleton is `bg-accent` where react-aria's is `bg-muted`), so identity is verified per component. `badge` was deliberately NOT derived — the react-aria version takes `render` as a function while Base UI's takes an element, so deriving it would ship the wrong API."
       ],
       "ssr": "Tier 1 is fully server-rendered and tested (17 families through renderToString with no browser globals, including Slot-composed hosts), with hydration adoption pinned for representative shapes (plain host, Button-asChild anchor, nested Table) — zero mismatch, preserved node identity. Tier 2's portal-free components (Checkbox, RadioGroup, Switch, Slider, Tabs, Toggle, ToggleGroup, Accordion, Collapsible, AspectRatio, Progress) are server-rendered and tested. Field is SSR-safe (no portals/browser globals); Sidebar server-renders its static desktop branch (useIsMobile is false on the server; the mobile Sheet branch and tooltip portals are client-only). Portal-backed overlays/menus/Select are excluded until the radix binding supports overlay SSR; ScrollArea awaits verification of its viewport style injection on the server.",
-      "verified": "2026-08-01"
+      "verified": "2026-08-02"
     },
     {
       "name": "@octanejs/sonner",
-      "version": "0.1.18",
+      "version": "0.1.20",
       "category": "UI and interaction",
       "upstream": { "package": "sonner", "version": "2.0.7" },
       "surface": "Complete against the published `sonner@2.0.7` public surface: `Toaster`, the callable `toast` API and all methods, `useSonner`, promise lifecycle, multiple toaster targeting, stacked layout, themes, styling, focus management, timers, and swipe dismissal.",
@@ -425,7 +443,7 @@
     },
     {
       "name": "@octanejs/streamdown",
-      "version": "0.1.2",
+      "version": "0.1.4",
       "category": "Forms and content",
       "upstream": { "package": "streamdown", "version": "2.5.0" },
       "surface": "Complete Streamdown 2.5.0 root runtime and public type surface, plus the official code 1.1.1, math 1.0.2, Mermaid 1.0.2, and CJK 1.0.3 plugins exposed through ./code, ./math, ./mermaid, and ./cjk.",
@@ -438,7 +456,7 @@
     },
     {
       "name": "@octanejs/styled-components",
-      "version": "0.1.15",
+      "version": "0.1.17",
       "category": "Styling, tests, and devtools",
       "upstream": { "package": "styled-components", "version": "6.4.3" },
       "surface": "Full v6 web API, ported from the upstream 6.4.3 sources: `styled` with every HTML/SVG tag shortcut, `.attrs`/`.withConfig` chaining, `css`, `keyframes`, `createGlobalStyle`, `createTheme`, `ThemeProvider`/`ThemeContext`/`ThemeConsumer`/`useTheme`/`withTheme`, `StyleSheetManager`/`StyleSheetContext`/`StyleSheetConsumer` (targets, namespaces, vendor prefixing, stylis plugins, `shouldForwardProp`), `ServerStyleSheet`, `isStyledComponent`, `version`, and `__PRIVATE__`. Component selectors, folding (`styled(Styled)`), transient `$` props, `as`/`forwardedAs`, and the grouped CSSOM sheet engine (with upstream `data-styled` rehydration) all behave as upstream. The React Native surface and the RSC-only `stylisPluginRSC` are not ported.",
@@ -457,7 +475,7 @@
     },
     {
       "name": "@octanejs/stylex",
-      "version": "0.1.22",
+      "version": "0.1.24",
       "category": "Styling, tests, and devtools",
       "upstream": { "package": "@stylexjs/stylex", "version": "0.19.0" },
       "surface": "Full compile-time integration: re-exports the StyleX runtime API (`create`, `props`, `attrs`, `keyframes`, `defineVars`, `createTheme`) and registers as an import source; the `/vite` plugin runs the StyleX compiler over octane's compiled output and emits one static atomic stylesheet (`virtual:stylex.css`) with zero StyleX runtime in the bundle.",
@@ -470,7 +488,7 @@
     },
     {
       "name": "@octanejs/tanstack-ai",
-      "version": "0.0.17",
+      "version": "0.0.19",
       "category": "AI, data, and routing",
       "upstream": { "package": "@tanstack/ai-react", "version": "0.17.0" },
       "surface": "Ports the @tanstack/ai-react 0.17.0 hook surface (useChat, useRealtimeChat, useGeneration, useGenerateImage/Audio/Speech/Video, useTranscription, useSummarize, useAudioRecorder, useMcpAppBridge) while reusing @tanstack/ai 0.41.0 and @tanstack/ai-client 0.21.0 unchanged and mirroring all 30 @tanstack/ai-client convenience re-exports from the upstream index.",
@@ -489,7 +507,7 @@
     },
     {
       "name": "@octanejs/tanstack-devtools",
-      "version": "0.0.17",
+      "version": "0.0.19",
       "category": "Styling, tests, and devtools",
       "upstream": { "package": "@tanstack/react-devtools", "version": "0.10.7" },
       "surface": "Ports the @tanstack/react-devtools 0.10.7 public surface (the `TanStackDevtools` component plus its plugin/init types) onto Octane while reusing the framework-agnostic `@tanstack/devtools` 0.12.5 core (`TanStackDevtoolsCore`) unchanged. Plugin, title, and custom-trigger content authored as Octane elements is portaled into the containers the core creates.",
@@ -504,7 +522,7 @@
     },
     {
       "name": "@octanejs/tanstack-form",
-      "version": "0.0.17",
+      "version": "0.0.19",
       "category": "Forms and content",
       "upstream": { "package": "@tanstack/react-form", "version": "1.33.2" },
       "surface": "Ports the complete @tanstack/react-form 1.33.2 adapter surface (`useForm`, `useField`, form and field groups, hook contexts and component composition) while re-exporting @tanstack/form-core 1.33.2 unchanged and using @octanejs/tanstack-store for subscriptions.",
@@ -518,7 +536,7 @@
     },
     {
       "name": "@octanejs/tanstack-hotkeys",
-      "version": "0.0.12",
+      "version": "0.0.14",
       "category": "UI and interaction",
       "upstream": { "package": "@tanstack/react-hotkeys", "version": "0.10.0" },
       "surface": "Complete: the full upstream hook surface (`useHotkey`, `useHotkeys`, `useHeldKeys`, `useHeldKeyCodes`, `useKeyHold`, `useHotkeySequence`, `useHotkeySequences`, `useHotkeyRecorder`, `useHotkeySequenceRecorder`, `useHotkeyRegistrations`) plus `HotkeysProvider`/`useHotkeysContext`/`useDefaultHotkeysOptions`, re-exporting the framework-agnostic `@tanstack/hotkeys@0.8.0` core unchanged; store subscriptions go through `@octanejs/tanstack-store`.",
@@ -530,7 +548,7 @@
     },
     {
       "name": "@octanejs/tanstack-pacer",
-      "version": "0.0.12",
+      "version": "0.0.14",
       "category": "UI and interaction",
       "upstream": { "package": "@tanstack/react-pacer", "version": "0.22.1" },
       "surface": "Complete: every upstream hook family — debouncer (`useDebouncer`, `useDebouncedState`, `useDebouncedValue`, `useDebouncedCallback`), throttler, rate-limiter, queuer, batcher, and their async variants (async-debouncer, async-throttler, async-rate-limiter, async-queuer, async-batcher) — plus `PacerProvider`/`usePacerContext`/`useDefaultPacerOptions`, the per-instance `Subscribe` render-prop component, and the upstream subpath exports (`/debouncer`, `/async-retryer`, `/types`, `/utils`, ...), re-exporting the framework-agnostic `@tanstack/pacer@0.21.1` core unchanged.",
@@ -542,7 +560,7 @@
     },
     {
       "name": "@octanejs/tanstack-query",
-      "version": "0.1.22",
+      "version": "0.1.24",
       "category": "AI, data, and routing",
       "upstream": { "package": "@tanstack/react-query", "version": "5.101.3" },
       "surface": "Complete: 58/58 runtime exports plus the full TypeScript surface; the export surface is byte-identical to upstream in both directions (locked by test), and `@tanstack/query-core` is re-exported verbatim.",
@@ -554,7 +572,7 @@
     },
     {
       "name": "@octanejs/tanstack-router",
-      "version": "0.1.22",
+      "version": "0.1.24",
       "category": "AI, data, and routing",
       "upstream": { "package": "@tanstack/react-router", "version": "1.170.18" },
       "surface": "Octane's TanStack Router binding: typed route factories and hooks, the full Match pipeline and lifecycle, file routes with TSRX-aware generator integration, full Link navigation/preloading/masking behavior, blocking, Await/deferred hydration, scroll restoration, lazy routes, not-found handling, document/head assets, and client/server SSR entries.",
@@ -568,7 +586,7 @@
     },
     {
       "name": "@octanejs/tanstack-router-ssr-query",
-      "version": "0.0.12",
+      "version": "0.0.14",
       "category": "AI, data, and routing",
       "upstream": { "package": "@tanstack/react-router-ssr-query", "version": "1.167.1" },
       "surface": "Complete: `setupRouterSsrQueryIntegration` (the package's only export) delegating to `@tanstack/router-ssr-query-core@1.169.1`, with the QueryClientProvider Wrap composition on Octane.",
@@ -578,7 +596,7 @@
     },
     {
       "name": "@octanejs/tanstack-store",
-      "version": "0.0.17",
+      "version": "0.0.19",
       "category": "Shared state",
       "upstream": { "package": "@tanstack/react-store", "version": "0.11.0" },
       "surface": "Re-exports `@tanstack/store@0.11.0` unchanged and implements the stable React binding surface (`useSelector`, `useAtom`, `useCreateAtom`, `useCreateStore`, `createStoreContext`, and deprecated `useStore`) on Octane hooks.",
@@ -590,7 +608,7 @@
     },
     {
       "name": "@octanejs/tanstack-table",
-      "version": "0.1.20",
+      "version": "0.1.22",
       "category": "Data-heavy screens",
       "upstream": { "package": "@tanstack/react-table", "version": "9.0.0-beta.58" },
       "surface": "Complete port of the v9 adapter: the framework-agnostic `@tanstack/table-core` (constructTable + every tree-shakeable feature and row model) is reused verbatim, and the adapter — `useTable`, `Subscribe`, `flexRender`/`FlexRender`, `createTableHook`, `createTableHookContexts` — is transcribed onto octane hooks. Table state lives in TanStack Store atoms via the `coreReactivityFeature` bindings, and `useSelector` drives re-renders from the selected slice. Every store primitive (hooks, `createAtom`, `batch`, `shallow`, and the atom/store types) is imported from @octanejs/tanstack-store, which re-exports all of @tanstack/store — the binding takes no direct dependency on the store core, so there is only one path to it and atom identity cannot be split across duplicate copies.",
@@ -603,7 +621,7 @@
     },
     {
       "name": "@octanejs/tanstack-virtual",
-      "version": "0.1.20",
+      "version": "0.1.22",
       "category": "Data-heavy screens",
       "upstream": { "package": "@tanstack/react-virtual", "version": "3.14.5" },
       "surface": "Complete 1:1 port: the framework-agnostic `@tanstack/virtual-core` (Virtualizer + observers + windowing math) is reused verbatim; the React adapter (`useVirtualizer`, `useWindowVirtualizer`, incl. `useFlushSync` and the experimental `directDomUpdates` surface) is transcribed onto octane hooks, preserving upstream's force-update + flushSync-on-sync-scroll wiring and layout-effect lifecycle.",
@@ -615,7 +633,7 @@
     },
     {
       "name": "@octanejs/tauri",
-      "version": "0.0.6",
+      "version": "0.0.8",
       "category": "Desktop",
       "upstream": { "package": "@tauri-apps/api", "version": "2.11.1" },
       "surface": "Octane hooks over the framework-neutral Tauri IPC surface: useInvoke (suspending command), useInvokeState (pending/success/error with refetch), and useTauriEvent (event subscription with lifecycle-safe teardown). The rest of @tauri-apps/api — window, webview, menu, tray, path, dpi, image, and the plugin packages — is already framework-neutral and is imported directly rather than re-exported here.",
@@ -633,7 +651,7 @@
     },
     {
       "name": "@octanejs/testing-library",
-      "version": "0.1.20",
+      "version": "0.1.22",
       "category": "Styling, tests, and devtools",
       "upstream": { "package": "@testing-library/react", "version": "unpinned" },
       "surface": "`render`/`rerender`/`cleanup`/`renderHook` + `act` over the verbatim `@testing-library/dom` (every query, `screen`, `within`, `waitFor`, `fireEvent`, `prettyDOM`, `configure`), with commit timing wired to octane's scheduler via the dom-library's `eventWrapper`/`asyncWrapper` config.",
@@ -646,7 +664,7 @@
     },
     {
       "name": "@octanejs/three",
-      "version": "0.1.16",
+      "version": "0.1.18",
       "category": "Web 3D",
       "upstream": { "package": "@react-three/fiber", "version": "9.6.1 (2a528745)" },
       "surface": "Technical-preview Milestones 0–10 surface: renderer configuration and the DOM Canvas boundary, compiler ABI and renderer-local Three intrinsic types, catalogue and both extend forms, primitive/args construction, Three prop application, attachment, ordered placement/recreation, retained visibility, lifecycle/ref delivery, ownership-aware disposal, promise-returning HTMLCanvasElement and OffscreenCanvas roots, Octane act/flushSync scheduling, callback-aware unmountComponentAtNode, callable root state, scene/camera/raycaster and resize/DPR/viewport configuration, shadows/colors, one shared frame loop, controlled WebXR loop handoff, context-restore invalidation, compatible/reconstructing HMR, global effects, useStore/useThree/useFrame/useGraph and managed-instance helpers, the ray/pointer event system with DOM sources and custom managers, a keyed useLoader cache with preload/clear and GLTF graph augmentation, retained Suspense/Activity behavior, client Three-to-DOM pending/error projection, same-renderer createPortal targets with state/event enclaves and physical Three event bubbling, client-only Canvas shell streaming and production Vite/Rsbuild hydration adoption with the matching raw Rspack graph split, the explicit-target low-level DOMRegion boundary, a deterministic testing harness, an asynchronously acknowledged structured-clone transport proof, a checked public API/subpath matrix, Three r156/current compatibility lanes, a packed external consumer, real WebGL failure/recovery coverage, and semantic-checksummed renderer and shipped-size benchmarks.",
@@ -667,7 +685,7 @@
     },
     {
       "name": "@octanejs/tiptap",
-      "version": "0.0.17",
+      "version": "0.0.19",
       "category": "Forms and content",
       "upstream": { "package": "@tiptap/react", "version": "3.28.0" },
       "surface": "Complete @tiptap/react 3.28.0 adapter surface across the root and ./menus entries: @tiptap/core re-exports, editor hooks and contexts, the EditorContent portal bridge, compound Tiptap API, ReactRenderer, custom NodeView/MarkView renderers and helpers, BubbleMenu, and FloatingMenu.",
@@ -684,7 +702,7 @@
     },
     {
       "name": "@octanejs/usehooks-ts",
-      "version": "0.0.4",
+      "version": "0.0.6",
       "category": "UI and interaction",
       "upstream": {
         "package": "usehooks-ts",
@@ -702,7 +720,7 @@
     },
     {
       "name": "@octanejs/valtio",
-      "version": "0.1.6",
+      "version": "0.1.8",
       "category": "Shared state",
       "upstream": { "package": "valtio", "version": "2.3.2" },
       "surface": "The framework-agnostic `valtio/vanilla` core and `valtio/vanilla/utils` are re-exported verbatim; `useSnapshot` and the `useProxy` utility are ported to Octane.",
@@ -714,7 +732,7 @@
     },
     {
       "name": "@octanejs/visx",
-      "version": "0.1.17",
+      "version": "0.1.19",
       "category": "Data-heavy screens",
       "upstream": { "package": "@visx/visx", "version": "4.0.0 + master@485c035" },
       "surface": "Complete current Visx 4.x web runtime surface: the exact 35-namespace aggregate, all 40 feature entry points, and the eight public a11y/react, a11y/server, axis/react, scale/react, shape/react, theme/react, tooltip/floating, and voronoi/react subpaths. Released-only packages chord, delaunay, react-spring, sankey, and stats remain directly importable exactly as upstream specifies.",
@@ -730,7 +748,7 @@
     },
     {
       "name": "@octanejs/wagmi",
-      "version": "0.0.3",
+      "version": "0.0.5",
       "category": "Web3",
       "upstream": { "package": "wagmi", "version": "3.7.4" },
       "surface": "WagmiProvider and createConfig over @wagmi/core 3.6.4, with config, connection, connect, disconnect, switch-connection, switch-chain, connectors, connections, chains, balance, contract read/simulate/write, transaction send/wait, and message-signing hooks.",
@@ -746,7 +764,7 @@
     },
     {
       "name": "@octanejs/zustand",
-      "version": "0.1.22",
+      "version": "0.1.24",
       "category": "Shared state",
       "upstream": { "package": "zustand", "version": "5.0.14" },
       "surface": "Complete 1:1 port: the framework-agnostic vanilla store is reused verbatim; `create`/`useStore`, `shallow`/`useShallow`, the traditional equality-fn variants, and all middleware (persist, devtools, subscribeWithSelector, combine, redux).",