tokra 0.0.1.pre.1

data/LICENSES/CC0-1.0.txt

@@ -0,0 +1,121 @@
+Creative Commons Legal Code
+
+CC0 1.0 Universal
+
+    CREATIVE COMMONS CORPORATION IS NOT A LAW FIRM AND DOES NOT PROVIDE
+    LEGAL SERVICES. DISTRIBUTION OF THIS DOCUMENT DOES NOT CREATE AN
+    ATTORNEY-CLIENT RELATIONSHIP. CREATIVE COMMONS PROVIDES THIS
+    INFORMATION ON AN "AS-IS" BASIS. CREATIVE COMMONS MAKES NO WARRANTIES
+    REGARDING THE USE OF THIS DOCUMENT OR THE INFORMATION OR WORKS
+    PROVIDED HEREUNDER, AND DISCLAIMS LIABILITY FOR DAMAGES RESULTING FROM
+    THE USE OF THIS DOCUMENT OR THE INFORMATION OR WORKS PROVIDED
+    HEREUNDER.
+
+Statement of Purpose
+
+The laws of most jurisdictions throughout the world automatically confer
+exclusive Copyright and Related Rights (defined below) upon the creator
+and subsequent owner(s) (each and all, an "owner") of an original work of
+authorship and/or a database (each, a "Work").
+
+Certain owners wish to permanently relinquish those rights to a Work for
+the purpose of contributing to a commons of creative, cultural and
+scientific works ("Commons") that the public can reliably and without fear
+of later claims of infringement build upon, modify, incorporate in other
+works, reuse and redistribute as freely as possible in any form whatsoever
+and for any purposes, including without limitation commercial purposes.
+These owners may contribute to the Commons to promote the ideal of a free
+culture and the further production of creative, cultural and scientific
+works, or to gain reputation or greater distribution for their Work in
+part through the use and efforts of others.
+
+For these and/or other purposes and motivations, and without any
+expectation of additional consideration or compensation, the person
+associating CC0 with a Work (the "Affirmer"), to the extent that he or she
+is an owner of Copyright and Related Rights in the Work, voluntarily
+elects to apply CC0 to the Work and publicly distribute the Work under its
+terms, with knowledge of his or her Copyright and Related Rights in the
+Work and the meaning and intended legal effect of CC0 on those rights.
+
+1. Copyright and Related Rights. A Work made available under CC0 may be
+protected by copyright and related or neighboring rights ("Copyright and
+Related Rights"). Copyright and Related Rights include, but are not
+limited to, the following:
+
+  i. the right to reproduce, adapt, distribute, perform, display,
+     communicate, and translate a Work;
+ ii. moral rights retained by the original author(s) and/or performer(s);
+iii. publicity and privacy rights pertaining to a person's image or
+     likeness depicted in a Work;
+ iv. rights protecting against unfair competition in regards to a Work,
+     subject to the limitations in paragraph 4(a), below;
+  v. rights protecting the extraction, dissemination, use and reuse of data
+     in a Work;
+ vi. database rights (such as those arising under Directive 96/9/EC of the
+     European Parliament and of the Council of 11 March 1996 on the legal
+     protection of databases, and under any national implementation
+     thereof, including any amended or successor version of such
+     directive); and
+vii. other similar, equivalent or corresponding rights throughout the
+     world based on applicable law or treaty, and any national
+     implementations thereof.
+
+2. Waiver. To the greatest extent permitted by, but not in contravention
+of, applicable law, Affirmer hereby overtly, fully, permanently,
+irrevocably and unconditionally waives, abandons, and surrenders all of
+Affirmer's Copyright and Related Rights and associated claims and causes
+of action, whether now known or unknown (including existing as well as
+future claims and causes of action), in the Work (i) in all territories
+worldwide, (ii) for the maximum duration provided by applicable law or
+treaty (including future time extensions), (iii) in any current or future
+medium and for any number of copies, and (iv) for any purpose whatsoever,
+including without limitation commercial, advertising or promotional
+purposes (the "Waiver"). Affirmer makes the Waiver for the benefit of each
+member of the public at large and to the detriment of Affirmer's heirs and
+successors, fully intending that such Waiver shall not be subject to
+revocation, rescission, cancellation, termination, or any other legal or
+equitable action to disrupt the quiet enjoyment of the Work by the public
+as contemplated by Affirmer's express Statement of Purpose.
+
+3. Public License Fallback. Should any part of the Waiver for any reason
+be judged legally invalid or ineffective under applicable law, then the
+Waiver shall be preserved to the maximum extent permitted taking into
+account Affirmer's express Statement of Purpose. In addition, to the
+extent the Waiver is so judged Affirmer hereby grants to each affected
+person a royalty-free, non transferable, non sublicensable, non exclusive,
+irrevocable and unconditional license to exercise Affirmer's Copyright and
+Related Rights in the Work (i) in all territories worldwide, (ii) for the
+maximum duration provided by applicable law or treaty (including future
+time extensions), (iii) in any current or future medium and for any number
+of copies, and (iv) for any purpose whatsoever, including without
+limitation commercial, advertising or promotional purposes (the
+"License"). The License shall be deemed effective as of the date CC0 was
+applied by Affirmer to the Work. Should any part of the License for any
+reason be judged legally invalid or ineffective under applicable law, such
+partial invalidity or ineffectiveness shall not invalidate the remainder
+of the License, and in such case Affirmer hereby affirms that he or she
+will not (i) exercise any of his or her remaining Copyright and Related
+Rights in the Work or (ii) assert any associated claims and causes of
+action with respect to the Work, in either case contrary to Affirmer's
+express Statement of Purpose.
+
+4. Limitations and Disclaimers.
+
+ a. No trademark or patent rights held by Affirmer are waived, abandoned,
+    surrendered, licensed or otherwise affected by this document.
+ b. Affirmer offers the Work as-is and makes no representations or
+    warranties of any kind concerning the Work, express, implied,
+    statutory or otherwise, including without limitation warranties of
+    title, merchantability, fitness for a particular purpose, non
+    infringement, or the absence of latent or other defects, accuracy, or
+    the present or absence of errors, whether or not discoverable, all to
+    the greatest extent permissible under applicable law.
+ c. Affirmer disclaims responsibility for clearing rights of other persons
+    that may apply to the Work or any use thereof, including without
+    limitation any person's Copyright and Related Rights in the Work.
+    Further, Affirmer disclaims responsibility for obtaining any necessary
+    consents, permissions or other rights required for any use of the
+    Work.
+ d. Affirmer understands and acknowledges that Creative Commons is not a
+    party to this document and has no duty or obligation with respect to
+    this CC0 or use of the Work.

data/LICENSES/MIT.txt

@@ -0,0 +1,18 @@
+MIT License
+
+Copyright (c) <year> <copyright holders>
+
+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,45 @@
+<!--
+SPDX-FileCopyrightText: 2026 Kerrick Long <me@kerricklong.com>
+
+SPDX-License-Identifier: CC-BY-SA-4.0
+-->
+
+# Tokra
+
+TODO: Delete this and the text below, and describe your gem
+
+Welcome to your new gem! In this directory, you'll find the files you need to be able to package up your Ruby library into a gem. Put your Ruby code in the file `lib/tokra`. To experiment with that code, run `bin/console` for an interactive prompt.
+
+## Installation
+
+TODO: Replace `UPDATE_WITH_YOUR_GEM_NAME_IMMEDIATELY_AFTER_RELEASE_TO_RUBYGEMS_ORG` with your gem name right after releasing it to RubyGems.org. Please do not do it earlier due to security reasons. Alternatively, replace this section with instructions to install your gem from git if you don't plan to release to RubyGems.org.
+
+Install the gem and add to the application's Gemfile by executing:
+
+```bash
+bundle add UPDATE_WITH_YOUR_GEM_NAME_IMMEDIATELY_AFTER_RELEASE_TO_RUBYGEMS_ORG
+```
+
+If bundler is not being used to manage dependencies, install the gem by executing:
+
+```bash
+gem install UPDATE_WITH_YOUR_GEM_NAME_IMMEDIATELY_AFTER_RELEASE_TO_RUBYGEMS_ORG
+```
+
+## Usage
+
+TODO: Write usage instructions here
+
+## Development
+
+After checking out the repo, run `bin/setup` to install dependencies. Then, run `rake test` to run the tests. You can also run `bin/console` for an interactive prompt that will allow you to experiment.
+
+To install this gem onto your local machine, run `bundle exec rake install`. To release a new version, update the version number in `version.rb`, and then run `bundle exec rake release`, which will create a git tag for the version, push git commits and the created tag, and push the `.gem` file to [rubygems.org](https://rubygems.org).
+
+## Contributing
+
+Bug reports and pull requests are welcome on GitHub at https://github.com/[USERNAME]/tokra. This project is intended to be a safe, welcoming space for collaboration, and contributors are expected to adhere to the [code of conduct](https://github.com/[USERNAME]/tokra/blob/main/CODE_OF_CONDUCT.md).
+
+## Code of Conduct
+
+Everyone interacting in the Tokra project's codebases, issue trackers, chat rooms and mailing lists is expected to follow the [code of conduct](https://github.com/[USERNAME]/tokra/blob/main/CODE_OF_CONDUCT.md).

data/README.rdoc

@@ -0,0 +1,4 @@
+== Build Desktop Apps with Ruby and Web Technologies
+
+Tokra is a port of Tauri to Ruby, enabling you to build desktop applications
+with web technologies backed by Ruby.

data/REUSE.toml

@@ -0,0 +1,11 @@
+version = 1
+
+[[annotations]]
+path = 'Gemfile.lock'
+SPDX-FileCopyrightText = "2025 Kerrick Long <me@kerricklong.com>"
+SPDX-License-Identifier = "CC0-1.0"
+
+[[annotations]]
+path = 'README.rdoc'
+SPDX-FileCopyrightText = "2026 Kerrick Long <me@kerricklong.com>"
+SPDX-License-Identifier = "CC-BY-SA-4.0"

data/Rakefile

@@ -0,0 +1,27 @@
+# frozen_string_literal: true
+
+# SPDX-FileCopyrightText: 2025 Kerrick Long <me@kerricklong.com>
+# SPDX-License-Identifier: AGPL-3.0-or-later
+
+require "bundler/gem_tasks"
+
+require "rdoc/task"
+RDoc::Task.new do |rdoc|
+  rdoc.rdoc_dir = ENV["RDOC_OUTPUT"] || "tmp/rdoc"
+end
+
+# Rust extension compilation
+require "rb_sys/extensiontask"
+
+GEMSPEC = Gem::Specification.load("tokra.gemspec")
+
+RbSys::ExtensionTask.new("tokra", GEMSPEC) do |ext|
+  ext.lib_dir = "lib/tokra"
+end
+
+task build: :compile
+
+# Import all tasks from the tasks/ directory
+Dir.glob("tasks/*.rake").each { |r| import r }
+
+task default: %w[compile lint:fix test lint steep lint:rust]

data/Steepfile

@@ -0,0 +1,15 @@
+# frozen_string_literal: true
+
+# SPDX-FileCopyrightText: 2026 Kerrick Long <me@kerricklong.com>
+# SPDX-License-Identifier: AGPL-3.0-or-later
+
+target :lib do
+  signature "sig"
+  check "lib"
+
+  library "pathname"
+  library "fileutils"
+  library "minitest"
+  library "date"
+  library "timeout"
+end

data/clippy.toml

@@ -0,0 +1,5 @@
+# SPDX-FileCopyrightText: 2026 Kerrick Long <me@kerricklong.com>
+# SPDX-License-Identifier: AGPL-3.0-or-later
+
+# Clippy configuration for lint parameters only.
+# Lint levels (forbid/deny/warn/allow) are configured in Cargo.toml [lints] section.

data/clippy_exceptions.rb

@@ -0,0 +1,59 @@
+# frozen_string_literal: true
+
+#--
+# SPDX-FileCopyrightText: 2026 Kerrick Long <me@kerricklong.com>
+# SPDX-License-Identifier: AGPL-3.0-or-later
+#++
+
+# Approved Clippy allow exceptions.
+# Each entry must explain WHY the exception is unavoidable.
+# Review carefully before adding new entries.
+
+allow "ext/tokra/src/lib.rs", line: 7, reason: <<~END
+  Magnus FFI requires owned types at the Ruby-Rust boundary. Ruby strings must be
+  converted to owned Rust Strings when crossing the FFI, as borrowed references
+  cannot safely outlive the Ruby GC cycle. This is a fundamental constraint of
+  the magnus crate's type marshaling, not a code smell to be fixed.
+END
+
+allow "ext/tokra/src/lib.rs", lines: [77, 189, 249], lint: "unsafe_code", reason: <<~END
+  Tauri Pattern: unsafe impl Send for RbEventLoop, RbWindow, RbWebView
+
+  These types wrap platform-native GUI objects (tao::Window, wry::WebView) that
+  are bound to the main OS thread. Magnus's TypedData trait requires Send, but
+  these types are not inherently thread-safe.
+
+  INVARIANT: All access to these types happens exclusively on the main thread
+  via the tao event loop. Ruby code cannot access these objects from Worker
+  Ractors - only through the Send-safe Proxy which marshals commands to the
+  main thread.
+
+  This pattern is identical to how Tauri implements this in tauri-runtime-wry:
+  - `unsafe impl Send for WindowsStore {}` (lib.rs:433)
+  - `unsafe impl Send for DispatcherMainThreadContext<T> {}` (lib.rs:451)
+  - `unsafe impl Send for WindowBuilderWrapper {}` (lib.rs:809)
+
+  The invariant is enforced by:
+  1. The event loop callback runs only on the main thread
+  2. Ractors can only hold the Proxy (which IS genuinely Send+Sync-safe)
+  3. Integration tests verify invariants:
+     test/integration/thread_safety_invariant_test.rb:23-38 (Proxy is Ractor-safe)
+     test/integration/thread_safety_invariant_test.rb:44-55 (main thread instantiation)
+     test/integration/thread_safety_invariant_test.rb:60-73 (main thread operations)
+END
+
+allow "ext/tokra/src/lib.rs", lines: [310], lint: "unsafe_code", reason: <<~END
+  Magnus TypedData for RbProxy: unsafe impl TypedData for RbProxy
+
+  This is SAFE because EventLoopProxy<T> is genuinely Send+Sync by design.
+  We use this to enable the `frozen_shareable` flag which makes the Ruby
+  object Ractor-shareable when frozen.
+
+  Unlike the other unsafe impls (which are for main-thread-only types),
+  this one is actually safe - tao explicitly designed EventLoopProxy for
+  cross-thread communication. The unsafe is only required by Magnus's
+  TypedData trait signature, not because the operation is unsafe.
+
+  VERIFIED BY: test/integration/thread_safety_invariant_test.rb:23-38
+  Tests that frozen Proxy becomes Ractor-shareable.
+END

data/doc/contributors/adr/001.md

@@ -0,0 +1,187 @@
+<!--
+SPDX-FileCopyrightText: 2026 Kerrick Long <me@kerricklong.com>
+
+SPDX-License-Identifier: CC-BY-SA-4.0
+-->
+
+# ADR 001: Tokra Architecture - Ruby-Host with Thin Rust Bindings
+
+## Status
+Accepted
+
+## Date
+2026-01-29
+
+## Context
+We are building **Tokra**, a desktop application framework for Ruby 4.0.1+.
+The goal is to enable developers to build performant, native-feeling desktop apps using HTML/CSS/JS for the frontend and **Pure Ruby** for the backend logic.
+
+Historically, frameworks like Tauri required significant Rust code to manage state, commands, and sidecars. However, with the release of Ruby 4.0 (Ractors, YJIT), Ruby is now fast enough and concurrent enough to handle these responsibilities directly.
+
+We need an architecture that:
+1.  Minimizes Rust maintenance overhead (cost & complexity).
+2.  Maximizes Ruby developer experience (logic stays in Ruby).
+3.  Ensures 60FPS UI performance by never blocking the main thread.
+4.  Maintains a secure barrier between the WebView and the System.
+
+## Decision
+We will adopt the **"Thin Binding" + "Ruby Host"** architecture.
+
+1.  **Rust Layer (The Dumb Pipe):** We will use `magnus` to create a thin, un-opinionated wrapper around `tao` (Windowing) and `wry` (WebView). It will not know about "commands" or "state"; it will strictly pass raw string messages to Ruby.
+2.  **Ruby Layer (The Brain):** The application lifecycle, command routing, security allowlists, and state management will be implemented entirely in Ruby.
+3.  **Concurrency Model (Ractor Isolation):**
+    * **Main Ractor:** Dedicated exclusively to the `Tao` event loop and Window management.
+    * **Worker Ractor:** Dedicated to user business logic, file I/O, and heavy computation.
+    * **IPC:** Communication between layers uses `Ractor.send(obj, move: true)` for zero-copy overhead.
+
+## Architecture Specification
+
+### 1. High-Level Diagram
+
+    [ WebView (HTML/JS) ]
+            |
+            | IPC (Raw JSON String)
+            v
+    [ Rust Layer (TokraFFI) ]  <-- "Dumb Pipe"
+            |
+            | Callback
+            v
+    [ Main Ractor (UI) ]       <-- "The Window Manager"
+            |   1. Security Check (Allowlist)
+            |   2. Ractor.send(move: true)
+            v
+    [ Worker Ractor (Logic) ]  <-- "The User App"
+            |   1. Command Routing
+            |   2. Business Logic / DB / IO
+            |
+            | proxy.send_event()
+            v
+    [ Main Ractor (UI) ]       <-- Wakes up Event Loop
+            |
+            v
+    [ Rust Layer (eval_js) ]
+            |
+            v
+    [ WebView (Update UI) ]
+
+### 2. Rust Deliverables (`ext/tokra/src/lib.rs`)
+
+The Rust extension must expose three primary classes via Magnus. It should use `cdylib` crate type.
+
+#### A. `Tokra::Native::EventLoop`
+* **Responsibility:** Hijack the OS Main Thread for `tao`.
+* **Signature:** `run(&self, callback: Proc)` -> `!` (Never returns)
+* **Signal Safety:** Must implement a `ctrlc` handler that triggers `UserEvent::Exit` to wake the loop on SIGINT. Ruby's `Signal.trap` will not work while Tao is running.
+* **Behavior:**
+    * Iterates `event_loop.run_return` or `run`.
+    * On `UserEvent` (from Proxy), triggers the callback.
+    * On `WindowEvent` (Resize, Close), triggers the callback.
+
+#### B. `Tokra::Native::Window`
+* **Responsibility:** Wrap `tao::window::Window`.
+* **Methods:** `new`, `set_title`, `set_size`, `id`.
+
+#### C. `Tokra::Native::WebView`
+* **Responsibility:** Wrap `wry::WebView`.
+* **Methods:**
+    * `new(window, url, ipc_callback)`
+    * `eval(js_string)`
+* **Security Detail:** The `ipc_callback` passed here is the "Border Crossing". Rust blindly fires this Proc whenever the WebView emits a message.
+
+#### D. `Tokra::Native::Proxy`
+* **Responsibility:** Thread-safe handle to wake up the loop.
+* **Methods:** `wake_up(payload)`
+* **Implementation:** Wraps `tao::event_loop::EventLoopProxy`. This is critical for Ractors to talk back to the UI.
+
+### 3. Ruby Implementation (`lib/tokra.rb`)
+
+The Ruby gem bootstraps the Ractor model.
+
+#### The Main Ractor (UI Thread)
+
+```ruby
+module Tokra
+  class App
+    def self.run(initial_url)
+      # 1. Create communication ports
+      ipc_port = Ractor::Port.new      # Main receives IPC from WebView
+      response_port = Ractor::Port.new # Main receives responses from Worker
+
+      # 2. Setup the logic worker
+      worker = Ractor.new(response_port) do |resp_port|
+        loop do
+          msg = Ractor.receive
+          result = yield(msg)  # User's logic runs here
+          resp_port << result
+        end
+      end
+
+      # 3. Setup Rust Windowing (Main Thread)
+      event_loop = Tokra::Native::EventLoop.new
+      proxy = event_loop.create_proxy
+
+      # 4. Define the IPC "Bridge" (must be shareable)
+      ipc_handler = Ractor.shareable_proc do |raw_msg|
+        ipc_port << raw_msg
+      end
+
+      window = Tokra::Native::Window.new(event_loop)
+      webview = Tokra::Native::WebView.new(window, initial_url, ipc_handler)
+
+      # 5. Block forever on Main Thread
+      event_loop.run do |event|
+        case event
+        when Tokra::Native::IpcEvent
+          # Security: Validate before forwarding
+          worker << { type: :ipc, payload: event.message, proxy: proxy }
+        when Tokra::Native::WakeUpEvent
+          # Response from worker - send to WebView
+          webview.eval("window.__tokra_callback(#{event.payload.to_json})")
+        when Tokra::Native::WindowCloseEvent
+          break
+        end
+      end
+    end
+  end
+end
+```
+
+#### The Security Implementation
+
+Security is enforced in **Ruby**, not Rust.
+
+```ruby
+class SecurityGuard
+  ALLOWLIST = {
+    "fs_read" => ->(path) { path.start_with?(APP_DATA_DIR) },
+    "net_req" => ->(url)  { url.start_with?("https://api.myapp.com") }
+  }.freeze
+
+  def self.authorize!(command, args)
+    raise SecurityError, "Access Denied: #{command}" unless ALLOWLIST[command]&.call(args)
+  end
+end
+```
+    
+### 4. Build System Specification
+* **Tooling:** Must use `rb_sys` gem to bridge Cargo and Make.
+* **Manifest:** `ext/tokra/extconf.rb` must use `create_rust_makefile("tokra/tokra")`.
+* **Extension:** The compiled binary must be reachable via `require "tokra/tokra"`.
+
+## Consequences
+
+### Positive
+* **Dev Velocity:** Logic changes happen in Ruby (Instant reload potential). Rust compilation is rare.
+* **Cost:** Rust contractor scope is fixed and small (~500 LOC).
+* **Performance:** UI is unblockable. Ractor move semantics avoid GC pressure during IPC.
+
+### Negative
+* **Complexity:** Ractor message passing is strictly async. The user must write async-aware Ruby code (promises/callbacks).
+* **Signals:** Standard Ruby signal trapping (Ctrl+C) is disabled; we rely on the Rust layer to catch OS signals.
+* **Memory:** Minimum 2 Ractors means slightly higher base memory usage than a single-threaded app.
+* **Packaging:** Requires bundling the compiled `.so`/`.dll` inside the gem.
+
+## References
+* [Magnus Documentation](https://docs.rs/magnus)
+* [Ruby 4.0 Ractor Guide](https://docs.ruby-lang.org/en/master/ractor.md)
+* [Wry IPC Interface](https://docs.rs/wry/latest/wry/struct.WebViewBuilder.html#method.with_ipc_handler)

data/doc/contributors/adr/002.md

@@ -0,0 +1,132 @@
+<!--
+SPDX-FileCopyrightText: 2026 Kerrick Long <me@kerricklong.com>
+
+SPDX-License-Identifier: CC-BY-SA-4.0
+-->
+
+# ADR 002: Tokra Rails - The Rack Adapter & "Serverless" Desktop
+
+## Status
+Accepted
+
+## Date
+2026-01-29
+
+## Context
+Developers want to use **Ruby on Rails** to build Tokra desktop applications.
+The traditional approach (Electron) involves spawning a child process running a TCP web server (like Puma) and pointing the WebView to `http://localhost:3000`.
+
+This approach has significant downsides:
+1.  **Security:** It opens a TCP port on the user's machine, which other processes can sniff.
+2.  **Performance:** It incurs TCP/IP loopback overhead.
+3.  **Management:** Dealing with "orphan" server processes when the app closes is difficult.
+
+We need a way to run Rails *inside* the Tokra process, leveraging the Ruby 4.0 architecture defined in [ADR 001].
+
+## Decision
+We will implement **Tokra Rails** as a direct Rack Adapter over a Wry Custom Protocol.
+
+We will **not** bundle Puma or any TCP server. Instead, we will treat the WebView's resource loader as the "Web Server" and the Rails App as a library function call.
+
+## The "100 Lines" Architecture
+
+### 1. The Mechanism: Custom Protocol (`rails://`)
+Instead of IPC (which is for JSON messages), we will use Wry's **Custom Protocol** feature.
+* **Rust Layer:** We add *one* generic method to our FFI: `register_protocol(scheme, ruby_proc)`.
+* **The Flow:**
+    1.  Frontend requests `rails://app/posts/1` (via Turbo, HTMX, or `fetch`).
+    2.  Rust intercepts the request.
+    3.  Rust passes the HTTP verb, headers, and body to the **Main Ractor** (Ruby).
+    4.  Main Ractor sends it to the **Rails Ractor**.
+    5.  Rails Ractor runs `MyApp::Application.call(env)`.
+    6.  The response (HTML/JSON) is handed back to Rust.
+
+### 2. The Ruby Code (`lib/tokra/rails/handler.rb`)
+
+This is the "100 lines" of Ruby. It is a standard `Rack::Handler` that translates the Tokra Protocol Struct into a Rack Environment Hash.
+
+```ruby
+# frozen_string_literal: true
+
+module Rack
+  module Handler
+    class Tokra
+      def self.run(app, options = {})
+        # The protocol handler must be a shareable proc since it's
+        # called from Rust across potential Ractor boundaries
+        handler = Ractor.shareable_proc do |req|
+          # 1. Map Request -> Rack Env
+          env = {
+            "REQUEST_METHOD"  => req.method,
+            "SCRIPT_NAME"     => "",
+            "PATH_INFO"       => req.path,
+            "QUERY_STRING"    => req.query,
+            "SERVER_NAME"     => "tokra",
+            "SERVER_PORT"     => "80",
+            "rack.version"    => Rack::VERSION,
+            "rack.input"      => StringIO.new(req.body),
+            "rack.errors"     => $stderr,
+            "rack.multithread" => false, # Requests are serialized through protocol handler
+            "rack.run_once"   => false,
+            "rack.url_scheme" => "rails"
+          }
+
+          # 2. Call Rails (In-Memory)
+          status, headers, body_proxy = app.call(env)
+
+          # 3. Map Response -> Rust Response
+          body_string = +""
+          body_proxy.each { |chunk| body_string << chunk }
+          body_proxy.close if body_proxy.respond_to?(:close)
+
+          # Return to Rust
+          { status: status, headers: headers, body: body_string }
+        end
+
+        # Register the "rails://" protocol hook in Rust
+        ::Tokra::Native.register_protocol("rails", &handler)
+      end
+    end
+  end
+end
+```
+
+### 3. The JS Code (`10 lines`)
+We need a tiny shim to ensure relative links work and Turbo behaves correctly with the custom protocol.
+
+    // app/javascript/tokra_shim.js
+    document.addEventListener("turbo:before-fetch-request", (event) => {
+      // Ensure Turbo knows we are using a custom protocol
+      // (Turbo 8+ handles non-HTTP protocols gracefully usually)
+    })
+    
+    // Optional: Bridge for "Server Push" via standard IPC
+    window.Tokra.on("rails:stream", (html) => {
+      Turbo.renderStreamMessage(html) 
+    })
+
+## Integration with Solid* & SQLite
+
+Because the Rails app runs inside the **Worker Ractor** (defined in ADR 001), strict isolation rules apply:
+
+1.  **SQLite Ownership:** `SQLite3::Database` objects are NOT Ractor-shareable.
+    * **Constraint:** You cannot establish the DB connection in the Main Ractor and pass it down.
+    * **Implementation:** The Rails app must lazy-load the connection (`ActiveRecord::Base.establish_connection`) *only* after the Worker Ractor has started.
+2.  **Solid Queue:** The background worker threads for Solid Queue spawn *inside* the Worker Ractor (or we spawn a dedicated `Queue Ractor`).
+3.  **Solid Cache:** Writes to the local SQLite DB.
+
+## Consequences
+
+### Positive
+* **Zero Latency:** No TCP handshake. Request/Response is a memory copy (or move).
+* **Native Assets:** Images/CSS served via `rails://app/assets/...` work exactly like standard web pages.
+* **Standard Rails:** Developers use `routes.rb`, Controllers, and Views exactly as normal. No "API-only" mode required.
+
+### Negative
+* **Streaming Limitations:** The `rails://` custom protocol does NOT support `ActionController::Live` or Turbo Streams (chunked responses).
+    * **Mitigation:** Streaming features must use the IPC Bridge (`Tokra.on('stream')`) instead of the protocol handler.
+* **Cookies:** The WebView manages cookies for the custom protocol, but we must ensure `set-cookie` headers are respected by Wry's custom protocol implementation.
+
+## Validation
+* **Is it 100 lines?** Yes. The Rack Handler logic is mostly hash mapping.
+* **Does Solid work?** Yes. Solid is just Ruby code and SQL. It doesn't know it's not running in a Puma process.