robot_lab 0.0.4 → 0.0.6

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 8d3bfa06c07301b03b01359a15a945374b135f2055c77396ad456a916917a742
-  data.tar.gz: 0b9e81d50841bf9a56d4efcc8f4175f34aa0e17702c89cc4bd5d4750631c0f68
+  metadata.gz: db26fa8aa3d47eb49face5b344cd1b41ed6e148a0460514b54913b5973ca9cc1
+  data.tar.gz: 79f2a71535ddaabd6f2a7c5dceaf3aefad10e3e51b4c0ccbd04fbe82c7804f57
 SHA512:
-  metadata.gz: 15649fd320dd84530d49884900d99c2cdc98ddd5841948b052ed6b3a6f3d0fa9cec3e80636883f6d2bcd5b5a8ffe6b61ad681dc907faf5e881f48ac05ebef0fd
-  data.tar.gz: cdd136aad382247babb5639cf3a2b0b35db5086b33661823a6e00d8099f2a18a57325c3ed57f3474d23ee8f317f65c1f0b70911d349ad04f111d80cac03dd8c9
+  metadata.gz: 832389808ec464678849736bb0d9fceca5dd67a5a3fa1e4c0486367bdf20a389257f4bfdeeb3afc9ca8619168274eb2a7cbed2c0376e358c902030ee26b105de
+  data.tar.gz: fb57b2e6cb329f6c116cbd7cb81a60bb68a9daeddc6e45a1f859690cc7f44ff3074eb4dfcdf0240b6a95f3786d992fc31c6edc3ed61fd2f838b435a19b550876

data/CHANGELOG.md

@@ -11,6 +11,56 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
+## [0.0.6] - 2026-02-17 [unreleased]
+
+### Added
+
+- **Writers' Room example** (`examples/16_writers_room/`) — Self-Organizing Group (SOG) demo where identical writer robots collaborate to produce a 10-chapter fiction novella
+  - Writer class with `fresh_chat!` pattern to prevent RubyLLM empty text content block corruption in bus-based robots
+  - 7 tools: Broadcast, DirectMessage, ReadMemory, WriteMemory, ListMemory, SpawnWriter, MarkComplete
+  - Room class with bus, shared memory, writer roster, heartbeat-based progress nudging, and structured logging
+  - Display class with color-coded terminal output, word wrapping, and optional log file
+  - CLI with `--premise`, `--writers`, `--log`, `--timeout`, `-h`/`--help` options
+  - Shared prompt template (`prompts/writer.md`) — all writers use the same instructions with no hierarchy
+- **Network pipeline tests** (`test/robot_lab/network_pipeline_test.rb`) for sequential robot execution and memory sharing
+- **`dispatch_async` error handling** — exceptions inside async dispatch are now logged and contained instead of propagating
+
+### Changed
+
+- Bumped version to 0.0.6
+- **Removed `Errors` module** and related test file — unused error classes cleaned out
+- **Zeitwerk autoloading optimized** — streamlined loader configuration in `lib/robot_lab.rb`
+- Rakefile updated with `16_writers_room` entry point in `SUBDIR_ENTRY_POINTS`
+
+## [0.0.5] - 2026-02-17 [unreleased]
+
+### Added
+
+- **`RunConfig` class** (`lib/robot_lab/run_config.rb`) for shared operational defaults
+  - Field categories: LLM (`model`, `temperature`, `top_p`, `top_k`, `max_tokens`, `presence_penalty`, `frequency_penalty`, `stop`), tools (`mcp`, `tools`), callbacks (`on_tool_call`, `on_tool_result`), infrastructure (`bus`, `enable_cache`)
+  - Keyword construction, block DSL, and method chaining
+  - Merge semantics: more-specific config's non-nil values win
+  - `apply_to(chat)` applies LLM fields to a RubyLLM chat
+  - `from_front_matter(metadata)` extracts config from template YAML front matter
+  - `to_h`, `to_json_hash` (skips Procs/IO), `empty?`, `key?`, `==`, `inspect`
+  - Full test suite (`test/robot_lab/run_config_test.rb`, 39 tests)
+- **`config:` parameter** on `Robot.new`, `Network.new`, `Network#task`, `RobotLab.build`, and `RobotLab.create_network` for passing RunConfig instances
+- **Configuration inheritance chain**: `RobotLab.config` (global) -> `network.config` -> task `config:` -> `robot.config` -> template front matter -> constructor kwargs
+- **`robot.config` / `network.config` accessors** (`attr_reader`) returning the effective RunConfig
+- **`RobotLab.configure`** block-style configuration method yielding the config object
+- **Bus processing guard** (`handle_incoming_delivery`) serializing message deliveries across bus-connected robots to prevent Async fiber re-entrancy corrupting chat message ordering
+- Documentation for RunConfig across README, configuration guide, network guide, and API reference
+- Updated examples (`03_network`, `08_llm_config`, `09_chaining`, `11_network_introspection`) demonstrating RunConfig usage
+
+### Changed
+
+- Bumped version to 0.0.5
+- **Template rendering refactored** to use `RunConfig.from_front_matter` instead of `apply_front_matter_config` — front matter config is now merged with the robot's RunConfig before applying to chat
+- **MCP/tools hierarchy resolution** now accepts `network_config:` parameter instead of directly accessing the network object, enabling RunConfig-driven configuration flow
+- **`dispatch_async`** simplified to exclusively use Async fibers, removing Thread-based fallback
+- **`Memory#get`** improved nil value handling — uses `@backend.key?()` instead of nil check for correct nil value storage and retrieval
+- **`Memory#clone`** optimized — results and messages are referenced directly instead of duplicated
+
 ## [0.0.4] - 2026-02-16 [unreleased]
 
 ### Added

