@novoagents/react 0.3.0-alpha.2 → 0.3.0-alpha.21

package/CHANGELOG.md

@@ -1,85 +1,37 @@
 # Changelog
 
-## Unreleased
+## 0.3.0-alpha.21 - 2026-08-17
 
-## 0.3.0-alpha.2 - 2026-07-28
+- Companion release for `novoagents` 0.5.0-alpha.19. The hook runtime is
+  unchanged; the package carries an exact peer on the SDK version whose browser
+  run controller it binds.
 
-- Companion release for `novoagents` 0.5.0-alpha.2 (stream schema v4:
-  `data-novo-step-terminal` splits overflow reporting into `truncated` for
-  clipped text and `messagesOmitted` for dropped message arrays, and
-  `artifactRef` is removed). The hook source is unchanged; the exact SDK peer
-  moves to the v4 contract, and the packed tarball check now verifies the
-  installed wire contract against the workspace artifact instead of a pinned
-  revision literal.
+## 0.3.0-alpha.20 - 2026-08-16
 
-## 0.3.0-alpha.1 - 2026-07-28
+- Companion release for `novoagents` 0.5.0-alpha.18. The hook runtime is
+  unchanged; the package carries an exact peer on the SDK version whose browser
+  run controller it binds.
+- `0.3.0-alpha.19` was published through npm instead of pnpm and therefore
+  preserved the workspace protocol in its peer metadata. It was never tagged
+  `latest`; use this build instead.
 
-- Companion release for `novoagents` 0.5.0-alpha.1 (stream schema v3:
-  `platform_error` replaces the three engine-named terminal reasons, terminal
-  errors carry `retryable`, and the SDK ships the generated
-  `novoagents/wire-contract.json` compatibility manifest). The hook source is
-  unchanged; the exact SDK peer moves to the v3 contract, and the packed
-  tarball check verifies the installed wire contract's protocol revision.
+## 0.3.0-alpha.18 - 2026-08-12
 
-## 0.2.0-alpha.7 - 2026-07-16
+- Companion release for `novoagents` 0.5.0-alpha.17. The hook runtime is
+  unchanged; the package carries an exact peer on the SDK version whose browser
+  run controller it binds.
 
-- Companion release for `novoagents` 0.4.0-alpha.7. The hook source remains
-  unchanged; its exact SDK peer moves with the App-only GitHub contract.
-- The workspace declares `novoagents` as a development dependency so a clean
-  CI install can compile the peer-backed `novoagents/browser` imports;
-  consumers still receive only the exact peer dependency, never a nested SDK.
+## 0.3.0-alpha.17 - 2026-08-12
 
-## 0.2.0-alpha.6 - 2026-07-16
+- Companion release for `novoagents` 0.5.0-alpha.16. The hook runtime is
+  unchanged; the package carries an exact peer on the SDK version whose browser
+  run controller it binds.
 
-- Companion release for `novoagents` 0.4.0-alpha.6. The hook source is
-  unchanged; publishing the React package alongside the SDK keeps its exact
-  `novoagents` peer on the current canonical browser-controller contract.
+## 0.3.0-alpha.16 - 2026-08-12
 
-## 0.2.0-alpha.5 - 2026-07-16
+- Companion release for `novoagents` 0.5.0-alpha.15. The hook runtime is
+  unchanged; the package carries an exact peer on the SDK version whose browser
+  run controller it binds.
 
