@creator-notes/cnotes 0.35.1 → 0.40.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -264,6 +264,16 @@ cnotes canvas add-node <canvasId> --note <noteId> [--x <n>] [--y <n>] # (despi
264
264
  cnotes canvas add-text <canvasId> --content "<markdown>" [--size small|medium|large] [--color "<hex>"] [--x <n>] [--y <n>] # inline (short only)
265
265
  cnotes canvas add-text <canvasId> --content-file <path.md> [--size small|medium|large] [--color "<hex>"] [--x <n>] [--y <n>]
266
266
  cnotes canvas add-richtext ... # DEPRECATED alias of add-text (identical flags). Use add-text.
267
+ # THE BOX IS DERIVED, NOT CHOSEN. You pick x/y; the server picks the size. WIDTH is the
268
+ # --size preset: small 560px, medium 1120px, large 1680px. HEIGHT follows the content, and
269
+ # there is no in-place content update: replacing a text element = remove-node + add-text,
270
+ # and the new card is exactly as tall as its new content. So both halves bite — columns
271
+ # pitched for a small card while the items are medium overlap by 460px each, and longer
272
+ # copy at the same x/y runs over whatever sits below. The write still succeeds either way.
273
+ # When it happens the response carries layoutWarning naming the run-over nodes (CLI also
274
+ # prints it to stderr): reflow what's below (bulk-move / arrange), or hand the whole block
275
+ # to `canvas place` and let the solver pack it, then re-check with canvas get. Never treat
276
+ # "write succeeded" as "layout is fine" after a size bump or a content change.
267
277
  # A list item is a COLLECTION OF NOTES, not a text block. --description is a one-line FRAME;
268
278
  # the content is the member notes you pass to --notes. If you have N distinct things
269
279
  # (questions, risks, options), create N notes first — pick the right type, e.g. a Question
@@ -870,6 +880,8 @@ The schema is strict: an unknown or typo'd key anywhere in the doc (e.g. `gapp`,
870
880
 
871
881
  Leaf enums (exact values): richtext `size` = `small` | `medium` | `large`, `colorHex` = a saturated hex (omit for no background); list `viewMode` = `list` | `grid`, list `size` = `sm` | `md` | `lg` | `xl`.
872
882
 
883
+ A richtext `size` is not a hint — it IS the width the card paints: `small` 560px, `medium` 1120px, `large` 1680px, with the height following the content. `place` measures that box for you, which is the whole reason to prefer it over hand-picked coordinates: pitch a row of columns for `small` and then send `medium` items and every card runs 460px into its neighbour.
884
+
873
885
  #### Section container (frame WITH content — preferred)
874
886
 
875
887
  Beyond the fixed-size leaf above, `section` is also a CONTAINER: wrap any