pikuri 0.0.1 → 0.0.3

metadata

@@ -1,234 +1,120 @@
 --- !ruby/object:Gem::Specification
 name: pikuri
 version: !ruby/object:Gem::Version
-  version: 0.0.1
+  version: 0.0.3
 platform: ruby
 authors:
 - Martin Vysny
 autorequire:
 bindir: bin
 cert_chain: []
-date: 2026-05-14 00:00:00.000000000 Z
+date: 2026-05-22 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
-  name: dentaku
+  name: pikuri-assistant
   requirement: !ruby/object:Gem::Requirement
     requirements:
-    - - "~>"
+    - - '='
       - !ruby/object:Gem::Version
-        version: '3.5'
+        version: 0.0.3
   type: :runtime
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
-    - - "~>"
+    - - '='
       - !ruby/object:Gem::Version
-        version: '3.5'
+        version: 0.0.3
 - !ruby/object:Gem::Dependency
-  name: faraday
+  name: pikuri-code
   requirement: !ruby/object:Gem::Requirement
     requirements:
-    - - "~>"
+    - - '='
       - !ruby/object:Gem::Version
-        version: '2.9'
+        version: 0.0.3
   type: :runtime
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
-    - - "~>"
+    - - '='
       - !ruby/object:Gem::Version
-        version: '2.9'
+        version: 0.0.3
 - !ruby/object:Gem::Dependency
-  name: nokogiri
+  name: pikuri-core
   requirement: !ruby/object:Gem::Requirement
     requirements:
-    - - "~>"
+    - - '='
       - !ruby/object:Gem::Version
-        version: '1.19'
+        version: 0.0.3
   type: :runtime
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
-    - - "~>"
+    - - '='
       - !ruby/object:Gem::Version
-        version: '1.19'
+        version: 0.0.3
 - !ruby/object:Gem::Dependency
-  name: pdf-reader
+  name: pikuri-mcp
   requirement: !ruby/object:Gem::Requirement
     requirements:
-    - - "~>"
+    - - '='
       - !ruby/object:Gem::Version
-        version: '2.15'
+        version: 0.0.3
   type: :runtime
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
-    - - "~>"
+    - - '='
       - !ruby/object:Gem::Version
-        version: '2.15'
+        version: 0.0.3
 - !ruby/object:Gem::Dependency
-  name: rainbow
+  name: pikuri-skills
   requirement: !ruby/object:Gem::Requirement
     requirements:
-    - - "~>"
+    - - '='
       - !ruby/object:Gem::Version
-        version: '3.1'
+        version: 0.0.3
   type: :runtime
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
-    - - "~>"
+    - - '='
       - !ruby/object:Gem::Version
-        version: '3.1'
+        version: 0.0.3
 - !ruby/object:Gem::Dependency
-  name: reverse_markdown
+  name: pikuri-workspace
   requirement: !ruby/object:Gem::Requirement
     requirements:
-    - - "~>"
+    - - '='
       - !ruby/object:Gem::Version
-        version: '3.0'
+        version: 0.0.3
   type: :runtime
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
-    - - "~>"
+    - - '='
       - !ruby/object:Gem::Version
