robot_lab 0.3.0 → 0.3.1

data/.rubocop.yml

@@ -1,10 +0,0 @@
-inherit_from: ../.rubocop-base.yml
-
-# Core-only overrides. Exclude patterns here are relative to this repo and
-# merge with the shared base's excludes.
-AllCops:
-  Exclude:
-    - '_notes/**/*'
-
-Metrics/ClassLength:
-  Max: 650 # Robot is the central class; a future refactor could split it further

data/Archspec.rb

@@ -1,44 +0,0 @@
-component :robot,         in: "lib/robot_lab/robot.rb"
-component :robot_support, in: "lib/robot_lab/robot/**/*.rb"
-component :network,       in: ["lib/robot_lab/network.rb", "lib/robot_lab/bus_poller.rb"]
-component :memory,        in: ["lib/robot_lab/memory.rb", "lib/robot_lab/memory_change.rb"]
-component :mcp,           in: "lib/robot_lab/mcp/**/*.rb"
-component :sandbox,       in: ["lib/robot_lab/sandbox.rb", "lib/robot_lab/sandbox/**/*.rb"]
-component :streaming,     in: "lib/robot_lab/streaming/**/*.rb"
-component :budget,        in: "lib/robot_lab/budget/**/*.rb"
-component :hooks,         in: %w[
-  lib/robot_lab/hook.rb
-  lib/robot_lab/hook_context.rb
-  lib/robot_lab/hook_registry.rb
-  lib/robot_lab/hooks.rb
-]
-component :tools, in: %w[
-  lib/robot_lab/tool.rb
-  lib/robot_lab/tool_config.rb
-  lib/robot_lab/tool_manifest.rb
-  lib/robot_lab/script_tool.rb
-]
-component :config, in: ["lib/robot_lab/config.rb", "lib/robot_lab/run_config.rb"]
-
-# NOTE: every file here reopens `module RobotLab`, so a `dependencies.forbid`
-# rule keyed on components (e.g. `memory.cannot_use :robot`) treats a plain
-# `RobotLab.config` call as "depends on every component" — every file
-# "defines" the bare RobotLab constant. Naming the actual target constants
-# instead of components sidesteps that ambiguity.
-
-# Memory is a low-level primitive shared by Robot and Network; it must not
-# depend back on the things that depend on it.
-memory.cannot_reference_constants "RobotLab::Robot", "RobotLab::Network"
-
-# MCP is an external-tool integration layer that Robot/Network consume; it
-# must not reach back into the objects that use it.
-mcp.cannot_reference_constants "RobotLab::Robot", "RobotLab::Network"
-
-# Sandbox runs untrusted/generated code paths and should have the smallest
-# possible surface area — no reaching into orchestration or memory internals.
-sandbox.cannot_reference_constants "RobotLab::Robot", "RobotLab::Network", "RobotLab::Memory"
-
-# Config/RunConfig sits at the bottom of the configuration cascade
-# (RobotLab.config -> Network -> Robot -> template -> task -> runtime) and
-# must not depend upward on the objects it configures.
-config.cannot_reference_constants "RobotLab::Robot", "RobotLab::Network"

data/CLAUDE.md

