chorus-llm 0.2.0 → 0.2.1

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: e9aaa6c14d9fe4b979246f8fbf95ae878c1e05178ebdffd6c90ad1f9d73c1d17
-  data.tar.gz: c4d5473d68812262c3670d972ed42791d758990a204745855d87cc55c94c66c7
+  metadata.gz: 330e292060dd4fe53ef0688cb0a3d757176727287f2f72b43a9c3a8e0b9634f6
+  data.tar.gz: ffff3fda91880555a6e20a8be66fbf72b5e928cd9caccfb2a098feca78771b27
 SHA512:
-  metadata.gz: f3e1b1df26ef99d02da3bcf161088fe5650d4d959061ad229015b2a95b98687fc5864d34b13038905673353b7ac2fd2b14a4724865432f14fc9f7a3f0752c19b
-  data.tar.gz: 62f5a01e91cbc78bc6adcd05e7649ac06a1300067bb37a4d3ff95e16f23044683d314b9fce3a07c96de1982ad1cc5e65c5f58ea834c1be0a1c4711934c0b2c18
+  metadata.gz: 0d0fdf51324967fd47b5bc76e9842a2d477fddcef26224c95c43d5be53119b40e738cbbd0c2a40158bf16f224479bf6a60530f3f5621c8e6d4fd19e11e1aee6d
+  data.tar.gz: '039574260bd44a49778e11e9a1ea077eaa04b05181c9170414ce98042abea78ff02ffc9e289614aee038ecd3b27ef466a0c623710229a003f70d14df429c3eae'

data/README.md

@@ -171,3 +171,15 @@ intentionally does not include:
 - **LLM-generated summaries** — the other-agents summary in `slice_for` is a
   simple concatenation of truncated subjects, not an API call.
 - **Advanced error handling** (retries, backoff, etc.) on API calls.
+
+See [open issues](https://github.com/Amayyas/Chorus/issues) for the full,
+up-to-date backlog — the list above is the original MVP scope, not a
+snapshot of everything planned.
+
+## Contributing
+
+Contributions are welcome. See [CONTRIBUTING.md](CONTRIBUTING.md) for dev
+setup, how to run checks locally, and the commit/PR conventions this project
+follows. Participation is governed by the
+[Code of Conduct](CODE_OF_CONDUCT.md). Found a security issue? See
+[SECURITY.md](SECURITY.md) instead of opening a public issue.

data/lib/chorus/router.rb

@@ -21,13 +21,18 @@ module Chorus
 
     private
 
+    # Whole-word matching, not substring: a naive `include?` check would
+    # match "class" inside "classical" or "error" inside "errors", routing
+    # unrelated messages to :coder. Splitting into words first avoids that
+    # class of false positive.
+    #
+    # This doesn't make keyword matching perfect — a word like "function" is
+    # genuinely ambiguous ("a function" vs. "how it functions") and will
+    # still misroute some messages either way. That's an inherent limitation
+    # of keyword matching, not a bug; see the LLM-based router follow-up.
     def coding_task?(message)
-      normalized = message.downcase
-      # rubocop:disable Style/ArrayIntersect -- `normalized` is a String, not
-      # an Array; Array#intersect? would raise a TypeError here. This is a
-      # substring check on each keyword, not an array-element intersection.
-      CODER_KEYWORDS.any? { |keyword| normalized.include?(keyword) }
-      # rubocop:enable Style/ArrayIntersect
+      words = message.downcase.scan(/\w+/)
+      CODER_KEYWORDS.intersect?(words)
     end
   end
 end

data/lib/chorus/version.rb

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

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: chorus-llm
 version: !ruby/object:Gem::Version
-  version: 0.2.0
+  version: 0.2.1
 platform: ruby
 authors:
 - Amayyas
@@ -53,7 +53,7 @@ required_rubygems_version: !ruby/object:Gem::Requirement
     - !ruby/object:Gem::Version
       version: '0'
 requirements: []
-rubygems_version: 4.0.10
+rubygems_version: 4.0.16
 specification_version: 4
 summary: Ruby framework for multi-agent LLM orchestration with contextual routing.
 test_files: []