@jabworks/condux 0.14.0 → 0.14.2

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@jabworks/condux",
-  "version": "0.14.0",
+  "version": "0.14.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/discovery/evals/trigger_eval.json

@@ -7,12 +7,12 @@
   { "query": "design session for the new onboarding", "should_trigger": true, "expected_skill": "discovery" },
   { "query": "brainstorm ideas for the notifications feature", "should_trigger": true, "expected_skill": "discovery" },
   { "query": "whats done look like for this feature? lets align first", "should_trigger": true, "expected_skill": "discovery" },
-  { "query": "resume the design we started yesterday", "should_trigger": true, "expected_skill": "discovery" },
-  { "query": "found an existing design doc for this, continue from it", "should_trigger": true, "expected_skill": "discovery" },
+  { "query": "resume the design we started yesterday", "should_trigger": true, "expected_skill": "discovery", "disallowed": ["session-handoff"] },
+  { "query": "found an existing design doc for this, continue from it", "should_trigger": true, "expected_skill": "discovery", "disallowed": ["session-handoff"] },
   { "query": "design a database schema for multi-tenancy", "should_trigger": true, "expected_skill": "discovery" },
   { "query": "big refactor, unclear boundaries — where do we even start", "should_trigger": true, "expected_skill": "discovery" },
-  { "query": "resume where we left off last session", "should_trigger": true, "expected_skill": "session-handoff" },
-  { "query": "pick up from the handoff doc", "should_trigger": true, "expected_skill": "session-handoff" },
+  { "query": "resume where we left off last session", "should_trigger": true, "expected_skill": "session-handoff", "disallowed": ["discovery"] },
+  { "query": "pick up from the handoff doc", "should_trigger": true, "expected_skill": "session-handoff", "disallowed": ["discovery"] },
   { "query": "we already have a signed off design, write the plan", "should_trigger": true, "expected_skill": "draft-plan" },
   { "query": "skip discovery, just plan it", "should_trigger": true, "expected_skill": "draft-plan" },
   { "query": "small tweak to the button color", "should_trigger": true, "expected_skill": "workflow" },

package/skills/draft-plan/evals/trigger_eval.json