@@ -1,141 +0,0 @@
-# CLAUDE.md
-
-This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
-
-## Project Overview
-
-RobotLab is a Ruby framework for building and orchestrating multi-robot LLM workflows. It provides:
-- **Robots**: LLM agents with tools, templates, and memory
-- **Networks**: Orchestration of multiple robots with routing logic
-- **MCP Integration**: Model Context Protocol for external tool servers
-- **Rails Integration**: Generators and ActiveRecord support for conversation history
-
-Built on top of [ruby_llm](https://rubyllm.com) and uses Zeitwerk for autoloading.
-
-## Commands
-
-```bash
-# Run all tests
-bundle exec rake test
-
-# Run a single test file
-bundle exec rake test_file[robot_lab/robot_test.rb]
-
-# Run tests with verbose output
-bundle exec rake test_verbose
-
-# Run integration tests only
-bundle exec rake integration
-
-# Lint with RuboCop
-bundle exec rubocop
-
-# Auto-fix RuboCop offenses
-bundle exec rubocop -a
-
-# Run all examples
-bundle exec rake examples:all
-
-# Run specific example by number (e.g., 01, 02)
-bundle exec rake examples:run[1]
-```
-
-## Architecture
-
-### Core Classes
-
-- **`RobotLab`** (`lib/robot_lab.rb`): Module entry point with factory methods `build()` for robots and `create_network()` for networks
-- **`Robot`** (`lib/robot_lab/robot.rb`): Subclass of `RubyLLM::Agent` with template-based prompts, tools, MCP clients, and memory. Creates a persistent chat on initialization. Use `robot.run("...")` to interact. When standalone uses its own memory; when in a network uses shared network memory
-- **`Network`** (`lib/robot_lab/network.rb`): Orchestrates multiple robots with routing logic. Robots execute sequentially sharing memory. Router is a lambda that returns robot names
-- **`NetworkRun`** (`lib/robot_lab/network_run.rb`): Stateful execution of a network run with isolated memory clone
-
-### RunConfig
-
-- **`RunConfig`** (`lib/robot_lab/run_config.rb`): Shared configuration object for LLM, tools, callbacks, and infrastructure settings. Flows through the hierarchy: `RobotLab.config -> Network -> Robot -> Template front matter -> Task -> Runtime`. Supports keyword construction, block DSL, merge semantics (more-specific wins), and `apply_to(chat)` for LLM field application. Both Robot and Network accept `config:` parameter. Infrastructure fields include: `bus`, `enable_cache`, `max_tool_rounds`, `token_budget`, `ractor_pool_size`, `max_concurrent_robots`, `doom_loop_threshold`, `auto_compact`, `compact_threshold`.
-
-### Memory System
-
-- **`Memory`** (`lib/robot_lab/memory.rb`): Key-value store with reserved keys (`:data`, `:results`, `:messages`, `:session_id`, `:cache`). Supports Redis backend. Semantic caching via RubyLLM::SemanticCache when the optional ruby_llm-semantic_cache gem is installed (`memory.cache` is nil otherwise)
-
-### MCP (Model Context Protocol)
-
-- **`MCP::Client`** (`lib/robot_lab/mcp/client.rb`): Connects to MCP servers
-- **Transports** (`lib/robot_lab/mcp/transports/`): stdio, websocket, SSE, streamable HTTP
-
-### Built-in Tools
-
-- **`AskUser`** (`lib/robot_lab/ask_user.rb`): Tool that lets a robot ask the user a question via the terminal. Supports open-ended text, multiple choice, and default values. IO sourced from `robot.input`/`robot.output` (defaults to `$stdin`/`$stdout`)
-
-### Adapters
-
-Provider adapters in `lib/robot_lab/adapters/`: Anthropic, OpenAI, Gemini (for provider-specific formatting)
-
-### Configuration Hierarchy
-
-Tools and MCP servers use hierarchical configuration: `runtime > robot > network > global config`. Values can be `:none`, `:inherit`, or explicit arrays.
-
-## Key Patterns
-
-### Creating Robots
-
-```ruby
-# Bare robot (no template or prompt)
-robot = RobotLab.build
-robot.with_instructions("You are helpful.").run("Hello!")
-
-# With template (.md file in prompts directory with YAML front matter)
-robot = RobotLab.build(name: "helper", template: :helper, context: { key: "value" })
-result = robot.run("Hello!")
-
-# With inline system prompt
-robot = RobotLab.build(name: "bot", system_prompt: "You are helpful.")
-result = robot.run("What can you do?")
-
-# With tools
-robot = RobotLab.build(name: "bot", system_prompt: "...", local_tools: [my_tool])
-
-# Chaining with_* methods
-robot.with_temperature(0.9).with_model("claude-sonnet-4").run("Be creative!")
-```
-
-### Creating Networks
-
-```ruby
-router = ->(args) { args.call_count.zero? ? ["classifier"] : nil }
-network = RobotLab.create_network(name: "support", robots: [robot1, robot2], router: router)
-result = network.run(message: "Hello")
-```
-
-### Router Args
-
-Router receives `Router::Args` with: `context`, `network`, `stack`, `call_count`, `last_result`
-
-## Testing
-
-- Uses Minitest with SimpleCov for coverage
-- Test helper at `test/test_helper.rb` provides `build_robot`, `build_network`, `build_tool` helpers
-- Templates for tests are in `examples/prompts/`
-- VCR and WebMock for HTTP stubbing
-
-## Dependencies
-
-Core: zeitwerk, ruby_llm (~> 2.0.0.rc3), prompt_manager, async, simple_flow, state_machines
-
-Optional: ruby_llm-semantic_cache (Memory#cache; no ruby_llm 2.0-compatible release yet — Memory runs with caching disabled when absent), classifier (compress_history), ruby_llm-providers-lms (local LM Studio provider used by the examples: qwen/qwen3.8-27b for complex work, openai/gpt-oss-20b for simple demos)
-
-### Templates
-
-Templates use prompt_manager format: single `.md` files with YAML front matter in the configured prompts directory.
-
-```markdown
----
-description: A helpful assistant
-parameters:
-  company_name: null
-  tone: friendly
----
-You are a helpful assistant for <%= company_name %>.
-Respond in a <%= tone %> manner.
-```
-
-Front matter supports: `description`, `parameters` (null = required), LLM config keys (`model`, `temperature`, `top_p`, `top_k`, `max_tokens`, etc.), and robot extras (`robot_name`, `tools`, `mcp`). Constructor-provided values always override front matter.

data/COMMITS.md

@@ -1,196 +0,0 @@
----
-url: https://www.conventionalcommits.org/en/v1.0.0/
-title: Conventional Commits
-description: A specification for adding human and machine readable meaning to commit messages
-access_date: 2025-07-31T20:51:29.000Z
-current_date: 2025-07-31T20:51:29.601Z
----
-
-# Conventional Commits
-
-A specification for adding human and machine readable meaning to commit messages
-
- Quick Summary Full Specification Contribute
-
-# Conventional Commits 1.0.0
-
-## Summary
-
-The Conventional Commits specification is a lightweight convention on top of commit messages. It provides an easy set of rules for creating an explicit commit history; which makes it easier to write automated tools on top of. This convention dovetails with SemVer, by describing the features, fixes, and breaking changes made in commit messages.
-
-The commit message should be structured as follows:
-
----
-
-```
-<type>[optional scope]: <description>
-
-[optional body]
-
-[optional footer(s)]
-
-```
-
----
-
-The commit contains the following structural elements, to communicate intent to the consumers of your library:
-
-1. **fix:** a commit of the _type_ `fix` patches a bug in your codebase (this correlates with `PATCH` in Semantic Versioning).
-2. **feat:** a commit of the _type_ `feat` introduces a new feature to the codebase (this correlates with `MINOR` in Semantic Versioning).
-3. **BREAKING CHANGE:** a commit that has a footer `BREAKING CHANGE:`, or appends a `!` after the type/scope, introduces a breaking API change (correlating with `MAJOR` in Semantic Versioning). A BREAKING CHANGE can be part of commits of any _type_.
-4. _types_ other than `fix:` and `feat:` are allowed, for example @commitlint/config-conventional (based on the Angular convention) recommends `build:`, `chore:`,`ci:`, `docs:`, `style:`, `refactor:`, `perf:`, `test:`, and others.
-5. _footers_ other than `BREAKING CHANGE: <description>` may be provided and follow a convention similar to git trailer format.
-
-Additional types are not mandated by the Conventional Commits specification, and have no implicit effect in Semantic Versioning (unless they include a BREAKING CHANGE). A scope may be provided to a commit’s type, to provide additional contextual information and is contained within parenthesis, e.g., `feat(parser): add ability to parse arrays`.
-
-## Examples
-
-### Commit message with description and breaking change footer
-
-```
-feat: allow provided config object to extend other configs
-
-BREAKING CHANGE: `extends` key in config file is now used for extending other config files
-
-```
-
-### Commit message with `!` to draw attention to breaking change
-
-```
-feat!: send an email to the customer when a product is shipped
-
-```
-
-### Commit message with scope and `!` to draw attention to breaking change
-
-```
-feat(api)!: send an email to the customer when a product is shipped
-
-```
-
-### Commit message with both `!` and BREAKING CHANGE footer
-
-```
-chore!: drop support for Node 6
-
-BREAKING CHANGE: use JavaScript features not available in Node 6.
-
-```
-
-### Commit message with no body
-
-```
-docs: correct spelling of CHANGELOG
-
-```
-
-### Commit message with scope
-
-```
-feat(lang): add Polish language
-
-```
-
-### Commit message with multi-paragraph body and multiple footers
-
-```
-fix: prevent racing of requests
-
-Introduce a request id and a reference to latest request. Dismiss
-incoming responses other than from latest request.
-
-Remove timeouts which were used to mitigate the racing issue but are
-obsolete now.
-
-Reviewed-by: Z
-Refs: #123
-
-```
-
-## Specification
-
-The key words “MUST”, “MUST NOT”, “REQUIRED”, “SHALL”, “SHALL NOT”, “SHOULD”, “SHOULD NOT”, “RECOMMENDED”, “MAY”, and “OPTIONAL” in this document are to be interpreted as described in RFC 2119.
-
-1. Commits MUST be prefixed with a type, which consists of a noun, `feat`, `fix`, etc., followed by the OPTIONAL scope, OPTIONAL `!`, and REQUIRED terminal colon and space.
-2. The type `feat` MUST be used when a commit adds a new feature to your application or library.
-3. The type `fix` MUST be used when a commit represents a bug fix for your application.
-4. A scope MAY be provided after a type. A scope MUST consist of a noun describing a section of the codebase surrounded by parenthesis, e.g., `fix(parser):`
-5. A description MUST immediately follow the colon and space after the type/scope prefix. The description is a short summary of the code changes, e.g., _fix: array parsing issue when multiple spaces were contained in string_.
-6. A longer commit body MAY be provided after the short description, providing additional contextual information about the code changes. The body MUST begin one blank line after the description.
-7. A commit body is free-form and MAY consist of any number of newline separated paragraphs.
-8. One or more footers MAY be provided one blank line after the body. Each footer MUST consist of a word token, followed by either a `:<space>` or `<space>#` separator, followed by a string value (this is inspired by the git trailer convention).
-9. A footer’s token MUST use `-` in place of whitespace characters, e.g., `Acked-by` (this helps differentiate the footer section from a multi-paragraph body). An exception is made for `BREAKING CHANGE`, which MAY also be used as a token.
-10. A footer’s value MAY contain spaces and newlines, and parsing MUST terminate when the next valid footer token/separator pair is observed.
-11. Breaking changes MUST be indicated in the type/scope prefix of a commit, or as an entry in the footer.
-12. If included as a footer, a breaking change MUST consist of the uppercase text BREAKING CHANGE, followed by a colon, space, and description, e.g.,_BREAKING CHANGE: environment variables now take precedence over config files_.
-13. If included in the type/scope prefix, breaking changes MUST be indicated by a`!` immediately before the `:`. If `!` is used, `BREAKING CHANGE:` MAY be omitted from the footer section, and the commit description SHALL be used to describe the breaking change.
-14. Types other than `feat` and `fix` MAY be used in your commit messages, e.g., _docs: update ref docs._
-15. The units of information that make up Conventional Commits MUST NOT be treated as case sensitive by implementors, with the exception of BREAKING CHANGE which MUST be uppercase.
-16. BREAKING-CHANGE MUST be synonymous with BREAKING CHANGE, when used as a token in a footer.
-
-## Why Use Conventional Commits
-
-* Automatically generating CHANGELOGs.
-* Automatically determining a semantic version bump (based on the types of commits landed).
-* Communicating the nature of changes to teammates, the public, and other stakeholders.
-* Triggering build and publish processes.
-* Making it easier for people to contribute to your projects, by allowing them to explore a more structured commit history.
-
-## FAQ
-
-### How should I deal with commit messages in the initial development phase?
-
-We recommend that you proceed as if you’ve already released the product. Typically _somebody_, even if it’s your fellow software developers, is using your software. They’ll want to know what’s fixed, what breaks etc.
-
-### Are the types in the commit title uppercase or lowercase?
-
-Any casing may be used, but it’s best to be consistent.
-
-### What do I do if the commit conforms to more than one of the commit types?
-
-Go back and make multiple commits whenever possible. Part of the benefit of Conventional Commits is its ability to drive us to make more organized commits and PRs.
-
-### Doesn’t this discourage rapid development and fast iteration?
-
-It discourages moving fast in a disorganized way. It helps you be able to move fast long term across multiple projects with varied contributors.
-
-### Might Conventional Commits lead developers to limit the type of commits they make because they’ll be thinking in the types provided?
-
-Conventional Commits encourages us to make more of certain types of commits such as fixes. Other than that, the flexibility of Conventional Commits allows your team to come up with their own types and change those types over time.
-
-### How does this relate to SemVer?
-
-`fix` type commits should be translated to `PATCH` releases. `feat` type commits should be translated to `MINOR` releases. Commits with `BREAKING CHANGE` in the commits, regardless of type, should be translated to `MAJOR` releases.
-
-### How should I version my extensions to the Conventional Commits Specification, e.g. `@jameswomack/conventional-commit-spec`?
-
-We recommend using SemVer to release your own extensions to this specification (and encourage you to make these extensions!)
-
-### What do I do if I accidentally use the wrong commit type?
-
-#### When you used a type that’s of the spec but not the correct type, e.g. `fix` instead of `feat`
-
-Prior to merging or releasing the mistake, we recommend using `git rebase -i` to edit the commit history. After release, the cleanup will be different according to what tools and processes you use.
-
-#### When you used a type _not_ of the spec, e.g. `feet` instead of `feat`
-
-In a worst case scenario, it’s not the end of the world if a commit lands that does not meet the Conventional Commits specification. It simply means that commit will be missed by tools that are based on the spec.
-
-### Do all my contributors need to use the Conventional Commits specification?
-
-No! If you use a squash based workflow on Git lead maintainers can clean up the commit messages as they’re merged—adding no workload to casual committers. A common workflow for this is to have your git system automatically squash commits from a pull request and present a form for the lead maintainer to enter the proper git commit message for the merge.
-
-### How does Conventional Commits handle revert commits?
-
-Reverting code can be complicated: are you reverting multiple commits? if you revert a feature, should the next release instead be a patch?
-
-Conventional Commits does not make an explicit effort to define revert behavior. Instead we leave it to tooling authors to use the flexibility of _types_ and _footers_ to develop their logic for handling reverts.
-
-One recommendation is to use the `revert` type, and a footer that references the commit SHAs that are being reverted:
-
-```
-revert: let us never again speak of the noodle incident
-
-Refs: 676104e, a215868
-
-```

data/Rakefile

@@ -1,193 +0,0 @@
-# frozen_string_literal: true
-
-# Quality gates (quality, rubocop_check, flog_check, flay_check,
-# archspec_check, ...), doc *serving*, and the gem lifecycle (build, install,
-# release) live in asgard — see .loki and the shared dev/*.loki files it
-# imports. This Rakefile keeps the tasks asgard delegates to (tests,
-# integration, examples, docs:build).
-
-require "rake/testtask"
-
-Rake::TestTask.new(:test) do |t|
-  t.libs << "test"
-  t.libs << "lib"
-  t.test_files = FileList["test/**/*_test.rb"]
-  t.verbose = true
-  # Load test_helper before any tests run to ensure SimpleCov starts first
-  t.ruby_opts << "-rtest_helper"
-end
-
-task default: :test
-
-desc "Run tests with verbose output"
-task :test_verbose do
-  ENV["TESTOPTS"] = "--verbose"
-  Rake::Task[:test].invoke
-end
-
-desc "Run a single test file"
-task :test_file, [:file] do |_t, args|
-  ruby "test/#{args[:file]}"
-end
-
-desc "Run integration tests only"
-Rake::TestTask.new(:integration) do |t|
-  t.libs << "test"
-  t.libs << "lib"
-  t.test_files = FileList["test/integration/**/*_test.rb"]
-  t.verbose = true
-  t.ruby_opts << "-rtest_helper"
-end
-
-namespace :examples do
-  # Map of subdirectory-based demos to their entry point scripts
-  SUBDIR_ENTRY_POINTS = {
-    "14_rusty_circuit" => "open_mic.rb",
-    "15_memory_network_and_bus" => "editorial_pipeline.rb",
-    "16_writers_room" => "writers_room.rb",
-    "27_incident_response" => "incident_response.rb"
-  }.freeze
-
-  # Subdirectory demos that are standalone apps (not run via `ruby`)
-  STANDALONE_APPS = {
-    "18_rails" => { setup: "bin/setup", run: "bin/dev" }
-  }.freeze
-
-  # Examples that require external services or user setup not guaranteed to be present
-  EXTERNAL_SERVICE_EXAMPLES = {
-    "33_stock_generator.rb" => "Redis server on localhost:6379",
-    "33_stock_predictor.rb" => "Redis server on localhost:6379 + running 33_stock_generator",
-    "34_agentskills.rb"     => "AgentSkills skill file at ~/.prompts/skills/code_reviewer/SKILL.md"
-  }.freeze
-
-  desc "Run all examples (excludes standalone apps like 18_rails)"
-  task :all do
-    failed = []
-
-    # Single-file examples
-    Dir.glob("examples/*.rb").each do |example|
-      base = File.basename(example)
-
-      if EXTERNAL_SERVICE_EXAMPLES.key?(base)
-        puts "\n#{'=' * 60}"
-        puts "Skipped: #{example} (requires #{EXTERNAL_SERVICE_EXAMPLES[base]})"
-        puts '=' * 60
-        next
-      end
-
-      puts "\n#{'=' * 60}"
-      puts "Running: #{example}"
-      puts '=' * 60
-      begin
-        ruby example
-      rescue RuntimeError => e
-        puts "FAILED: #{example} — #{e.message}"
-        failed << example
-      end
-    end
-
-    # Subdirectory-based demos
-    SUBDIR_ENTRY_POINTS.each do |dir, entry|
-      path = "examples/#{dir}/#{entry}"
-      next unless File.exist?(path)
-
-      puts "\n#{'=' * 60}"
-      puts "Running: #{path}"
-      puts '=' * 60
-      begin
-        ruby path
-      rescue RuntimeError => e
-        puts "FAILED: #{path} — #{e.message}"
-        failed << path
-      end
-    end
-
-    # Remind about standalone apps
-    STANDALONE_APPS.each do |dir, commands|
-      puts "\n#{'=' * 60}"
-      puts "Skipped: examples/#{dir} (standalone app)"
-      puts "  Setup: cd examples/#{dir} && #{commands[:setup]}"
-      puts "  Run:   cd examples/#{dir} && #{commands[:run]}"
-      puts '=' * 60
-    end
-
-    if failed.any?
-      puts "\n#{'=' * 60}"
-      puts "#{failed.size} example(s) failed:"
-      failed.each { |f| puts "  #{f}" }
-      puts '=' * 60
-      exit 1
-    end
-  end
-
-  desc "Run a specific example by number (e.g., rake examples:run[1])"
-  task :run, [:num] do |_t, args|
-    padded = args[:num].rjust(2, '0')
-
-    # Try single-file example first
-    example = Dir.glob("examples/#{padded}_*.rb").first
-    if example
-      ruby example
-      next
-    end
-
-    # Try subdirectory-based demo
-    dir = Dir.glob("examples/#{padded}_*/").first
-    if dir
-      dir_name = File.basename(dir)
-
-      # Check if it's a standalone app
-      if STANDALONE_APPS.key?(dir_name)
-        commands = STANDALONE_APPS[dir_name]
-        puts "Example #{args[:num]} is a standalone app (#{dir_name})."
-        puts "  Setup: cd examples/#{dir_name} && #{commands[:setup]}"
-        puts "  Run:   cd examples/#{dir_name} && #{commands[:run]}"
-        next
-      end
-
-      entry = SUBDIR_ENTRY_POINTS[dir_name]
-      if entry && File.exist?(File.join(dir, entry))
-        ruby File.join(dir, entry)
-      else
-        puts "Example #{args[:num]} directory found (#{dir_name}) but no entry point configured"
-      end
-    else
-      puts "Example #{args[:num]} not found"
-    end
-  end
-
-  desc "Setup the Rails demo app (example 18)"
-  task :rails_setup do
-    Dir.chdir("examples/18_rails") do
-      sh "bin/setup"
-    end
-  end
-
-  desc "Start the Rails demo app (example 18)"
-  task :rails do
-    Dir.chdir("examples/18_rails") do
-      sh "bin/dev"
-    end
-  end
-end
-
-namespace :docs do
-  desc "Build all documentation (YARD and MkDocs)"
-  task build: %i[yard mkdocs]
-
-  desc "Clean generated documentation"
-  task :clean do
-    rm_rf "doc"
-    rm_rf "site"
-  end
-
-  desc "Build YARD API documentation"
-  task :yard do
-    sh "yard doc"
-  end
-
-  desc "Build MkDocs documentation"
-  task :mkdocs do
-    sh "mkdocs build"
-  end
-end

data/_typos.toml

@@ -1,21 +0,0 @@
-# False-positive suppressions for the typos quality gate (asgard).
-# Everything here was reviewed by hand — see git history for context.
-
-[files]
-extend-exclude = [
-  # Example transcripts / articles: prose quotes real names ("Damon Clark")
-  # and SQL-ish plurals ("SELECTs") that typos mis-parses.
-  "examples/ruboruby.md",
-  "examples/25_history_search/conversation.jsonl",
-]
-
-[default.extend-identifiers]
-# Robot names in lib/robot_lab/names.rb
-BATs     = "BATs"
-Damon    = "Damon"
-Mata_Nui = "Mata_Nui"
-Pris     = "Pris"
-S1MONE   = "S1MONE"
-# Test-local variable names
-ba  = "ba"   # b→a similarity (convergence_test.rb)
-thr = "thr"  # thread handle (connection_poller_test.rb)