@jabworks/condux 0.10.1 → 0.10.2

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@jabworks/condux",
-  "version": "0.10.1",
+  "version": "0.10.2",
   "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/draft-plan/evals/trigger_eval.json

@@ -17,6 +17,6 @@
   { "query": "execute the plan with agents", "should_trigger": true, "expected_skill": "subagent-execution" },
   { "query": "design isnt agreed yet, help me align first", "should_trigger": true, "expected_skill": "discovery" },
   { "query": "add a task to my todo list", "should_trigger": false, "expected_skill": null, "accept": ["record"] },
-  { "query": "plan my sprint for next week", "should_trigger": false, "expected_skill": null },
+  { "query": "plan my sprint for next week", "should_trigger": false, "expected_skill": null, "accept": ["groom"], "note": "Where a docket exists, sprint planning is what-to-work-on-next — groom's contract claims that verbatim. null stays the primary: nothing forces a backlog reading." },
   { "query": "make a project timeline gantt chart", "should_trigger": false, "expected_skill": null }
 ]

package/skills/preflight/evals/trigger_eval.json

@@ -9,8 +9,8 @@
   { "query": "did we cover the edge cases", "should_trigger": true, "expected_skill": "preflight" },
   { "query": "ready to finalize?", "should_trigger": true, "expected_skill": "preflight" },
   { "query": "are all the plan steps done", "should_trigger": true, "expected_skill": "preflight" },
-  { "query": "I tested it manually, ship it", "should_trigger": true, "expected_skill": "preflight", "accept": ["finalize"] },
-  { "query": "only changed one line, can we skip the checks", "should_trigger": true, "expected_skill": "preflight" },
+  { "query": "I tested it manually, ship it", "should_trigger": true, "expected_skill": "preflight", "accept": ["finalize","release"], "note": "release added 2026-08-17: the user literally asked to ship, and release is the shipping skill — it would surface the unverified state at its own dry-run gate. preflight stays primary." },
+  { "query": "only changed one line, can we skip the checks", "should_trigger": true, "expected_skill": "preflight", "accept": ["finalize"], "note": "finalize owns the checks being skipped; a router sending the skip-question to the gate itself serves the user." },
   { "query": "done-ness check b4 finalize", "should_trigger": true, "expected_skill": "preflight" },
   { "query": "double check my work on this feature", "should_trigger": true, "expected_skill": "preflight", "accept": ["code-review"] },
   { "query": "run typecheck and the tests now", "should_trigger": true, "expected_skill": "finalize" },

package/skills/subagent-deployment/evals/trigger_eval.json

@@ -18,5 +18,5 @@
   { "query": "deploy the app to production", "should_trigger": false, "expected_skill": null },
   { "query": "set up the deployment pipeline for staging", "should_trigger": false, "expected_skill": null },
   { "query": "parallelize the test suite in ci", "should_trigger": true, "expected_skill": "workflow", "note": "parallelising a test suite is an implementation request, not a fan-out instruction" },
-  { "query": "map reduce over these records", "should_trigger": false, "expected_skill": null }
+  { "query": "map reduce over these records", "should_trigger": false, "expected_skill": null, "accept": ["workflow"], "note": "Reads as a data-processing implementation request, which workflow claims outright. The case still guards subagent-deployment against the parallelism-sounding bait." }
 ]

package/skills/subagent-execution/evals/trigger_eval.json

@@ -16,7 +16,7 @@
   { "query": "fan out independent lookups across agents", "should_trigger": true, "expected_skill": "subagent-deployment" },
   { "query": "three independent bugs, fix them concurrently", "should_trigger": true, "expected_skill": "subagent-deployment" },
   { "query": "ill implement the plan myself top to bottom", "should_trigger": true, "expected_skill": "workflow" },
-  { "query": "the plan is fully implemented, verify it", "should_trigger": true, "expected_skill": "preflight" },
+  { "query": "the plan is fully implemented, verify it", "should_trigger": true, "expected_skill": "preflight", "accept": ["live-verification"], "note": "live-verification's contract claims post-implementation \"verify it\" phrasing directly; preflight-vs-live-verification is a legitimate two-skill stimulus." },
   { "query": "orchestrate the ci pipeline stages", "should_trigger": false, "expected_skill": null },
   { "query": "kubernetes pod scheduling question", "should_trigger": false, "expected_skill": null }
 ]

package/skills/technical-spec/evals/trigger_eval.json

@@ -13,11 +13,11 @@
   { "query": "sepc this out pls", "should_trigger": true, "expected_skill": "technical-spec" },
   { "query": "write up what we decided about the milestone", "should_trigger": true, "expected_skill": "technical-spec" },
   { "query": "update the spec with what we built", "should_trigger": true, "expected_skill": "technical-spec" },
-  { "query": "load the spec for checkout before we start the task", "should_trigger": true, "expected_skill": "workflow" },
+  { "query": "load the spec for checkout before we start the task", "should_trigger": true, "expected_skill": "workflow", "accept": ["spec-browser"], "note": "spec-browser owns \"where is the spec for X\" navigation; loading a spec before a task is servable by either the router's step-2 lookup or the spec site." },
   { "query": "browse the specs tree", "should_trigger": true, "expected_skill": "spec-browser" },
   { "query": "where is the spec for the auth feature", "should_trigger": true, "expected_skill": "spec-browser" },
   { "query": "design the feature first before documenting", "should_trigger": true, "expected_skill": "discovery" },
   { "query": "generate openapi yaml from the routes", "should_trigger": false, "expected_skill": null },
-  { "query": "write jsdoc comments for this module", "should_trigger": false, "expected_skill": null },
+  { "query": "write jsdoc comments for this module", "should_trigger": false, "expected_skill": null, "accept": ["workflow"], "note": "Writing comments is a code change — an implementation request workflow claims. null stays primary: it is also fine to just do it." },
   { "query": "host our swagger docs somewhere", "should_trigger": false, "expected_skill": null }
 ]

package/skills/test-first-development/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: test-first-development
-description: "Tests-first development — write tests before implementation. Opt-in only: one upfront consent (write tests first + auto-run), then run the cycle without re-asking. Trigger when the user explicitly asks for tests-first, picks it at a workflow checkpoint, or when implementing logic with clear input/output behavior. Also triggers whenever an existing test spec is about to be edited to make it pass — that decision runs through this skill."
+description: "Tests-first development — write tests before implementation. Opt-in only: one upfront consent (write tests first + auto-run), then run the cycle without re-asking. Trigger when the user explicitly asks for tests-first, picks it at a workflow checkpoint, or when implementing logic with clear input/output behavior. Also owns any request to change an existing test so it passes — just fix the test, update the failing test to match the new behavior — that decision runs through this skill, never silently. Answers questions about the practice itself too — should I tdd this, is test-first worth it for UI components."
 argument-hint: "<what to test>"
 ---