chore(release): v1.6.0

One release rather than two. 1.6 and 1.7 were separate lines on the roadmap,
but the code for both is on main and cannot be split without reverting — and a
1.6 tarball containing an editing API that only 1.7's changelog described
would be worse than merged numbering. So 1.6 is both, and the roadmap says so.

Also fixes something the code panel never did: the VIEW knobs were not in it.
Turn the connector to Straight, drag the indent, tick Colour by branch — the
snippet described the EXAMPLE rather than the chart in front of you. It reads
the live layout settings now, which is how edgeStyle became visible there at
all. Verified in the browser: `edgeStyle: 'spoke'` appears in the snippet the
moment the control moves.

That gap was the same one reported for drag-and-drop a few releases ago, in a
different corner.

Author: n1crack

.changeset/a-rule-of-your-own.md

@@ -1,5 +1,30 @@
 # @klad/engine
 
+## 1.6.0
+
+### Patch Changes
+
+- 57142dd: Two bugs where a source index outlived the tree it meant something in.
+
+  **Isolating a branch, then changing the data, isolated the wrong branch.**
+  `isolate` held a source index, and a source index means nothing once the tree
+  is rebuilt — so a drag-and-drop, a lazily-loaded branch, a cap change or an
+  edit left the chart framing whichever node inherited the old slot, and
+  reporting that node's id back through `getState().isolated`. It is held by id
+  now and resolved on every rebuild, alongside the filter and cap masks that were
+  already re-derived for exactly this reason. If the isolated node leaves the
+  tree, the chart shows the whole tree rather than an arbitrary branch.
+
+  **A rebuild that both reordered the data and took nodes out of view could crash
+  the relayout.** The engine's transition builder reads the previous tree in the
+  old index space and the maps it looks things up in are keyed by the new one.
+  Mixing them is invisible until both happen at once — a drop reorders but
+  nothing leaves the view, a collapse has things leave but does not reorder —
+  and then a fading node is looked up under another node's key: usually it fades
+  from the wrong place, and when the key is missing entirely the box comes back
+  `undefined` and reading it took the whole frame down. Isolating and then
+  reconciling does both.
+
 ## 1.5.1
 
 ### Patch Changes

.changeset/a-way-back.md

@@ -1,6 +1,6 @@
 {
   "name": "@klad/engine",
-  "version": "1.5.1",
+  "version": "1.6.0",
   "description": "Klad — a canvas tree engine for tens of thousands of nodes. Tiered, file, radial and sunburst layouts, with a DOM overlay for your own node content. Frameworkless.",
   "keywords": [
     "tree",

.changeset/data-that-keeps-arriving.md

@@ -9,7 +9,7 @@
  * asserts the two agree, in the release path, where a mismatch can still be
  * fixed without another publish.
  */
-export const VERSION = '1.5.1'
+export const VERSION = '1.6.0'
 
 export type { NodeData, Warning, WarningCode, Size, Bounds } from './types.js'
 export type { Tree, SubtreeStats } from './tree.js'