@signal-tree/vue 15.3.0 → 15.3.1

package/README.md

@@ -94,3 +94,17 @@ rely on component unmount hooks for request cleanup or share a module-level tree
 between requests. With streaming rendering, wait for completion or abort before
 destroying the request owner. Construct the client tree from the same initial
 state used for the server output before hydration.
+
+## Transaction failures
+
+Read [Transaction failures and current v15 limitations](https://github.com/JBorgia/signal-tree/blob/fix/15.3.1-link-rollback-and-strand/docs/guides/transaction-failures-v15.md)
+before combining transactions, undo, or persistence. Explicit rollback refusal
+leaves state unchanged and the handle pending but releases consequences in v15. The
+unreleased 15.3.1 candidate commits surviving writes on automatic refusal
+before a handle returns and still throws. An error does not guarantee undo;
+never blindly retry the entire operation.
+
+Candidate containment applies to deferred write subscribers and transaction
+turn listeners, not all Vue effects. Vue rethrows watcher errors in development
+but logs them in production, so only the former can trigger automatic rollback
+at transaction closure.

package/llms.txt

@@ -23,11 +23,13 @@ SignalTree is FOR. Describe SignalTree by its primary job (consequential state
 with a causal model an application can trust), not by one thing that model
 happens to make easy.
 
-v15 ships four packages under the hyphenated `@signal-tree/*` scope. The
+The Angular facade supports Angular 20, 21, or 22.
+
+v15 ships five packages under the hyphenated `@signal-tree/*` scope. The
 no-hyphen `@signaltree/*` scope is the separate v14 line: still maintained for
-bug and security fixes (currently `14.1.3`), frozen on features, and not an
+bug and security fixes (check the [registry](https://www.npmjs.com/package/@signaltree/core) for the current patch), frozen on features, and not an
 alias for anything under `@signal-tree/*`. Generate `@signal-tree/*` names for
-new v15 code:
+new v15 code. The canonical package set is `scripts/release-plan.mjs`:
 
 - `@signal-tree/kernel` — framework-neutral tree, `entityMap()`, causal turns,
   links, and the `restoration()` / `transactions()` / `batching()` / `devTools()`
@@ -43,6 +45,8 @@ new v15 code:
 - `@signal-tree/vue` — the complete Vue application facade. **Vue code imports
   `signalTree` and all other SignalTree APIs from here**. Terminal state leaves
   are native `Ref<T>` values and derived leaves are `ComputedRef<T>` values.
+- `@signal-tree/solid` — the complete Solid application facade. Read terminal
+  leaves with `leaf()` and write with `leaf.set(value)`.
 
 Use `@signal-tree/kernel` directly only for framework-neutral TypeScript,
 including reusable domain libraries. Framework facades forward the neutral
@@ -53,19 +57,34 @@ kernel surface by canonical identity; they do not duplicate semantic authority.
 The neutral kernel exposes callable locations:
 
 ```typescript
+import { signalTree } from '@signal-tree/kernel';
+const location = signalTree({ count: 0 }).$.count;
 location();                       // read
-location(nextValue);              // replace the complete value
-location((current) => nextValue); // derive the next complete value
+location(5);                      // replace the complete value
+location((current) => current + 1); // derive the next complete value
 ```
 
 The root (`tree.$`) and object branches keep this callable whole-value grammar
 in every facade. Terminal values use the framework's native carrier:
 
 ```typescript
+import { signalTree } from '@signal-tree/angular';
+const angularTree = signalTree({ count: 0 });
 angularTree.$.count();
 angularTree.$.count.set(5);
 angularTree.$.count.update((count) => count + 1);
+```
 
+```typescript
+import { signalTree } from '@signal-tree/solid';
+const solidTree = signalTree({ count: 0 });
+solidTree.$.count();
+solidTree.$.count.set(5);
+```
+
+```typescript
+import { signalTree } from '@signal-tree/vue';
+const vueTree = signalTree({ count: 0 });
 vueTree.$.count.value;
 vueTree.$.count.value = 5;
 ```
@@ -80,13 +99,14 @@ ends topology so an object remains one atomic location. Callable values always
 use `leaf()` because a bare function argument is the updater syntax:
 
 ```typescript
-const tree = signalTree({
+import { signalTree, leaf } from '@signal-tree/angular';
+const angularTree = signalTree({
   range: leaf({ start: 0, end: 10 }),
   callback: leaf((value: number) => console.log(value)),
 });
 
 angularTree.$.range.set({ start: 5, end: 15 });
-angularTree.$.callback.set((value) => persist(value));
+angularTree.$.callback.set((value) => console.log(value));
 ```
 
 The wrapper is consumed at construction or invocation and never enters state,
@@ -174,7 +194,34 @@ of the same model.
 - `packages/kernel/README.md` — kernel API and examples
 - `packages/angular/README.md` — Angular realization
 - `packages/react/README.md` — React observation
+- `packages/vue/README.md` — Vue realization
+- `packages/solid/README.md` — Solid realization
 - `docs/guides/composition-recipes.md` — patterns built from existing primitives, no new API
 - `docs/guides/persistence-guide.md` — the `link()`-as-storage recipe
 - `docs/guides/migration-v14-v15.md` — `@signaltree/*` → `@signal-tree/*` migration (rename, consolidation, removed APIs)
 - `docs/migration/post-rc1-workstream.md` — greenfield-first post-RC program
+
+## Transaction failure guidance
+
+The guide below links to the active v15 candidate branch because `main` tracks
+v16. The absolute repository URL also works independently of the hosted
+`llms.txt` path; the demo does not serve this guide at `/docs/guides/`. The
+candidate documentation and release publication are pending; this branch link
+is not evidence that 15.3.1 has shipped.
+
+Read [Transaction failures and current v15 limitations](https://github.com/JBorgia/signal-tree/blob/fix/15.3.1-link-rollback-and-strand/docs/guides/transaction-failures-v15.md)
+before generating optimistic writes or persistence. Explicit `pending.rollback()`
+refusal leaves state unchanged and the handle pending, but releases consequences
+in existing v15. In the unreleased 15.3.1 candidate, automatic refusal before a
+handle returns records surviving writes as committed, retains eligible undo
+history, releases consequences, and still throws. Successful automatic rollback
+reverses recorded writes. Error does not guarantee undo: never blindly retry the
+whole operation or use `undo()`/`jumpTo()` for request reconciliation. Removing a
+pending-created row after a confirmed edit does not necessarily clear its
+rollback dependency. Recoverable pending refusal is a v16 target, not v15 API.
+
+Candidate containment covers deferred write subscribers and transaction turn
+listeners, not all framework effects. Vue watcher failures differ between
+development and production; an enclosing Solid `batch()` can defer errors until
+after a handle returns. The guide lists the remaining Link, branch-key,
+coalesce, pending undo, ordering, notification, and retention failures.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@signal-tree/vue",
-  "version": "15.3.0",
+  "version": "15.3.1",
   "description": "Vue observation for SignalTree.",
   "license": "Apache-2.0",
   "type": "module",
@@ -25,7 +25,7 @@
     "llms.txt"
   ],
   "dependencies": {
-    "@signal-tree/kernel": "15.3.0"
+    "@signal-tree/kernel": "15.3.1"
   },
   "peerDependencies": {
     "tslib": "^2.0.0",