-- Moves the type-only `novoagents` relationship from a runtime dependency to
-  an exact peer dependency on 0.4.0-alpha.5. The hooks still require the
-  matching canonical browser-controller contract, while package managers now
-  install one app-owned SDK copy instead of retaining an older nested copy or
-  requiring a consumer override.
-
-## 0.2.0-alpha.4 - 2026-07-16
-
-- Superseded by 0.2.0-alpha.5. The alpha.4 registry artifact was published from
-  the workspace source with npm, which retained the internal `workspace:*`
-  peer specifier instead of pnpm's exact-version rewrite. It is not assigned a
-  dist-tag and should not be installed.
-
-## 0.2.0-alpha.3 - 2026-07-15
-
-- `useNovoRun` exposes the latest provider-neutral thinking/activity snapshot
-  on `state.progress`, or `null` after answer, pause, restart, or terminal
-  boundaries. When safe readable reasoning is available, the snapshot may be a
-  short reasoning-derived summary; it never contains raw reasoning. The hook
-  inherits the canonical browser reducer behavior from `novoagents`.
-
-## 0.2.0-alpha.2 - 2026-07-15
-
-- Updates the packed `novoagents` dependency to 0.4.0-alpha.2, so React run
-  hooks consume targeted `data-novo-model-step-restart` retractions through the
-  canonical browser controller.
-
-## 0.2.0-alpha.1 - 2026-07-14
-
-- `useNovoRun` normalizes `enabled` and `runKey` before its dependency arrays,
-  so identity toggles (`enabled: undefined <-> true`, `runKey: undefined <->
-  null`) no longer dispose and recreate a live controller.
-- Picks up `novoagents` 0.4.0-alpha.1 controller fixes: fatal (non-retried)
-  initial-connect errors, per-drop `transportError` publication, a final
-  `disposed` snapshot published before listeners detach, and interaction-race
-  hardening.
-
-## 0.2.0-alpha.0 - 2026-07-14
-
-- Replaced the alpha store/transport hooks with effect-owned bindings over the
-  canonical `NovoRunController`.
-- Added `useNovoRunSelector` and controller-bound `useNovoInteractions`.
-- Fixed run-key/unmount leaks with stop + disposal and generation-fenced core
-  consumption.
-- Added client entry directives, `sideEffects: false`, React 18/19 peer range,
-  SSR snapshots, and Strict Mode lifecycle coverage.
+Earlier prerelease builds are unsupported. Their immutable package artifacts
+and Git history retain their release records.

package/README.md

@@ -48,26 +48,3 @@ If your host persists interaction requests independently of the stream,
 configure `interactionDiscovery: { list, intervalMs? }` on the controller.
 Discovery is generation-fenced, runs while the SSE connection is idle, and
 reconciles DB-only requests into the same canonical pending queue.
-
-## Migrating from 0.1.0-alpha.0
-
-- `createNovoRunStore` → `createNovoRunController` from `novoagents/browser`.
-- `BrowserRunTransport` → `NovoRunEventSource`; use
-  `createNovoHttpRunSource` for fetch/SSE routes.
-- `useNovoRun({ transport })` →
-  `useNovoRun({ createController, runKey })`.
-- `useNovoInteractions({ endpoint, run })` → configure the controller's
-  interaction transport, then call `useNovoInteractions(run.controller)`.
-- `resolveNovoInteractions` → `createHttpInteractionResolveTransport`.
-
-There are no compatibility aliases for the alpha API.
-
-## Publishing
-
-After publishing `novoagents`, publish with
-`pnpm publish --access public --tag alpha`: pnpm rewrites the `workspace:*`
-peer dependency on `novoagents` to the exact packed version. Publish the two
-alpha packages in lockstep so both `alpha` tags always form one compatible
-browser-controller installation. Do not publish the workspace source with
-`npm publish`; npm does not perform pnpm's workspace-protocol rewrite. Verify
-the registry peer metadata before moving `latest`.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@novoagents/react",
-  "version": "0.3.0-alpha.2",
+  "version": "0.3.0-alpha.21",
   "description": "Browser-safe React hooks for Novo Agents streams and interactions.",
   "license": "UNLICENSED",
   "type": "module",
@@ -24,18 +24,18 @@
   },
   "peerDependencies": {
     "react": "^18.0.0 || ^19.0.0",
-    "novoagents": "0.5.0-alpha.2"
+    "novoagents": "0.5.0-alpha.19"
   },
   "devDependencies": {
-    "@types/react": "19.2.17",
-    "@types/react-dom": "19.2.3",
-    "happy-dom": "20.11.1",
-    "react": "19.2.7",
-    "react-dom": "19.2.7",
+    "@types/react": "19.2.18",
+    "@types/react-dom": "19.2.4",
+    "happy-dom": "20.11.2",
+    "react": "19.2.8",
+    "react-dom": "19.2.8",
     "typescript": "6.0.3",
-    "vite": "8.1.5",
-    "vitest": "5.0.0-beta.6",
-    "novoagents": "0.5.0-alpha.2"
+    "vite": "8.2.1",
+    "vitest": "5.0.0-rc.1",
+    "novoagents": "0.5.0-alpha.19"
   },
   "scripts": {
     "build": "tsc -p tsconfig.json && node scripts/check-dist.mjs",