chalkbridge 1.1.2 → 1.1.4

package/CHANGELOG.md

@@ -1,5 +1,121 @@
 # chalkbridge
 
+## 1.1.4
+
+### Patch Changes
+
+- c0c4810: Declare `author` in the published manifest.
+  
+  No `repository`, `homepage` or `bugs`: the source is private, so those fields would put
+  dead links on a public npm page. The author string carries the portfolio URL, which is
+  the one destination that actually resolves for a reader.
+
+## 1.1.2
+
+**Arrows stay attached when you drag the box they point at.**
+
+Reported as arrows never being attached to icons and some rectangles: drag the shape and
+the arrow stays put, its endpoints sitting exactly where they were drawn. The dividing line
+was not the shape type — it was which arrows were *elbowed*.
+
+`arrowType: "elbow"` set upstream's `elbowed` flag, and that flag is not decoration.
+`ExcalidrawElbowArrowElement` narrows **both** bindings to `FixedPointBinding`, which adds
+a `fixedPoint`. Every binding Chalkbridge produces comes from
+`convertToExcalidrawElements`, which derives the plain `focus`/`gap` form and no
+`fixedPoint` — so an elbow arrow carried a binding the renderer could not use, and moving
+the shape did nothing to it.
+
+- **Right angles are recorded as `customData.chalk.route`**, and the arrow ships as a plain
+  multi-point arrow with `roundness: null`. The same square corners, with a binding the
+  renderer honours.
+- **Old scenes repair on contact.** An arrow still carrying the flag loses it the first time
+  anything moves under it, so nothing needs migrating.
+- The `boundElements` half was correct throughout — measured across rectangle, ellipse,
+  diamond and image, every shape listed its arrows and no arrow had an unbound end.
+
+Verified on a scene built from scratch with an icon among the shapes, then moving the icon
+and two others: all seven endpoints on moved shapes followed, each still inside the binding
+gap.
+
+## 1.1.1
+
+**Layouts that read, and arrows that meet the boxes they name.**
+
+Everything here came from one rendered diagram — nineteen boxes, twenty-four bound arrows —
+and every claim was measured before and after rather than eyeballed.
+
+- **`layout-layered` no longer scatters a graph containing a cycle.** Ranking is a
+  fixed-point iteration and a ring has no fixed point, so the loop spent its whole pass
+  budget instead of settling: nineteen boxes with four small rings reached a **maximum rank
+  of 61**, and the drawing came out **11,072 px wide with a 5,824 px hole in it**. Cycles
+  are broken before ranking now — which the function had documented since it was written
+  and no code ever did. The same boxes land **1,760 px wide in six even columns**, and the
+  dropped edge is still drawn, running backwards against the flow.
+- **Arrows route around what is in the way.** Both previous routes were computed from the
+  two boxes at the ends and nothing else, so both drew through whatever sat between them —
+  five of thirteen arrows in one sample, and two of sixteen in another *while already
+  elbowed*. `domain/scene/route.ts` searches a sparse grid with A\* and a turn penalty, and
+  only detours when the direct line actually hits something. Both samples now measure **0
+  through a box**.
+- **Every bound endpoint is a fixed point of the renderer's own rule.** Excalidraw
+  re-derives a bound endpoint on every paint from the *adjacent* point, discarding what the
+  file said — so being on the boundary was not enough. Seventeen of twenty-nine arrows
+  drifted between file and canvas, by 8 to 105 px, while every stored endpoint sat
+  correctly on its box. Now **zero of twenty-nine**.
+- **`layout-radial` and `layout-tree` are new.** Radial rings a hub; tree puts it on the
+  left and fans the rest out, which reads better whenever labels are wide, because a ring
+  long enough to seat its members crosses its own middle.
+- **`chalk_describe_scene` ends with a `layout:` line** naming which of the three the graph
+  wants and what decided it, since Claude cannot see the canvas.
+- **A resize refits its container's caption**, which was translated by the container's
+  *origin* delta — a quantity a resize does not change.
+- **A free-standing note wraps.** 261 characters came out 2,651 px wide and 25 px tall, one
+  line. `chalk_annotate` also looks for somewhere clear instead of landing on whatever ran
+  under its anchor.
+- **Arrow captions stop printing through each other**, and `layout-tree` sizes its column
+  gaps to the captions crossing them.
+
+`@dagrejs/dagre` was evaluated behind a port and not adopted: benchmarked over five graph
+shapes with edge labels given to both engines it is a tie, and 18% wider on the shape
+closest to the reported diagram. ELK is the stronger engine and is EPL-2.0, which the
+licence suite forbids by name.
+
+## 1.1.0
+
+**Diagrams that come out readable the first time.**
+
+Drawing an eight-box architecture diagram used to take about 27 minutes and end with boxes
+resized by hand and elements dragged out from under their frames. The same diagram is now
+sixteen tool calls with nothing repositioned afterwards.
+
+- **Shapes are sized to their labels.** Node has no canvas, so every shape was a flat
+  180×80 whatever it said — and a long label wrapped past the bottom of an 80 px box, where
+  the container clipped it away entirely. Advance widths for the bundled font are now
+  measured (`adr/0006`, superseding `adr/0004`).
+- **Collisions are reported instead of photographed.** `chalk_describe_scene` ends with an
+  `overlaps:` section, and every write tool returns `overlapWarning`. Previously the only
+  way to ask "did that land badly?" was a rendered image.
+- **Frames follow what they hold.** A frame was sized to its contents once, when it was
+  created; every later move slid the children out and left the box behind.
+- **Icons belong to a box.** `chalk_place_icon` takes `attachTo` and `placement`, so an
+  attached icon travels with its element through every layout.
+- **Elbow arrows actually bend**, and arrows leaving the same face of a box fan out rather
+  than stacking in one lane.
+- **`layout-layered` leaves room for what it draws.** Edges spanning more than one rank get
+  a reserved corridor, and the gap between ranks is sized to the widest caption crossing it.
+
+## 1.0.4
+
+**Icons that render, and arrows that will bind to them.**
+
+- **An icon reached the canvas as an invisible element.** The image and its file have to
+  land in the same commit; they did not, so the element was there and nothing was drawn.
+- **An arrow would not bind to an icon.** Upstream's binding switch covers exactly
+  `rectangle | ellipse | diamond`, and Chalkbridge produces three types it does not —
+  `image`, `embeddable`, `frame`. Each now gets a rectangular stand-in during expansion, so
+  the binding is still *derived* rather than hand-written (invariant 16).
+- A README that explains what the thing is before explaining how to build it.
+
 ## 1.0.3
 
 **An upgrade now actually arrives, a bridge can be stopped, and it ends when you are

package/dist/cli.js

@@ -5663,7 +5663,7 @@ function readEnv(source) {
 }
 
 // src/composition/container.ts
-var PACKAGE_VERSION = "1.1.2";
+var PACKAGE_VERSION = "1.1.4";
 function readRuntime() {
   return {
     env: process.env,

package/package.json

@@ -1,9 +1,10 @@
 {
   "name": "chalkbridge",
-  "version": "1.1.2",
+  "version": "1.1.4",
   "type": "module",
   "description": "Self-hosted Excalidraw canvas for Claude Code to draw and reason on architecture diagrams.",
   "license": "MIT",
+  "author": "Manideep Kadambari (https://phoenixcodes.dev)",
   "keywords": [
     "excalidraw",
     "mcp",