-        version: '3.0'
-- !ruby/object:Gem::Dependency
-  name: ruby-readability
-  requirement: !ruby/object:Gem::Requirement
-    requirements:
-    - - "~>"
-      - !ruby/object:Gem::Version
-        version: '0.7'
-  type: :runtime
-  prerelease: false
-  version_requirements: !ruby/object:Gem::Requirement
-    requirements:
-    - - "~>"
-      - !ruby/object:Gem::Version
-        version: '0.7'
-- !ruby/object:Gem::Dependency
-  name: ruby_llm
-  requirement: !ruby/object:Gem::Requirement
-    requirements:
-    - - "~>"
-      - !ruby/object:Gem::Version
-        version: '1.15'
-  type: :runtime
-  prerelease: false
-  version_requirements: !ruby/object:Gem::Requirement
-    requirements:
-    - - "~>"
-      - !ruby/object:Gem::Version
-        version: '1.15'
-- !ruby/object:Gem::Dependency
-  name: tsort
-  requirement: !ruby/object:Gem::Requirement
-    requirements:
-    - - "~>"
-      - !ruby/object:Gem::Version
-        version: '0.2'
-  type: :runtime
-  prerelease: false
-  version_requirements: !ruby/object:Gem::Requirement
-    requirements:
-    - - "~>"
-      - !ruby/object:Gem::Version
-        version: '0.2'
-- !ruby/object:Gem::Dependency
-  name: tty-markdown
-  requirement: !ruby/object:Gem::Requirement
-    requirements:
-    - - "~>"
-      - !ruby/object:Gem::Version
-        version: '0.7'
-  type: :runtime
-  prerelease: false
-  version_requirements: !ruby/object:Gem::Requirement
-    requirements:
-    - - "~>"
-      - !ruby/object:Gem::Version
-        version: '0.7'
-- !ruby/object:Gem::Dependency
-  name: zeitwerk
-  requirement: !ruby/object:Gem::Requirement
-    requirements:
-    - - "~>"
-      - !ruby/object:Gem::Version
-        version: '2.7'
-  type: :runtime
-  prerelease: false
-  version_requirements: !ruby/object:Gem::Requirement
-    requirements:
-    - - "~>"
-      - !ruby/object:Gem::Version
-        version: '2.7'
+        version: 0.0.3
 description: |