@@ -1,8 +1,8 @@
 [
-  { "query": "write the implementation plan", "should_trigger": true, "expected_skill": "draft-plan", "accept": ["workflow"] },
-  { "query": "turn the design into task cards", "should_trigger": true, "expected_skill": "draft-plan" },
+  { "query": "write the implementation plan", "should_trigger": true, "expected_skill": "draft-plan", "accept": ["workflow"], "disallowed": ["technical-spec"] },
+  { "query": "turn the design into task cards", "should_trigger": true, "expected_skill": "draft-plan", "disallowed": ["technical-spec"] },
   { "query": "plan out the epic we signed off yesterday", "should_trigger": true, "expected_skill": "draft-plan" },
-  { "query": "create the .condux/plans file for this feature", "should_trigger": true, "expected_skill": "draft-plan" },
+  { "query": "create the .condux/plans file for this feature", "should_trigger": true, "expected_skill": "draft-plan", "disallowed": ["technical-spec"] },
   { "query": "break this down into tasks with dependencies", "should_trigger": true, "expected_skill": "draft-plan" },
   { "query": "write-plan for checkout v2", "should_trigger": true, "expected_skill": "draft-plan" },
   { "query": "we havent designed this yet but write a plan anyway", "should_trigger": true, "expected_skill": "draft-plan", "accept": ["discovery"] },

package/skills/plan-review/references/plan-review-template.html

@@ -372,16 +372,21 @@
 /* A keyboard layer nobody can discover is a keyboard layer nobody uses. kit.js
    places this next to every theme group, so the ? overlay has a visible way in
    for anyone who was never told the shortcut exists. */
-/* kit.js wraps the theme group and the help button in this. The theme group
-   keeps growing where its host stretched it (the guide's rail), and stays
-   content-sized where the host did not (the board's action row). */
+/* kit.js wraps the theme group and the help button in this. The pairing is
+   content-sized, so ? sits against the group no matter what the host is: in a
+   flex row the wrapper shrink-wraps anyway, and in block flow (a sidebar) the
+   wrapper fills the width but the group no longer stretches across it. Growing
+   the group is opt-in — a host that wants it to fill the row says so itself,
+   the way the style guide's rail does with `.kit-controls > .themebar`. This
+   was the default until 2026-08-25, and the one surface hosting the group in
+   block flow (plan-review's nav) got a ? at the far edge (docket #52). */
 .kit-controls {
   display: flex;
   align-items: center;
 }
 
 .kit-controls > .kit-theme {
-  flex: 1 1 auto;
+  flex: none;
 }
 
 .kit-helpbtn {
@@ -559,7 +564,11 @@
          text-indent does not produce a hanging indent here — it shifts the flex
          container's first line and clips the label against the row. */
       .nav { border-right: 1px solid var(--border); background: var(--background); overflow-y: auto; padding: 22px 16px 40px; }
-      .nav .kit-theme { margin: 0 0 12px; }
+      /* Space the whole theme+? pairing, not the group inside it. .kit-controls
+         centres its children on the cross axis and flex centres the MARGIN box,
+         so a bottom margin here would ride the group up ~6px while ? stayed put
+         (docket #52). */
+      .nav .kit-controls { margin: 0 0 12px; }
       .nav .tabs { display: flex; margin: 0 0 12px; border: 1px solid var(--border); border-radius: var(--radius); overflow: hidden; }
       .nav .tab { flex: 1; font: 500 var(--text-2xs) var(--sans); letter-spacing: .08em; text-transform: uppercase; padding: 6px 4px;
         background: transparent; border: none; border-right: 1px solid var(--border); color: var(--subtle); cursor: pointer; }

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

@@ -2,14 +2,14 @@
   { "query": "execute the plan with specialist agents", "should_trigger": true, "expected_skill": "subagent-execution" },
   { "query": "run the plan task by task with subagents", "should_trigger": true, "expected_skill": "subagent-execution" },
   { "query": "use the coder agent to implement the plan", "should_trigger": true, "expected_skill": "subagent-execution" },
-  { "query": "resume plan execution from the ledger", "should_trigger": true, "expected_skill": "subagent-execution" },
+  { "query": "resume plan execution from the ledger", "should_trigger": true, "expected_skill": "subagent-execution", "disallowed": ["session-handoff"] },
   { "query": "spawn agents for the LARGE plan", "should_trigger": true, "expected_skill": "subagent-execution" },
   { "query": "whats in spawn-rules for picking an agent", "should_trigger": true, "expected_skill": "subagent-execution" },
   { "query": "prepare a task brief for task 4", "should_trigger": true, "expected_skill": "subagent-execution" },
   { "query": "build the review package for the implementer's commits", "should_trigger": true, "expected_skill": "subagent-execution" },
   { "query": "which model should the coder agent get for this task", "should_trigger": true, "expected_skill": "subagent-execution" },
   { "query": "continue the wave, tasks 5 and 6 are unblocked", "should_trigger": true, "expected_skill": "subagent-execution" },
-  { "query": "we compacted mid-plan, where were we with the agents", "should_trigger": true, "expected_skill": "subagent-execution" },
+  { "query": "we compacted mid-plan, where were we with the agents", "should_trigger": true, "expected_skill": "subagent-execution", "disallowed": ["session-handoff"] },
   { "query": "dont re-dispatch tasks that are already done", "should_trigger": true, "expected_skill": "subagent-execution" },
   { "query": "spawn the agents for this plan", "should_trigger": true, "expected_skill": "subagent-execution" },
   { "query": "dispatch these three unrelated fixes in parallel", "should_trigger": true, "expected_skill": "subagent-deployment" },

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

@@ -1,17 +1,17 @@
 [
   { "query": "save spec", "should_trigger": true, "expected_skill": "technical-spec" },
-  { "query": "document what we decided", "should_trigger": true, "expected_skill": "technical-spec" },
+  { "query": "document what we decided", "should_trigger": true, "expected_skill": "technical-spec", "disallowed": ["draft-plan"] },
   { "query": "spec this out", "should_trigger": true, "expected_skill": "technical-spec" },
   { "query": "persist the api contract and the quirks we found", "should_trigger": true, "expected_skill": "technical-spec" },
   { "query": "write up the field mappings from backend to UI", "should_trigger": true, "expected_skill": "technical-spec" },
   { "query": "update the spec for wan-config", "should_trigger": true, "expected_skill": "technical-spec" },
   { "query": "scaffold a spec folder for this feature", "should_trigger": true, "expected_skill": "technical-spec" },
   { "query": "whats the format for quirks.md", "should_trigger": true, "expected_skill": "technical-spec", "kind": "in-context" },
-  { "query": "record the decision rationale for future sessions", "should_trigger": true, "expected_skill": "technical-spec" },
+  { "query": "record the decision rationale for future sessions", "should_trigger": true, "expected_skill": "technical-spec", "disallowed": ["draft-plan"] },
   { "query": "bump the index.md changelog for the spec", "should_trigger": true, "expected_skill": "technical-spec" },
-  { "query": "save the design as a tech spec with live preview", "should_trigger": true, "expected_skill": "technical-spec" },
+  { "query": "save the design as a tech spec with live preview", "should_trigger": true, "expected_skill": "technical-spec", "disallowed": ["draft-plan"] },
   { "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": "write up what we decided about the milestone", "should_trigger": true, "expected_skill": "technical-spec", "disallowed": ["draft-plan"] },
   { "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", "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" },