@jabworks/condux 0.14.0 → 0.14.1

package/package.json

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