v1.1.0

Added

• @devslab/editor-ruler-summernote — new package: a Summernote
  plugin (summernote >= 0.8). Register with defineRulerPlugin($) and add
  'ruler' to toolbar for the ruler-icon dropdown (Show/Hide, Vertical
  Ruler, Lock/Clear Guides, cm/inch/px). Options live under the ruler key:
  enabled, visible, unit, vertical, verticalGutter, guides,
  guideSnap, language.

  Summernote is direct-DOM like Froala, so this adapter reuses the same
  behavior rather than approximating it: whole-table indent and column-width
  markers work here too — the first adapter besides Froala to have them.
  Commits go through Summernote's own editor.afterCommand, which is the
  method that calls history.recordUndo(), so a whole drag gesture is exactly
  one undo step.

• Landing page gains a Summernote demo tab (jQuery and Summernote lazy-load
  from a CDN only when the tab is opened) and a Summernote integration
  section; examples/summernote added for one-click StackBlitz.

Changed

• Docs that counted adapters ("all three", "the four packages") are now
  count-free or corrected, and the feature split is stated where it matters:
  the vertical ruler and guides are on every adapter, while whole-table indent
  and column markers are on the direct-DOM adapters (Froala, Summernote).
• README CDN pins bumped @1.0 → @1.1.

v1.0.1

Fixed

• The 1.0.0 stability statement only reached the root README, so the npm
  pages — where people actually decide whether to adopt — announced 1.0.0
  without saying what "stable" covers. Each package README now carries the
  commitment up front and links to the full scope. Docs-only release
  (republished because npm versions are immutable).

v1.0.0

Stable. The API is now under semantic versioning: breaking changes to
the documented public surface require a major release. Nothing about the
ruler's behavior changed in this release — upgrading from 0.16.0 needs no
code changes.

What the commitment covers:

• Every symbol exported from the four packages' entry points, and the
  options/config each adapter accepts.
• The --edr-* CSS custom properties used for theming.
• The output contract: indentation is written as plain inline CSS
  (margin-left / margin-right / text-indent in px), so exported HTML
  stays portable.

What it deliberately does not cover, so these can still improve:

• The injected DOM structure and internal class names (.edr-vwrap,
  .edr-froala-vmount, …). Theme with the CSS variables, not by
  selector-matching internals.
• Anything marked @internal.

Added

• @devslab/editor-ruler-tiptap — RulerStorage is now exported. It is
  the type of editor.storage.editorRuler, which the README documents as
  public API, but consumers previously had no way to name it.
• @devslab/editor-ruler-froala — FroalaRulerApi is now exported, for
  the same reason: it types editor.ruler.

Changed

• @devslab/editor-ruler-tiptap — the implementation-only fields
  (setVerticalVisible, cleanup) were moved off the public RulerStorage
  type. They were never meant to be called from outside, and freezing them
  into a stable contract would have blocked internal refactors. Runtime
  behavior is unchanged.

Fixed

• The examples/ StackBlitz projects still pinned @devslab/editor-ruler*
  at ^0.10.0 / ^0.11.0, so every one-click demo linked from the READMEs
  and the landing page installed a build with no vertical ruler, no gutter,
  and no CKEditor 5 toolbar dropdown. Pins now track the released version.
  (No package changed, so no republish is needed — StackBlitz reads main.)

Changed

• Versions are now derived, not hand-edited: scripts/sync-versions.mjs
  propagates packages/editor-ruler/package.json's version to the sibling
  packages, the examples/ pins, and the README CDN pins. pnpm sync:versions writes, pnpm check:versions reports; the check runs inside
  verify, on every CI run, and thus in publish.yml before anything is
  published — stale references now fail the build instead of shipping.

v0.16.0

Added