data/README.md

@@ -187,6 +187,57 @@ robot = RobotLab.build(
 )
 ```
 
+### Shared Configuration with RunConfig
+
+`RunConfig` lets you define operational defaults that flow through the hierarchy: Network -> Robot -> Template -> Task -> Runtime. Use it to share LLM settings across multiple robots or an entire network.
+
+```ruby
+# Create a shared config
+shared = RobotLab::RunConfig.new(
+  model: "claude-sonnet-4",
+  temperature: 0.7,
+  max_tokens: 2000
+)
+
+# Apply to individual robots
+robot = RobotLab.build(
+  name: "writer",
+  system_prompt: "You are a creative writer.",
+  config: shared
+)
+
+# Apply to an entire network (all robots inherit these defaults)
+network = RobotLab.create_network(name: "pipeline", config: shared) do
+  task :analyzer, analyzer_robot, depends_on: :none
+  task :writer, writer_robot, depends_on: [:analyzer]
+end
+
+# Robot-specific kwargs always override the shared config
+robot = RobotLab.build(
+  name: "fast_bot",
+  system_prompt: "Be brief.",
+  config: shared,
+  temperature: 0.3  # overrides shared config's 0.7
+)
+```
+
+RunConfig supports keyword construction, block DSL, and merge semantics:
+
+```ruby
+# Block DSL
+config = RobotLab::RunConfig.new do |c|
+  c.model "claude-sonnet-4"
+  c.temperature 0.7
+end
+
+# Merge (more-specific wins)
+network_config = RobotLab::RunConfig.new(model: "claude-sonnet-4", temperature: 0.5)
+robot_config   = RobotLab::RunConfig.new(temperature: 0.9)
+effective      = network_config.merge(robot_config)
+effective.temperature  #=> 0.9
+effective.model        #=> "claude-sonnet-4"
+```
+
 ### Chaining Configuration
 
 Robots support method chaining to adjust configuration after creation:
@@ -375,7 +426,7 @@ class Comedian < RobotLab::Robot
     super(name: "bob", template: :comedian, bus: bus)
     on_message do |message|
       joke = run(message.content.to_s).last_text_content.strip
-      reply(message, joke)
+      send_reply(to: message.from.to_sym, content: joke, in_reply_to: message.key)
     end
   end
 end
@@ -402,7 +453,7 @@ Key features:
 
 - **Typed channels** — only `RobotMessage` objects are accepted (type enforcement via `typed_bus`)
 - **Auto-ACK** — `on_message { |message| }` auto-acknowledges; use `|delivery, message|` for manual ACK/NACK
-- **Reply correlation** — `reply(message, content)` tracks conversation threads via `in_reply_to`
+- **Reply correlation** — `send_reply(to:, content:, in_reply_to:)` tracks conversation threads
 - **Outbox tracking** — sent messages tracked in `robot.outbox` with status and replies
 - **Independent of Network** — bus communication works without a Network pipeline
 
@@ -451,17 +502,24 @@ Key features:
 
 ## Streaming
 
-Pass a block to `run` to receive real-time events during execution:
+Use a `Streaming::Context` with a publish callback to receive real-time events:
 
 ```ruby
-result = robot.run("Tell me a story") do |event|
+handler = lambda do |event|
   case event[:event]
-  when "text.delta"
+  when RobotLab::Streaming::Events::TEXT_DELTA
     print event[:data][:delta]