-  A library for assembling AI assistants: Pikuri::Agent (a thin wrapper around
-  ruby_llm's chat loop), Pikuri::Tool with strict argument validation, a
-  listener surface for rendering / budgets / sub-agents, and a small set of
-  bundled tools (calculator, web search, web scrape, fetch, plus six coding
-  tools: read / write / edit / grep / glob / bash). Downstream projects
-  (notably the planned pikuri-tui) wire these into actual binaries. The repo
-  also ships `bin/pikuri-chat` and `bin/pikuri-code` as demo entry points,
-  but they are NOT installed by `gem install pikuri` — they exist to show
-  how to wire the library together and to support development.
+  +pikuri+ is the convenience bundle for the pikuri AI-assistant
+  toolkit. It ships no Ruby code of its own beyond a tiny entry
+  file that +require+'s each sibling gem; +gem install pikuri+
+  pulls in pikuri-core, pikuri-skills, pikuri-workspace,
+  pikuri-code, pikuri-mcp, and pikuri-assistant in one shot, and
+  +require 'pikuri'+ boots all of them.
+
+  Privacy-conscious users who want a minimal dependency tree to
+  audit should install +pikuri-core+ directly and opt into the
+  extension gems they actually need — same +bundle add+ pattern
+  Rails users have always had. See each pikuri-* gem's README
+  for its individual surface.
 email:
 - martin@vysny.me
 executables: []
 extensions: []
 extra_rdoc_files: []
 files:
-- CHANGELOG.md
-- GETTING_STARTED.md
-- LICENSE
 - README.md
 - lib/pikuri.rb
-- lib/pikuri/agent.rb
-- lib/pikuri/agent/chat_transport.rb
-- lib/pikuri/agent/context_window_detector.rb
-- lib/pikuri/agent/listener/in_memory_message_list.rb
-- lib/pikuri/agent/listener/message_listener.rb
-- lib/pikuri/agent/listener/step_limit.rb
-- lib/pikuri/agent/listener/terminal.rb
-- lib/pikuri/agent/listener/token_log.rb
-- lib/pikuri/agent/listener_list.rb
-- lib/pikuri/agent/message.rb
-- lib/pikuri/agent/synthesizer.rb
-- lib/pikuri/agent/tokens.rb
-- lib/pikuri/subprocess.rb
-- lib/pikuri/tool.rb
-- lib/pikuri/tool/bash.rb
-- lib/pikuri/tool/calculator.rb
-- lib/pikuri/tool/confirmer.rb
-- lib/pikuri/tool/edit.rb
-- lib/pikuri/tool/fetch.rb
-- lib/pikuri/tool/glob.rb
-- lib/pikuri/tool/grep.rb
-- lib/pikuri/tool/parameters.rb
-- lib/pikuri/tool/read.rb
-- lib/pikuri/tool/scraper/fetch_error.rb
-- lib/pikuri/tool/scraper/html.rb
-- lib/pikuri/tool/scraper/pdf.rb
-- lib/pikuri/tool/scraper/simple.rb
-- lib/pikuri/tool/search/brave.rb
-- lib/pikuri/tool/search/duckduckgo.rb
-- lib/pikuri/tool/search/engines.rb
-- lib/pikuri/tool/search/exa.rb
-- lib/pikuri/tool/search/rate_limiter.rb
-- lib/pikuri/tool/search/result.rb
-- lib/pikuri/tool/skill.rb
-- lib/pikuri/tool/skill_catalog.rb
-- lib/pikuri/tool/sub_agent.rb
-- lib/pikuri/tool/web_scrape.rb
-- lib/pikuri/tool/web_search.rb
-- lib/pikuri/tool/workspace.rb
-- lib/pikuri/tool/write.rb
-- lib/pikuri/url_cache.rb
-- lib/pikuri/version.rb
-- prompts/coding-system-prompt.txt
-- prompts/pikuri-chat.txt
 homepage: https://codeberg.org/mvysny/pikuri
 licenses:
 - MIT
@@ -255,5 +141,5 @@ requirements: []
 rubygems_version: 3.5.22
 signing_key:
 specification_version: 4
-summary: A small, privacy-first Ruby toolkit for building local AI assistants.
+summary: 'Convenience metagem: installs every pikuri-* gem.'
 test_files: []

data/CHANGELOG.md

@@ -1,62 +0,0 @@
-# Changelog
-
-All notable changes to pikuri are recorded here. Format follows
-[Keep a Changelog](https://keepachangelog.com/en/1.1.0/); the project
-uses semver as documented in `lib/pikuri/version.rb`.
-
-## [Unreleased]
-
-## [0.0.1] - 2026-05-14 — first packaged release
-
-The initial gem release. Pikuri is shipped as a **library** — there are
-no executables installed by `gem install pikuri`. The `bin/pikuri-chat`
-and `bin/pikuri-code` scripts in the source tree are dev/demo entry
-points; production binaries built on pikuri (notably the planned
-`pikuri-tui`) will live in their own downstream gems.
-
-### Added
-- `pikuri.gemspec` with runtime deps pulled from the previous `Gemfile`
-  (one source of truth; `Gemfile` now uses `gemspec`).
-- `Pikuri::VERSION` constant (`lib/pikuri/version.rb`); Zeitwerk is
-  told to ignore the file since the constant is `VERSION`, not
-  `Version`.
-- `LICENSE` (MIT) and gemspec license metadata.
-- `Pikuri::PROMPTS_DIR` and `Pikuri.prompt(name)` — downstream library
-  users can read pikuri's bundled system prompts as a starting point
-  for their own wiring.
-- `Tool::Bash` emits a loud warning at construction: the tool runs
-  commands unsandboxed under pikuri's UID and can read `~/.ssh`, AWS
-  credentials, etc. A future release will gate this behind a sandbox.
-- `Pikuri::Tool::SkillCatalog` + `Pikuri::Tool::Skill` — pikuri's
-  implementation of the [Agent Skills standard](https://agentskills.io/specification).
-  `SkillCatalog` discovers and validates `SKILL.md` files under the
-  standard `.pikuri/skills`, `.claude/skills`, `.agents/skills`
-  directories (precedence in that order); `Tool::Skill` is auto-
-  registered by `Agent#initialize` whenever the wired-in catalog is
-  non-empty, and the catalog's prompt block is appended to the system
-  prompt so the LLM sees the available inventory without an extra
-  round-trip.
-- `mise.toml` pinning Ruby 3.3, matching the gemspec floor.
-- `CHANGELOG.md` (this file).
-
-### Changed
-- **Namespace move.** Top-level `Agent`, `Tool`, and `UrlCache` are now
-  `Pikuri::Agent`, `Pikuri::Tool`, `Pikuri::UrlCache`. All bundled
-  tools, listeners, and helpers live under `Pikuri::*`. Standard gem
-  layout: `lib/pikuri.rb` + `lib/pikuri/**/*.rb`; `spec/` mirrors it.
-- `Pikuri::Agent::Listener::InMemoryList` renamed to `InMemoryMessageList`
-  to clarify what it records (message events).
-- `UrlCache::ROOT_DIR` follows the XDG Base Directory spec:
-  `$XDG_CACHE_HOME/pikuri/url_cache` if set, else
-  `~/.cache/pikuri/url_cache`. Previously `/tmp/pikuri/cache`.
-- `bin/pikuri-chat` and `bin/pikuri-code` read prompts via
-  `Pikuri.prompt(name)` instead of hand-rolled `__dir__` arithmetic.
-
-### Project scope
-- Pikuri targets **Linux**; macOS may work; Windows is unsupported.
-  Rationale: the eventual Bash-tool sandbox (Docker / bubblewrap) and
-  the existing reliance on POSIX shell + GNU coreutils + XDG layout
-  make a Windows port more cost than benefit.
-- Hard ceiling on source size: a privacy-conscious user should be able
-  to read pikuri end-to-end in an evening and decide whether to trust
-  it outside a sandbox. New features compete against that budget.

data/GETTING_STARTED.md

@@ -1,223 +0,0 @@
-# Getting started with pikuri-chat
-
-This guide walks you from a fresh checkout to a working privacy-first
-chatbot running entirely on your own machine. The assumed platform is
-Ubuntu (or another Debian-derived Linux); adapt the package commands if
-you're elsewhere.
-
-## 1. Clone and install
-
-```sh
-git clone https://codeberg.org/mvysny/pikuri.git
-cd pikuri
-
-# Ruby 3.x and Bundler. Pikuri has no Rails or native-extension
-# headaches — the stock distro packages are fine.
-sudo apt install ruby ruby-bundler
-
-bundle install
-```
-
-That installs all the gems pikuri needs (`ruby_llm`, `faraday`,
-`nokogiri`, `tty-markdown`, …) into your user gem path.
-
-## 2. Try to run pikuri-chat (and watch it fail)
-
-```sh
-./bin/pikuri-chat "Hello"
-```
-
-You'll see a connection error. That's expected — pikuri-chat ships
-pointed at a local `llama.cpp` server, and you don't have one running
-yet. We'll start one in the next step.
-
-This is the privacy property in action: pikuri does not silently fall
-back to a cloud provider. No model means no answer.
-
-## 3. Install llama.cpp
-
-`llama.cpp` is the project that actually runs the model. Ubuntu 24.04
-and newer have it packaged:
-
-```sh
-sudo apt install llama.cpp
-```
-
-This gives you `llama-server` on your `$PATH`. If your distro doesn't
-package it, follow the build instructions at
-<https://github.com/ggml-org/llama.cpp> — pikuri only needs the
-`llama-server` binary.
-
-## 4. Start the model
-
-The model `bin/pikuri-chat` is wired for is `unsloth/Qwen3.6-35B-A3B-GGUF`
-— a mixture-of-experts model from the Qwen series, quantized by the
-folks at Unsloth so it fits in regular hardware. `llama-server` can
-download it from Hugging Face for you on first run:
-
-```sh
-llama-server \
-  -hf unsloth/Qwen3.6-35B-A3B-GGUF \
-  --hf-file Qwen3.6-35B-A3B-UD-Q4_K_M.gguf \
-  -c 65536 \
-  --jinja
-```
-
-What each flag does:
-
-- `-hf unsloth/Qwen3.6-35B-A3B-GGUF` — Hugging Face repo to pull from.
-- `--hf-file Qwen3.6-35B-A3B-UD-Q4_K_M.gguf` — pick the
-  Q4_K_M quantization (good size/quality tradeoff).
-- `-c 65536` — 64K context window. Pikuri's agent loop accumulates
-  tool observations into the context, so headroom matters.
-- `--jinja` — enable Jinja chat templates. The Qwen3 series needs this
-  for correct tool-call formatting.
-
-**Expect this to be slow on CPU.** A 35B-parameter mixture-of-experts
-model running on CPU can manage a few tokens per second. If you have
-an NVIDIA or AMD GPU with enough VRAM, add `-ngl 99` to offload all
-layers onto the GPU — this is the single biggest speedup you can get.
-See `llama-server --help` and the
-[llama.cpp docs](https://github.com/ggml-org/llama.cpp/tree/master/tools/server)
-for tuning options (`-t` for thread count, `-ngl N` for partial GPU
-offload, `--mlock`, and friends).
-
-The server binds to `127.0.0.1:8080` by default, and `bin/pikuri-chat`
-is wired to `http://localhost:8080/v1` — so if you're running both on
-the same machine, no further configuration is needed. If your
-`llama-server` lives on another host, edit the `openai_api_base`
-string near the top of `bin/pikuri-chat` to match.
-
-## 5. Talk to it
-
-In a second terminal, leaving `llama-server` running:
-
-```sh
-./bin/pikuri-chat
-```
-
-You'll get a `>` prompt. Try something the model can't answer from
-memory alone — that's where the tools come in:
-
-```
-> What is 1837 * 4291, and what's the current Ruby stable version?
-```
-
-You should see the model emit reasoning, call the `calculator` tool
-for the multiplication, call `web_search` (and likely `web_scrape`)
-for the Ruby version, then reply in plain text. Use Ctrl+D or Ctrl+C
-to exit.
-
-## How the agentic loop works (and why it's private)
-
-Pikuri runs the standard *Thought → Tool-call → Observation* loop:
-
-1. The model receives your message plus the running conversation.
-2. It produces either a final answer (and the turn ends) or a tool
-   call — a structured request like *"call `web_search` with query
-   `…`"*.
-3. Pikuri executes the requested tool locally, capturing its output as
-   an *observation*.
-4. The observation is appended to the conversation and the model is
-   called again.
-
-The model itself runs entirely inside your `llama-server` process. It
-has **no network access** of its own — it can only reason and emit
-text. The single way information leaves your machine is when the model
-asks pikuri to call a network-touching tool, and pikuri actually
-performs that call on your behalf. If you never give the model network
-tools, nothing the model "thinks about" can ever leave the box.
-
-This is meaningfully stronger than the typical hosted-assistant
-arrangement: there is no provider receiving your prompts, no telemetry
-pipeline, and no fine-tuning corpus being assembled from your chats.
-
-If you'd like to *see* this loop implemented in a handful of files
-with nothing else in the way, the sister project
-[agentic-loop-demo](https://codeberg.org/mvysny/agentic-loop-demo) is
-written exactly for that. Pikuri uses the same shape, just wrapped in
-tools, listeners, and sub-agents.
-
-## What tools `bin/pikuri-chat` ships with
-
-Four tools, all defined in `lib/pikuri/tool/` and wired in `bin/pikuri-chat`:
-
-- **`calculator`** — evaluates an arithmetic expression with Dentaku.
-  Local, no network.
-- **`web_search`** — runs a search query through one of the configured
-  search providers and returns a Markdown list of titles, URLs, and
-  snippets. See below for the privacy posture of each provider.
-- **`web_scrape`** — fetches an HTML page or PDF, strips the chrome
-  with readability extraction, and returns the main content as
-  Markdown. The model typically chains `web_search` → pick a URL →
-  `web_scrape` to read the full article.
-- **`fetch`** — downloads a URL verbatim (JSON, CSV, robots.txt,
-  source files) without any rendering pass that would corrupt the
-  bytes.
-
-Plus a built-in *sub-agent* facility (enabled by
-`agent.allow_sub_agent`): the model can dispatch a focused side-quest
-to a fresh agent so the noisy intermediate observations don't pollute
-the main context.
-
-## Search providers and their privacy trade-offs
-
-`web_search` is a cascade across whichever providers you have
-configured. The orchestration lives in `lib/pikuri/tool/search/engines.rb`;
-each provider's privacy posture is documented in detail at the top of
-its source file.
-
-### DuckDuckGo (default, no setup)
-
-Always available — no API key, no registration. Pikuri scrapes the
-public HTML endpoint at `html.duckduckgo.com`. DuckDuckGo's policy is
-that they don't save your IP alongside searches, don't sell personal
-information, and proxy the request so downstream content providers
-can't profile you. The catch: DDG is largely a relay over Bing for
-web results, so the *query content* still reaches Microsoft for
-fulfillment, even though identifying info is stripped on the way out.
-
-Good enough for everyday curiosity. See
-`lib/pikuri/tool/search/duckduckgo.rb` for the full write-up.
-
-### Brave Search API (recommended for sensitive queries)
-
-The best privacy posture of the three. Brave does **not** train its
-models on your queries, does not link queries to identifiers, and
-retains query logs for 90 days by default (Zero Data Retention is
-available on their Enterprise plan).
-
-To enable it, register for a free API key at
-<https://api-dashboard.search.brave.com> — the "Data for Search" tier
-gives you 1 query/sec and ~2k queries/month at no cost. Then export
-the key before starting pikuri:
-
-```sh
-export BRAVE_SEARCH_API_KEY=your-key-here
-./bin/pikuri-chat
-```
-
-Once the env var is set, Brave joins the cascade and may be chosen
-over DuckDuckGo for any given query. See `lib/pikuri/tool/search/brave.rb`.
-
-### Exa (paid, weakest privacy)
-
-Optional. Exa is a paid neural-search API; activate it by setting
-`EXA_API_KEY`. Be aware that Exa's Terms grant them a
-*perpetual, irrevocable, sub-licensable* license over the queries you
-submit, and their privacy policy explicitly says queries are used for
-training. Don't enable Exa if your search history would be
-embarrassing or sensitive in a training set.
-
-See `lib/pikuri/tool/search/exa.rb` for the full privacy posture.
-
-### Recommended setup for best privacy
-
-1. Run `llama-server` locally (Step 4 above).
-2. Register a free Brave Search API key and `export
-   BRAVE_SEARCH_API_KEY=…`.
-3. Leave Exa unset.
-
-With this configuration, your prompts never leave your machine, and
-your search queries hit Brave under a clear no-training-on-queries
-commitment.

data/LICENSE

@@ -1,21 +0,0 @@
-The MIT License (MIT)
-
-Copyright (c) 2026 Martin Vysny
-
-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/lib/pikuri/agent/chat_transport.rb

@@ -1,41 +0,0 @@
-# frozen_string_literal: true
-
-module Pikuri
-  class Agent
-    # The trio of arguments that has to travel together to +RubyLLM.chat+
-    # for model resolution to come out the same on every construction:
-    # the model id, the provider hint, and the registry-bypass flag.
-    #
-    # Bundling them is structural protection against a recurring bug
-    # class — every forwarding site (the synthesizer rescue in
-    # {Agent#run_loop}, {Tool::SubAgent} spawning a sub-agent) used to
-    # pass the three individually, and dropping one routed the spawned
-    # chat to a different server or raised +RubyLLM::ModelNotFoundError+
-    # on the unknown model id. With a single value object the call site
-    # can't silently miss a field.
-    #
-    # Pure data carrier: no +RubyLLM+ references here, so the seam stays
-    # in {Agent}, +bin/pikuri-chat+, and {Tool}.
-    #
-    # @!attribute [r] model
-    #   @return [String, nil] LLM identifier; +nil+ defers to
-    #     +RubyLLM.config.default_model+ at {Agent} construction time
-    # @!attribute [r] provider
-    #   @return [Symbol, nil] forwarded to +RubyLLM.chat+. Required
-    #     together with +assume_model_exists+ when pointing at a local
-    #     OpenAI-compatible server (llama.cpp, gpustack, ...) whose model
-    #     ids are not in ruby_llm's bundled registry.
-    # @!attribute [r] assume_model_exists
-    #   @return [Boolean] forwarded to +RubyLLM.chat+; +true+ skips
-    #     ruby_llm's registry lookup and trusts the supplied model id.
-    #     Requires +provider+.
-    class ChatTransport < Data.define(:model, :provider, :assume_model_exists)
-      # @param model [String, nil]
-      # @param provider [Symbol, nil]
-      # @param assume_model_exists [Boolean]
-      def initialize(model:, provider: nil, assume_model_exists: false)
-        super
-      end
-    end
-  end
-end