• Vertical ruler on every adapter — the core createVRuler strip was
  only wired into Froala; now Tiptap and CKEditor 5 mount it too (flex-wrap
  the editable with the 23px strip beside it, exactly the Froala mechanic),
  including the gutter behavior and vertical-guide dragging:
  • @devslab/editor-ruler-tiptap — vertical / verticalGutter options
    plus showVerticalRuler / hideVerticalRuler / toggleVerticalRuler
    commands; strip handle at editor.storage.editorRuler.vruler, state at
    …verticalVisible.
  • @devslab/editor-ruler-ckeditor5 — editorRuler.vertical /
    editorRuler.verticalGutter config, showVRuler() / hideVRuler() /
    toggleVRuler() / isVRulerVisible() plugin API, and a Vertical
    Ruler entry in the editorRuler toolbar dropdown (ko/en).
  • verticalGutter: true reserves the strip's 23px column up front
    (scrollbar-gutter: stable style) so toggling never reflows the
    content — same option Froala got in 0.13.0.

Changed

• README CDN pins bumped @0.15 → @0.16.

v0.15.0

Added

• Start-hidden parity across adapters — the Froala-only rulerVisible
  idea (0.14.0) now exists everywhere:
  • @devslab/editor-ruler-tiptap — visible option (default true) plus
    showRuler / hideRuler / toggleRuler commands; current state at
    editor.storage.editorRuler.visible. Typed via Tiptap Commands /
    Storage module augmentation.
  • @devslab/editor-ruler-ckeditor5 — editorRuler.visible config
    (default true); the existing show()/hide()/toggle() plugin API and
    toolbar dropdown bring it up later. The editorRuler config key is now
    typed via EditorConfig module augmentation.
  • Note: the vertical ruler (and its rulerVerticalGutter) remains
    Froala-only for now.
• Landing page gains a CKEditor 5 연동 section (it had Froala and Tiptap
  but never CKEditor 5) and documents the new visibility controls.

Changed

• README CDN pins bumped @0.14 → @0.15.

v0.14.0

Added

• @devslab/editor-ruler-froala — rulerVisible option (default true):
  controls whether the horizontal ruler starts visible with the editor.
  rulerVisible: false starts it hidden while keeping the plugin and its
  toolbar commands alive, so users toggle it on when they want it — the
  start-state counterpart to rulerVertical, completing the symmetry
  (rulerEnabled: false still disables the plugin entirely).

Changed

• README CDN pins bumped @0.13 → @0.14.

v0.13.0

Added

• @devslab/editor-ruler-froala — rulerVerticalGutter option (default
  false): reserves the vertical ruler's 23px column from init, like CSS
  scrollbar-gutter: stable. Without it, showing the vertical ruler narrows
  the writable area by 23px (the strip has to take its space from somewhere,
  and the horizontal ruler correctly re-reads the narrower width — e.g.
  820 → ~797); with the gutter on, that space is always reserved, so toggling
  the vertical ruler never reflows the content. Prompted by a field report of
  the width shift — thank you!

Changed

• README CDN pins bumped @0.12 → @0.13.

v0.12.3

Fixed

• @devslab/editor-ruler-froala — the vertical ruler sized itself to
  .fr-element (which grows with content) instead of .fr-wrapper (the
  fixed-height scroll container), so with a fixed editor height and long
  content the strip outgrew the visible editor. It is now capped at the
  wrapper's viewport height, falling back to the content height when the
  wrapper has no fixed layout (heightMin-only setups, jsdom). Reported by
  a user running a fixed-height Froala — thank you!

v0.12.2

Fixed

• README CDN examples still pinned @0.1 from the first release — updated to
  the current minor (@0.12) across all package READMEs, and the landing
  page's version-pinning note now auto-fills both the exact version and the
  minor pin at build time so it can't go stale again. Docs-only release
  (republished so npmjs shows the corrected READMEs).

v0.12.1

Changed

• Search discoverability: compound keywords added to every package
  (froala-ruler, tiptap-ruler, ckeditor-ruler, horizontal-ruler, …)
  and the landing site now ships robots.txt + sitemap.xml. No code
  changes.