-  when "run.completed"
+  when RobotLab::Streaming::Events::RUN_COMPLETED
     puts "\nDone!"
   end
 end
+
+context = RobotLab::Streaming::Context.new(
+  run_id: SecureRandom.uuid,
+  message_id: SecureRandom.uuid,
+  scope: "robot",
+  publish: handler
+)
 ```
 
 ## Rails Integration

data/Rakefile

@@ -48,7 +48,8 @@ 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"
+    "15_memory_network_and_bus" => "editorial_pipeline.rb",
+    "16_writers_room" => "writers_room.rb"
   }.freeze
 
   desc "Run all examples"

data/docs/api/core/index.md

@@ -12,21 +12,21 @@ classDiagram
         +model: String
         +template: String
         +tools: Array~Tool~
-        +run(state, network)
+        +run(message) Message
     }
 
     class Network {
         +name: String
         +robots: Hash
-        +router: Proc
-        +run(state)
+        +config: RunConfig
+        +run(message)
     }
 
-    class State {
-        +data: StateProxy
-        +results: Array
-        +messages: Array
-        +memory: Memory
+    class RunConfig {
+        +model: String
+        +temperature: Float
+        +merge(other) RunConfig
+        +apply_to(chat)
     }
 
     class Tool {
@@ -37,10 +37,13 @@ classDiagram
     }
 
     class Memory {
-        +remember(key, value)
-        +recall(key)
-        +forget(key)
-        +scoped(namespace)
+        +set(key, value)
+        +get(key)
+        +delete(key)
+        +data: StateProxy
+        +results: Array
+        +messages: Array
+        +session_id: String
     }
 
     class RobotMessage {
@@ -53,9 +56,11 @@ classDiagram
     }
 
     Network --> Robot : contains
+    Network --> RunConfig : uses
+    Robot --> RunConfig : uses
     Robot --> Tool : has
-    State --> Memory : has
-    Network --> State : uses
+    Robot --> Memory : uses
+    Network --> Memory : uses
     Robot ..> RobotMessage : sends/receives
 ```
 
@@ -65,10 +70,10 @@ classDiagram
 |-------|---------|
 | [Robot](robot.md) | LLM agent with personality, tools, and model configuration |
 | [Network](network.md) | Container for robots with routing and orchestration |
-| [State](state.md) | Conversation state with data, results, and memory |
+| RunConfig | Shared configuration for LLM, tools, callbacks, and infrastructure |
 | [Tool](tool.md) | Callable function with parameters and handler |
 | [AskUser](tool.md#built-in-askuser) | Built-in tool for terminal-based user interaction |
-| [Memory](memory.md) | Namespaced key-value store for sharing data |
+| [Memory](memory.md) | Reactive key-value store for sharing data |
 | RobotMessage | Typed envelope for bus-based inter-robot communication |
 
 ## Quick Examples
@@ -76,50 +81,40 @@ classDiagram
 ### Robot
 
 ```ruby
-robot = RobotLab.build do
-  name "assistant"
-  model "claude-sonnet-4"
-  template "You are helpful."
-
-  tool :greet do
-    parameter :name, type: :string
-    handler { |name:, **_| "Hello, #{name}!" }
-  end
-end
+robot = RobotLab.build(
+  name: "assistant",
+  model: "claude-sonnet-4",
+  system_prompt: "You are helpful.",
+  local_tools: [greet_tool]
+)
+
+result = robot.run("Hello!")
 ```
 
 ### Network
 
 ```ruby
-network = RobotLab.create_network do
-  name "my_network"
-  add_robot robot
-  router ->(args) { args.call_count.zero? ? :assistant : nil }
+network = RobotLab.create_network(name: "my_network") do
+  step :analyzer, analyzer_robot, depends_on: :none
+  step :writer, writer_robot, depends_on: [:analyzer]
 end
+
+result = network.run(message: "Process this")
 ```
 
-### State
+### Memory
 
 ```ruby
-state = RobotLab.create_state(
-  message: "Hello",
-  data: { user_id: "123" }
-)
+memory = RobotLab.create_memory(data: { user_id: "123" })
+memory.set(:category, "billing")
+memory.get(:category)  # => "billing"
 ```
 
 ### Tool
 
 ```ruby
-tool = RobotLab::Tool.new(
+tool = RobotLab::Tool.create(
   name: "get_time",
-  description: "Get current time",
-  handler: ->(**, _) { Time.now.to_s }
-)
-```
-
-### Memory
-
-```ruby
-state.memory.remember("key", "value")
-value = state.memory.recall("key")
+  description: "Get current time"
+) { |**_| Time.now.to_s }
 ```