@jabworks/condux 0.12.0 → 0.12.1

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@jabworks/condux",
-  "version": "0.12.0",
+  "version": "0.12.1",
   "description": "OpenCode plugin for the condux workflow toolkit — bundles the condux skills and injects the specialist agents (coder, explorer, planner, researcher) plus an opt-in plan-review listener.",
   "type": "module",
   "publishConfig": {

package/skills/blueprint/evals/trigger_eval.json

@@ -81,12 +81,16 @@
   {
     "query": "build the settings page from the approved design",
     "should_trigger": false,
-    "expected_skill": null
+    "expected_skill": null,
+    "accept": ["workflow"],
+    "note": "Building from an approved design is an implementation request; workflow's any-implementation-request claim covers it. The case still guards blueprint against the \"design\" bait."
   },
   {
     "query": "implement this Figma design as a React component",
     "should_trigger": false,
-    "expected_skill": null
+    "expected_skill": null,
+    "accept": ["workflow"],
+    "note": "Implementing a design in code is an implementation request; workflow covers it. The case still guards blueprint against the \"Figma design\" bait."
   },
   {
     "query": "pick a color palette and typography for the marketing site",

package/skills/test-first-development/evals/trigger_eval.json

@@ -1,17 +1,17 @@
 [
-  { "query": "write tests first for this", "should_trigger": true, "expected_skill": "test-first-development" },
-  { "query": "tdd this feature", "should_trigger": true, "expected_skill": "test-first-development" },
-  { "query": "test-first for the parser module", "should_trigger": true, "expected_skill": "test-first-development" },
-  { "query": "write failing tests before implementing", "should_trigger": true, "expected_skill": "test-first-development" },
-  { "query": "red green refactor cycle please", "should_trigger": true, "expected_skill": "test-first-development" },
-  { "query": "can you do this test driven", "should_trigger": true, "expected_skill": "test-first-development" },
-  { "query": "write unit tests for the date helpers before you code them", "should_trigger": true, "expected_skill": "test-first-development" },
-  { "query": "update the failing test to match the new behavior", "should_trigger": true, "expected_skill": "test-first-development" },
-  { "query": "the test is failing so just fix the test", "should_trigger": true, "expected_skill": "test-first-development" },
-  { "query": "should I tdd ui components", "should_trigger": true, "expected_skill": "test-first-development" },
+  { "query": "write tests first for this", "should_trigger": true, "expected_skill": "test-first-development", "accept": ["workflow"], "note": "Implementation request with a test-first modifier. routing.md lists test-first-development among the skills that execute within workflow, never instead of it, so the router is a correct first answer." },
+  { "query": "tdd this feature", "should_trigger": true, "expected_skill": "test-first-development", "accept": ["workflow"] },
+  { "query": "test-first for the parser module", "should_trigger": true, "expected_skill": "test-first-development", "accept": ["workflow"] },
+  { "query": "write failing tests before implementing", "should_trigger": true, "expected_skill": "test-first-development", "accept": ["workflow"] },
+  { "query": "red green refactor cycle please", "should_trigger": true, "expected_skill": "test-first-development", "accept": ["workflow"] },
+  { "query": "can you do this test driven", "should_trigger": true, "expected_skill": "test-first-development", "accept": ["workflow"] },
+  { "query": "write unit tests for the date helpers before you code them", "should_trigger": true, "expected_skill": "test-first-development", "accept": ["workflow"] },
+  { "query": "update the failing test to match the new behavior", "should_trigger": true, "expected_skill": "test-first-development", "note": "Ownership of an existing test, not an implementation request — test-first-development is the sole right answer and this case must stay strict to keep its discriminating power." },
+  { "query": "the test is failing so just fix the test", "should_trigger": true, "expected_skill": "test-first-development", "note": "Ownership of an existing test — strict on purpose, see above." },
+  { "query": "should I tdd ui components", "should_trigger": true, "expected_skill": "test-first-development", "note": "Question about the practice, not a request to build anything — workflow would be wrong here, so no accept alternate." },
   { "query": "you already asked once, dont re-ask each cycle right?", "should_trigger": true, "expected_skill": "test-first-development", "kind": "in-context" },
-  { "query": "bug: prove it with a failing test then fix it", "should_trigger": true, "expected_skill": "test-first-development" },
-  { "query": "tets first plz", "should_trigger": true, "expected_skill": "test-first-development" },
+  { "query": "bug: prove it with a failing test then fix it", "should_trigger": true, "expected_skill": "test-first-development", "accept": ["workflow", "root-cause-analysis"], "note": "Bug-shaped and test-first at once. Doctrine routes a bug through workflow, which loads root-cause-analysis — both are defensible first answers." },
+  { "query": "tets first plz", "should_trigger": true, "expected_skill": "test-first-development", "accept": ["workflow"] },
   { "query": "add tests for the existing legacy code", "should_trigger": true, "expected_skill": "workflow" },
   { "query": "implement the currency formatter utility", "should_trigger": true, "expected_skill": "workflow" },
   { "query": "write e2e tests with playwright for the flow", "should_trigger": true, "expected_skill": "workflow" },