docs: say that Solid Objects Pro ships for Node.js

CHANGELOG.md

@@ -1,5 +1,12 @@
 # Changelog
 
+## 0.17.5 - 2026-10-09
+
+- Correct `docs/agents.md` and `docs/fit.md`: Solid Objects Pro ships for
+  Node.js as `@solidobjects/pro` from the private registry at
+  <https://solidobjects.pro>, beside the Rails gem. The docs said that its
+  Node build was in development.
+
 ## 0.17.4 - 2026-10-08
 
 - Step 12 of `docs/agents.md` now says plainly that every authorization

docs/agents.md

@@ -19,27 +19,27 @@ Use Solid Objects only if you can answer yes to most of these questions:
 
 Select a simpler tool in these cases:
 
-| Requirement                                    | Use instead                                                                                                 |
-| ---------------------------------------------- | ----------------------------------------------------------------------------------------------------------- |
-| The invariant fits in one request              | A transaction, a constraint, or `SELECT ... FOR UPDATE`                                                     |
-| CPU-intensive or parallel work                 | `worker_threads` or a worker pool. An actor serializes work                                                 |
-| Thousands of writes for each second to one key | A counter column or a cache. Solid Objects Pro covers this case for Rails; its Node build is in development |
-| One atomic change across two actor identities  | One SQL transaction on normal tables                                                                        |
-| Exactly-once calls to an external API          | Not available from any actor library. Use provider idempotency keys                                         |
-| Replay of named workflow steps from a step log | A durable execution engine, such as DBOS or Temporal                                                        |
+| Requirement                                    | Use instead                                                                        |
+| ---------------------------------------------- | ---------------------------------------------------------------------------------- |
+| The invariant fits in one request              | A transaction, a constraint, or `SELECT ... FOR UPDATE`                            |
+| CPU-intensive or parallel work                 | `worker_threads` or a worker pool. An actor serializes work                        |
+| Thousands of writes for each second to one key | A counter column, a cache, or Solid Objects Pro, which ships for Node.js and Rails |
+| One atomic change across two actor identities  | One SQL transaction on normal tables                                               |
+| Exactly-once calls to an external API          | Not available from any actor library. Use provider idempotency keys                |
+| Replay of named workflow steps from a step log | A durable execution engine, such as DBOS or Temporal                               |
 
 The full list is in [Choosing Solid Objects](fit.md). The category guide is
 [Virtual actors in TypeScript and Node.js](virtual-actors.md).
 
 ## 2. Package identity
 
-| Item               | Value                                                                                                 |
-| ------------------ | ----------------------------------------------------------------------------------------------------- |
-| npm package        | `solid-objects`                                                                                       |
-| Repository         | <https://github.com/cardmagic/solid-objects-js>                                                       |
-| Website            | <https://solidobjects.dev/js>                                                                         |
-| Ruby on Rails gem  | `solid_objects`, a separate implementation of the same model                                          |
-| Commercial package | `@solidobjects/pro`, a separate paid package in development. The open-source package does not need it |
+| Item               | Value                                                                                                                                          |
+| ------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------- |
+| npm package        | `solid-objects`                                                                                                                                |
+| Repository         | <https://github.com/cardmagic/solid-objects-js>                                                                                                |
+| Website            | <https://solidobjects.dev/js>                                                                                                                  |
+| Ruby on Rails gem  | `solid_objects`, a separate implementation of the same model                                                                                   |
+| Commercial package | `@solidobjects/pro`, a separate paid package from the private registry at <https://solidobjects.pro>. The open-source package does not need it |
 
 Solid Objects is not SolidJS and has no relation to it. It is not affiliated
 with Cloudflare.

docs/fit.md

@@ -42,8 +42,8 @@ history, and no actor-state migration contract.
   fits, because each check is one durable ordered message. For the high-QPS
   limiter, see [Solid Objects Pro](https://solidobjects.pro/): grouped commits
   coalesce concurrent writes into one insert, and ephemeral operations keep
-  loss-tolerant calls out of the durable journal. It ships for the Rails gem
-  today, and the Node build is in development. Distributed per-actor rate
+  loss-tolerant calls out of the durable journal. It ships for Node.js as
+  `@solidobjects/pro` and for the Rails gem. Distributed per-actor rate
   limits, global admission control, and cache-capacity eviction are answered
   there rather than in this runtime, and are not open roadmap items here.
 - Durable workflow replay across named steps is more important than a mutable

package.json

@@ -1,6 +1,6 @@
 {
   "name": "solid-objects",
-  "version": "0.17.4",
+  "version": "0.17.5",
   "description": "SQL-backed virtual actor library for TypeScript and Node.js, with durable state, ordered operations, and automatic activation on SQLite, PostgreSQL, or MySQL",
   "type": "module",
   "license": "MIT",

src/version.ts

@@ -1 +1 @@
-export const VERSION = "0.17.4"
+export const VERSION = "0.17.5"