yrby 0.2.0-arm64-darwin

checksums.yaml

@@ -0,0 +1,7 @@
+---
+SHA256:
+  metadata.gz: 7e301d4bf70b08390eba5ac7edc02781c47edf98b688725fa639db1ebee99e51
+  data.tar.gz: b23e2aba79d1f3609f2421a82757359f636b6e376764891f5349cec862eef97e
+SHA512:
+  metadata.gz: '08444d03a50bddfa51cde2987c750961eb26e6b226d5194608a92413de3abcd7ffe596814a81e495f667ab9addcff6d5fe5eba90f63dbbc85a78b78c5ba3f1ed'
+  data.tar.gz: d0eda3683c1c6a61f152e109ad90eb5e9b1beb64cf6677d099b408512bde8e9627f6efb3ef8e93e4c51c32d94c6d91c04c503fd649f527b8169e8a77687b6a39

data/CHANGELOG.md

@@ -0,0 +1,30 @@
+# Changelog
+
+All notable changes to this project are documented here. The format is based on
+[Keep a Changelog](https://keepachangelog.com/en/1.1.0/), and this project aims
+to follow [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
+
+## [Unreleased]
+
+## [0.2.0] - 2026-06-28
+
+First release under the **`yrby`** name (the project was previously developed
+as `yrb-lite`). The public Ruby interface is the top-level module **`Y`** —
+mirroring the `y-rb` gem's `Y::Doc` interface.
+
+### Changed
+- **Renamed `yrb-lite` → `yrby`.** Module `YrbLite` → top-level `Y`
+  (`Y::Doc`, `Y::Error`, `Y::VERSION`). Require path `require "yrb_lite"` →
+  `require "y"`. Native extension crate `yrb_lite` → `y_ruby`, loaded from
+  `lib/y/y_ruby.bundle`.
+
+### Added
+- Native `Doc#read_text` and `Doc#read_map` readers — reconstruct plain text and
+  a JSON map from the stored CRDT state in-process, server-side, with no Node or
+  subprocess.
+
+### Notes
+- y-crdt wrapper over Rust `yrs` 0.27.2 (magnus/rb-sys), with the full
+  y-websocket sync protocol + Awareness, thread-safe (`Send`/`Sync`,
+  GVL released around CRDT work). Precompiled platform gems are published
+  alongside the source gem so `gem install yrby` needs no Rust toolchain.

data/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

data/README.md

@@ -0,0 +1,413 @@
+# yrby
+
+[![CI](https://github.com/jpcamara/yrby/actions/workflows/ci.yml/badge.svg)](https://github.com/jpcamara/yrby/actions/workflows/ci.yml)
+
+Collaborative editing for Rails, backed by [y-crdt](https://github.com/y-crdt/y-crdt)
+(the Rust library behind Y.js). Your Rails server speaks the y-websocket sync
+protocol directly, so there's no separate Node process hosting the Y.js
+documents.
+
+```ruby
+class DocumentChannel < ApplicationCable::Channel
+  include Y::ActionCable::Sync
+
+  on_load   { |key|         MyStore.load(key) }
+  on_change { |key, update| MyStore.append(key, update) }
+
+  def subscribed    = sync_subscribed(params[:id])
+  def receive(data) = sync_receive(data, params[:id])
+end
+```
+
+On the browser, use the `ActionCableProvider` from the 
+[`@yrby/client`](https://www.npmjs.com/package/@yrby/client) npm package.
+Integrates with any editor that includes Y.js support, such as Tiptap, ProseMirror
+and [Lexxy](https://www.npmjs.com/package/lexxy-realtime).
+
+## Usage
+
+Install the gem and npm package:
+
+```
+gem install yrby-actioncable # depends on yrby
+npm install @yrby/client
+```
+
+## What you get
+
+- A thread-safe Ruby `Doc` you can share across Ruby threads/fibers, and native CRDT work
+  runs with the GVL released.
+- The y-websocket protocol (document sync plus awareness/presence) as a
+  one-include ActionCable concern.
+- Authoritative record-before-distribute semantics: each document change can be
+  recorded durably before it goes out to anyone.
+- 
+
+## Why "lite"
+
+The "lite" is the size of the surface. `yrby` binds just the part of `y-crdt` you
+need to *sync and persist* collaborative documents - a `Doc`, awareness, and the
+y-websocket protocol primitives. The Ruby side treats a document as opaque CRDT
+state: it applies updates, answers sync handshakes, and records deltas, but never
+reaches in to read or edit the contents. The browser editor owns the document's
+shape.
+
+## What isn't "lite"
+
+The surface area may be "lite", but a core focus is on durability, resiliency, delivery
+guarantees, correctness, and thread safety.
+
+Towards that goal, `yrby` adds capabilities that may even stand out in the Yjs ecosystem:
+
+- Built-in update acknowledgement: the `ActionCableProvider` in `@yrby/client` will continue to
+  send updates until an ack is received from the server. [`yrby-actioncable`](https://rubygems.org/gems/yrby-actioncable)
+  only sends an ack when applying an update is successful. The goal is at-least-once delivery,
+  and because CRDTs are idempotent a duplicate update is effectively a no-op.
+- Gap detection in document updates: before applying an update and sending an ack to the client,
+  `yrby` checks whether the update results in any causal gap. Ie, an update comes through
+  which depends on a previous update that is not yet present in the document. This can result in
+  a document stuck with "pending" updates, which will _never_ apply if the missing update is not sent.
+  To avoid this, `yrby` does not apply the update, and starts a new y-protocol sync with the client.
+  That will cause the client to synchronize its document with the server, sending through any updates
+  that may have been missed
+
+## What about [yrb](https://github.com/y-crdt/yrb)?
+
+`yrb` has a much larger interface that gives you most of the Yjs type system - 
+shared text, arrays, maps, XML - to build and query documents in Ruby. It was a great
+inspiration for my use of Yjs in Ruby/Rails, and I originally considered building
+on top of it. There are a few reasons I went with `yrby` instead:
+
+- `yrb` is largely unmaintained. It was built as an experiment for GitLab, and the original
+  author mostly moved onto other projects.
+- [It isn't thread-safe](https://github.com/y-crdt/yrb/issues/72). It segfaults in a threaded
+  environment (such as ActionCable...)
+- It's a much larger set of features to maintain, which most people don't need. The vast
+  majority of people manipulate Y.js documents in the browser, not from a server-side language.
+
+## Testing
+
+Ruby and Rust unit tests cover the core. CI also runs the npm client tests and a
+Rails demo smoke slice against the real ActionCable stack. The demo includes
+heavier local suites for hostile input, crash recovery, multi-browser editing,
+AnyCable, and load testing. The benchmark note below is from a single laptop.
+Issues and PRs are welcome.
+
+## Install
+
+```ruby
+# Core CRDT + protocol primitives:
+gem "yrby"
+
+# For the Rails/ActionCable server concern (Y::ActionCable::Sync):
+gem "yrby-actioncable"
+```
+
+Requires Ruby 3.4 or newer. The release workflow builds precompiled gems for
+Ruby 3.4 and 4.0 across the supported Ruby platforms, with native smoke tests
+on Linux x86_64 and macOS arm64. Installing from a matching platform gem needs
+no Rust; a source build needs [Rust](https://rustup.rs).
+
+To work on the gem itself:
+
+```bash
+git clone https://github.com/jpcamara/yrby
+cd yrby
+bundle install
+bundle exec rake compile test
+```
+
+The rest of the dev setup, plus the demo, is in [CONTRIBUTING.md](CONTRIBUTING.md).
+
+## Docs
+
+- The ActionCable concern and a quickstart are [below](#actioncable-integration).
+- [`examples/actioncable-demo`](examples/actioncable-demo): a runnable Rails +
+  Tiptap app with collaborative cursors, the AnyCable setup, a Postgres store,
+  and the test/load suites.
+- [CHANGELOG.md](CHANGELOG.md) and [CONTRIBUTING.md](CONTRIBUTING.md).
+
+## Usage
+
+### Doc (Low-Level Document Sync)
+
+```ruby
+require "y"
+
+# Create docs
+doc = Y::Doc.new        # random client ID
+doc = Y::Doc.new(12345) # specific client ID (used for CRDT identity)
+
+# Encoding
+doc.encode_state_vector           # => current state vector
+doc.encode_state_as_update        # => full update
+doc.encode_state_as_update(sv)    # => update diff against state vector
+
+# Applying updates
+doc.apply_update(update_bytes)    # apply raw V1 update
+
+# Sync protocol
+doc.sync_step1                    # => SyncStep1 message (this doc's state vector)
+doc.handle_sync_message(data)     # => [msg_type, sync_type, response]; answers a
+                                  #    peer's SyncStep1 with a SyncStep2
+```
+
+### Protocol codec (module functions)
+
+Classifying and unwrapping wire frames is stateless, so it's exposed as
+`Y` module functions rather than a class. The server never holds presence
+or document state to route a frame — presence lives in the browser clients, and
+the server only relays awareness frames opaquely.
+
+```ruby
+Y.message_kind(frame)         # => 0 drop / 1 step1 / 2 update / 3 awareness / 4 query
+Y.update_from_message(frame)  # => the document delta carried by a frame, or nil
+Y.wrap_update(update_bytes)   # => wrap a raw doc update as a sync Update frame
+```
+
+### ActionCable Integration
+
+`Y::ActionCable::Sync` (from the `yrby-actioncable` gem) is a channel
+concern that implements the full y-websocket protocol (document sync +
+awareness/presence) over ActionCable:
+
+```ruby
+# app/channels/document_channel.rb
+class DocumentChannel < ApplicationCable::Channel
+  include Y::ActionCable::Sync
+
+  on_load { |key| MyStore.load(key) }                 # source of truth
+  on_change { |key, update| MyStore.append(key, update) } # durable record
+
+  def subscribed
+    sync_subscribed params[:id]
+  end
+
+  def receive(data)
+    sync_receive(data, params[:id])
+  end
+end
+```
+
+The concern is store-backed. A handshake is answered from `on_load`; document
+changes are checked against that durable state, recorded through `on_change`,
+then broadcast. Nothing authoritative is kept in ActionCable process memory, so
+AnyCable RPC workers, Puma workers, and separate dynos can all handle messages
+for the same document as long as they share the same store and cable adapter.
+
+`on_load` and `on_change` are required. If either is missing, the channel fails 
+before it can acknowledge or broadcast edits. Presence is ephemeral:
+awareness frames are relayed, and `@yrby/client` sends a best-effort
+presence-removal frame on disconnect/pagehide, with the client-side awareness
+timeout as the fallback for abrupt disconnects.
+
+Incoming frames are validated as a single well-formed protocol message before
+anything processes or relays them. Malformed, truncated, multi-message,
+oversized, or unknown frames are dropped. A bad frame can't crash the process: a
+Rust panic is caught at the FFI boundary and re-raised as a Ruby exception. And
+no single client can relay garbage that breaks the others in a room.
+
+#### Delivery guarantees
+
+The contract is the same at every scale — one process, or hundreds across many
+servers:
+
+- **The document always converges.** CRDT updates are commutative and
+  idempotent, so out-of-order, duplicate, or concurrent delivery all converge to
+  the same correct document. This needs no coordination and holds everywhere.
+- **The durable log never goes gappy.** An update is recorded only once its
+  causal dependencies are already in the store (checked against `on_load`); a
+  causally-incomplete update triggers a resync instead, so the log always
+  rebuilds cleanly.
+- **`on_change` is at-least-once, and the durable guarantee is that replaying the
+  log reconstructs the document.** Every update triggers `on_change` before it's acked or
+  broadcast (record-before-distribute). If exactly-once updates matter for you, **you
+  must make `on_change` idempotent**. But remember that the CRDT can handle duplicates.
+- **A raising `on_change` rejects the update implicitly.** If the block raises,
+  the update is neither acked nor broadcast (record-before-distribute stops both).
+  There is no negative-ack: the client simply never receives the ack, keeps the
+  update pending, and retransmits on its timer/reconnect. This is built for
+  *transient* failures (the store is briefly down → a retry lands). A block that
+  raises *deterministically* — a validation that always fails for this edit —
+  will be retried forever, since nothing tells the client to stop. Enforce hard
+  rejections before the edit reaches `on_change` (channel authorization in
+  `subscribed`), not by raising inside it.
+- **An over-cap frame is dropped the same silent way.** A frame larger than
+  `max_frame_bytes` (default 8 MiB) is dropped before decoding — no ack, no
+  broadcast — to bound the work a client can force. For a genuine document
+  update that means the same implicit rejection as above: unacked, retransmitted
+  forever. Normal typing never approaches the cap, but a large paste, an embedded
+  image, or a big initial `SyncStep2` can. The drop is logged (`warn` for
+  over-cap, `debug` for undecodable) with the document key and update id so it's
+  findable; override `sync_log_context` on the channel to add a user/connection
+  id. Size the cap for your largest expected payload, and reject
+  genuinely-too-big content upstream rather than relying on the cap to reject it
+  gracefully.
+
+#### Multi-process deployments
+
+Most Rails apps run several processes, and any of them might serve a given document. 
+Two pieces keep them in step.
+
+Broadcasts cross processes through the Action Cable adapter, so it needs to something
+like `redis` or `solid_cable`, not `async`. With that in place, a change
+on one process reaches clients on all of them.
+
+Every process rebuilds document state from the durable store through `on_load`.
+Because changes are recorded before broadcast, record-before-distribute holds
+across processes: whichever process receives a change records it to the shared
+store before anyone, anywhere, sees it.
+
+`bun multiprocess.mjs` in the demo runs clients across two processes and checks
+convergence, fresh reads on both, presence across processes, and one shared log.
+
+##### AnyCable
+
+`yrby` fully supports AnyCable.
+
+The demo checks this against a real anycable-go + RPC server
+(`frontend/anycable_probe.mjs`, `anycable_concurrent.mjs`): liveness, the
+yrby client provider, cross-process reads, and concurrent convergence.
+
+##### Demo
+
+[`examples/actioncable-demo`](examples/actioncable-demo) is a full Rails + Tiptap
+app using the yrby provider, with end-to-end tests.
+
+#### Record Before Distribute
+
+Every document change is handed to the `on_change` handler before broadcasting.
+It is up to you to durably record it:
+
+```ruby
+class DocumentChannel < ApplicationCable::Channel
+  include Y::ActionCable::Sync
+
+  # ...
+
+  on_change do |key, update|
+    # Synchronous, durable write. `update` is the exact CRDT delta.
+    AuditLog.append!(key, update)   # raise to REJECT the change
+  end
+
+  # ...
+end
+```
+
+If the recorder raises (say the store is down), the change is rejected: not
+applied, not sent to anyone. The cost is a synchronous durable write on the path
+of every change. There's no in-gem per-document lock; concurrent writes to one
+document can both record (at-least-once), and since CRDT apply is idempotent a
+duplicate record replays to the same document.
+
+The demo wires `on_change` to a durable Postgres-backed log by default, and checks
+end to end that the log alone rebuilds the document.
+
+#### Reliable delivery (acks)
+
+yrby document delivery is ack-tracked. Browser document updates carry an
+`"id"`, and the server replies `{ "ack": <id> }` once `on_change` has succesfully fired.
+A causally-gapped update is not acked; the server sends a resync request, and
+the client keeps the update queued until it lands.
+
+```
+client -> server   { "update": "<base64 update>", "id": 42 }
+server -> client   { "ack": 42 }     # update accepted; safe to forget
+```
+
+`@yrby/client`'s `ActionCableProvider` handles this automatically. It keeps
+the unacknowledged local document tail in a queue and sends the merged tail as a
+single causally-complete delta. The id is the highest sequence in the batch, so
+one `{ ack: id }` cumulatively confirms everything up to it. Because CRDT apply
+is idempotent, a resend that already landed is a harmless no-op that just
+re-acks. Awareness stays ephemeral and is not acked.
+
+Presence (cursors, selections) is owned by the browser clients — the server
+never sets or holds presence state, it only relays awareness frames opaquely.
+See `@yrby/client` for the client-side awareness API.
+
+## Thread Safety
+
+A `Doc` is safe to share across Ruby threads — used concurrently from Puma
+workers, ActionCable connection threads, or background jobs without external
+locking.
+
+`test/thread_safety_test.rb` runs shared docs, the full sync handshake, and
+fan-in sync across 8 threads at once, and checks the interleaving doesn't change
+convergence.
+
+### Parallelism (GVL release)
+
+Every method that does real CRDT work (applying updates, encoding state,
+handling sync messages) releases Ruby's Global VM Lock
+(`rb_thread_call_without_gvl`) while the native code runs. That buys two things.
+
+CRDT work runs in parallel across Ruby threads on MRI, not just
+JRuby/TruffleRuby. `bench/parallelism_bench.rb` measures over 2x wall-clock
+speedup applying a ~900 KB update concurrently; native code that held the GVL
+couldn't beat serial time.
+
+A slow operation also can't stall the VM. A thread applying a large update holds
+the doc's write lock without holding the GVL, so other Ruby threads keep running
+instead of queuing behind it.
+
+Each method has the same shape: copy Ruby byte strings first, drop the GVL, do
+the yrs work while taking and releasing native locks entirely inside the
+closure, take the GVL back, then build Ruby objects. No Ruby API is touched
+without the GVL, and no native lock is held while reacquiring it, so the lock
+order can't deadlock. Panics in native code are caught and re-raised as Ruby
+exceptions.
+
+## Message Type Constants
+
+```ruby
+Y::MSG_SYNC            # 0 - Document sync messages
+Y::MSG_AWARENESS       # 1 - User presence data
+
+Y::MSG_SYNC_STEP1      # 0 - State vector request
+Y::MSG_SYNC_STEP2      # 1 - Update response
+Y::MSG_SYNC_UPDATE     # 2 - Incremental update
+```
+
+## Sync Flow
+
+```
+Client A                          Server
+   |                                  |
+   |-------- connect() ------------->|
+   |  (SyncStep1 + Awareness)        |
+   |                                  |
+   |<--- handle_sync_message resp ---|
+   |  (SyncStep2)                    |
+   |                                  |
+   |  (Document synchronized!)        |
+   |                                  |
+   |<------- updates ----------------|
+   |-------- updates --------------->|
+```
+
+## Development
+
+```bash
+# Setup
+bundle install
+
+# Build extension
+rake compile
+
+# Run tests
+rake test
+
+# Clean build artifacts
+rake clean
+```
+
+## License
+
+MIT License
+
+## Acknowledgments
+
+- [y-crdt/yrs](https://github.com/y-crdt/y-crdt) - The Rust implementation of Y.js
+- [Magnus](https://github.com/matsadler/magnus) - Ruby bindings for Rust
+- [rb-sys](https://github.com/oxidize-rb/rb-sys) - Rust extensions for Ruby

data/lib/y/decoder/version.rb

@@ -0,0 +1,7 @@
+# frozen_string_literal: true
+
+module Y
+  module Decoder
+    VERSION = "0.1.0.alpha1"
+  end
+end

data/lib/y/decoder.rb

@@ -0,0 +1,66 @@
+# frozen_string_literal: true
+
+require "y"
+require "y/decoder/version"
+
+module Y
+  # Plain-text reconstruction of a stored Yjs document, in pure Ruby — for search
+  # indexing and previews. The core `yrby` gem moves and stores opaque CRDT
+  # updates without reading them; this reads the text out of the shared type the
+  # editor uses (Lexical's `Y.XmlText`, plain `Y.Text`, or ProseMirror's
+  # `Y.XmlFragment`), in-process, on the native extension core already ships — no
+  # Node, no subprocess, no binary.
+  #
+  #   state = doc.encode_state_as_update        # opaque CRDT bytes from the store
+  #   Y::Decoder.text(state)              # => "hello world"
+  #   Y::Decoder.preview(state, 280)      # => "hello world…"
+  #
+  # Full-fidelity reconstruction (the exact Lexical EditorState / HTML, which
+  # needs @lexical/yjs) is a separate, opt-in concern — see the `yrby-decode`
+  # package's Bun binary. This gem stays pure Ruby on purpose.
+  module Decoder
+    class Error < Y::Error; end
+
+    module_function
+
+    # Plain text of the document. `field` pins the root key (Lexical: the editor
+    # id; ProseMirror: "default"); omit it to use the document's sole root.
+    def text(state, field: nil)
+      field ||= Y::Doc.new.tap { |d| d.apply_update(state) }.root_names.first
+      return "" unless field
+
+      # A plain `Y.Text` root (a simple shared-text editor) reads straight out.
+      # (A yrs root's type is fixed by its first typed access, so each reader
+      # gets a fresh doc to try a different shared type against the same state.)
+      direct = load(state).read_text(field)
+      return normalize(direct) if direct && !direct.strip.empty?
+
+      # Lexical (each block a sibling `Y.XmlText`) and ProseMirror (blocks are
+      # `Y.XmlElement`s) both come back from read_xml as block-per-line markup;
+      # strip any element tags to plain text.
+      markup = load(state).read_xml(field)
+      markup ? normalize(strip_tags(markup)) : ""
+    end
+
+    # A compact, single-line preview for list UIs.
+    def preview(state, limit: 280, field: nil)
+      body = text(state, field: field).gsub(/\s+/, " ").strip
+      body.length > limit ? "#{body[0, limit].rstrip}…" : body
+    end
+
+    def load(state)
+      Y::Doc.new.tap { |doc| doc.apply_update(state) }
+    end
+
+    def strip_tags(markup)
+      markup.gsub(/<[^>]*>/, " ")
+    end
+
+    def normalize(text)
+      text.gsub(/[ \t]+/, " ")     # collapse runs of spaces/tabs
+          .gsub(/ *\n */, "\n")    # trim spaces left around block separators
+          .gsub(/\n{3,}/, "\n\n")  # cap blank-line runs
+          .strip
+    end
+  end
+end

data/lib/y/version.rb

@@ -0,0 +1,5 @@
+# frozen_string_literal: true
+
+module Y
+  VERSION = "0.2.0"
+end

data/lib/y.rb

@@ -0,0 +1,19 @@
+# frozen_string_literal: true
+
+require_relative "y/version"
+
+# Load the native extension. Precompiled gems ship it in a per-Ruby-version
+# subdir (lib/y/<major.minor>/y_ruby.<ext>); a source build puts it flat at
+# lib/y/y_ruby.<ext>. Try the versioned path first, fall back.
+begin
+  RUBY_VERSION =~ /(\d+\.\d+)/
+  require_relative "y/#{Regexp.last_match(1)}/y_ruby"
+rescue LoadError
+  require_relative "y/y_ruby"
+end
+
+module Y
+  # Doc, Error, and the protocol module functions are defined in the Rust
+  # extension. The ActionCable integration (Y::ActionCable::Sync) lives in the
+  # separate `yrby-actioncable` gem; require "y/action_cable".
+end

data/lib/yrby-decoder.rb

@@ -0,0 +1,4 @@
+# frozen_string_literal: true
+
+# Entry point matching the gem name, so `Bundler.require` loads it automatically.
+require "y/decoder"

data/lib/yrby.rb

@@ -0,0 +1,4 @@
+# frozen_string_literal: true
+
+# Entry point matching the gem name, so `Bundler.require` loads it automatically.
+require "y"

metadata

@@ -0,0 +1,107 @@
+--- !ruby/object:Gem::Specification
+name: yrby
+version: !ruby/object:Gem::Version
+  version: 0.2.0
+platform: arm64-darwin
+authors:
+- JP Camara
+autorequire: 
+bindir: bin
+cert_chain: []
+date: 2026-06-29 00:00:00.000000000 Z
+dependencies:
+- !ruby/object:Gem::Dependency
+  name: minitest
+  requirement: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: '5.0'
+  type: :development
+  prerelease: false
+  version_requirements: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: '5.0'
+- !ruby/object:Gem::Dependency
+  name: rake
+  requirement: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: '13.0'
+  type: :development
+  prerelease: false
+  version_requirements: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: '13.0'
+- !ruby/object:Gem::Dependency
+  name: rake-compiler
+  requirement: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: '1.2'
+  type: :development
+  prerelease: false
+  version_requirements: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: '1.2'
+description: 'yrby is a thread-safe Ruby binding over the Rust y-crdt (yrs) library:
+  CRDT documents, awareness/presence, and the y-websocket sync protocol primitives,
+  with the GVL released during native work so documents sync in parallel. The ActionCable/Rails
+  integration lives in the companion yrby-actioncable gem.'
+email:
+- johnpcamara@gmail.com
+executables: []
+extensions: []
+extra_rdoc_files: []
+files:
+- CHANGELOG.md
+- LICENSE
+- README.md
+- lib/y.rb
+- lib/y/3.4/y_ruby.bundle
+- lib/y/4.0/y_ruby.bundle
+- lib/y/decoder.rb
+- lib/y/decoder/version.rb
+- lib/y/version.rb
+- lib/yrby-decoder.rb
+- lib/yrby.rb
+homepage: https://github.com/jpcamara/yrby
+licenses:
+- MIT
+metadata:
+  source_code_uri: https://github.com/jpcamara/yrby
+  changelog_uri: https://github.com/jpcamara/yrby/blob/main/CHANGELOG.md
+  bug_tracker_uri: https://github.com/jpcamara/yrby/issues
+  rubygems_mfa_required: 'true'
+post_install_message: 
+rdoc_options: []
+require_paths:
+- lib
+required_ruby_version: !ruby/object:Gem::Requirement
+  requirements:
+  - - ">="
+    - !ruby/object:Gem::Version
+      version: '3.4'
+  - - "<"
+    - !ruby/object:Gem::Version
+      version: 4.1.dev
+required_rubygems_version: !ruby/object:Gem::Requirement
+  requirements:
+  - - ">="
+    - !ruby/object:Gem::Version
+      version: '0'
+requirements: []
+rubygems_version: 3.5.23
+signing_key: 
+specification_version: 4
+summary: 'Thread-safe Ruby bindings for y-crdt (Y.js): documents, awareness, and the
+  y-websocket sync protocol'
+test_files: []