@jabworks/condux 0.13.0 → 0.13.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@jabworks/condux",
3
- "version": "0.13.0",
3
+ "version": "0.13.1",
4
4
  "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.",
5
5
  "type": "module",
6
6
  "publishConfig": {
@@ -341,6 +341,45 @@
341
341
  border-color: var(--primary);
342
342
  }
343
343
 
344
+ /* A keyboard layer nobody can discover is a keyboard layer nobody uses. kit.js
345
+ places this next to every theme group, so the ? overlay has a visible way in
346
+ for anyone who was never told the shortcut exists. */
347
+ /* kit.js wraps the theme group and the help button in this. The theme group
348
+ keeps growing where its host stretched it (the guide's rail), and stays
349
+ content-sized where the host did not (the board's action row). */
350
+ .kit-controls {
351
+ display: flex;
352
+ align-items: center;
353
+ }
354
+
355
+ .kit-controls > .kit-theme {
356
+ flex: 1 1 auto;
357
+ }
358
+
359
+ .kit-helpbtn {
360
+ margin-left: var(--space-2);
361
+ width: 1.65rem;
362
+ height: 1.65rem;
363
+ flex: none;
364
+ font: inherit;
365
+ font-family: var(--mono);
366
+ font-size: var(--text-2xs);
367
+ line-height: 1;
368
+ color: var(--muted-foreground);
369
+ background: var(--card);
370
+ border: 1px solid var(--border);
371
+ border-radius: var(--radius-full);
372
+ cursor: pointer;
373
+ transition:
374
+ color var(--dur-fast) var(--ease-out),
375
+ border-color var(--dur-fast) var(--ease-out);
376
+ }
377
+
378
+ .kit-helpbtn:hover {
379
+ color: var(--foreground);
380
+ border-color: var(--primary);
381
+ }
382
+
344
383
  .kit-copied {
345
384
  color: var(--success);
346
385
  }
@@ -384,6 +423,7 @@
384
423
 
385
424
  .kit-skip,
386
425
  .kit-help,
426
+ .kit-helpbtn,
387
427
  .kit-theme,
388
428
  [data-kit-chrome] {
389
429
  display: none !important;
@@ -1053,6 +1093,37 @@
1053
1093
  });
1054
1094
  }
1055
1095
 
1096
+ /* Give the ? overlay a visible way in. It rides alongside the theme group
1097
+ because every surface already has one, and because a floating badge is
1098
+ chrome each surface would then have to design around. */
1099
+ var groups = document.querySelectorAll('.kit-theme');
1100
+
1101
+ for (var g = 0; g < groups.length; g++) {
1102
+ if (!groups[g].parentNode) continue;
1103
+
1104
+ var help = document.createElement('button');
1105
+
1106
+ help.type = 'button';
1107
+ help.className = 'kit-helpbtn';
1108
+ help.textContent = '?';
1109
+ help.title = 'Keyboard shortcuts (?)';
1110
+ help.setAttribute('aria-label', 'Keyboard shortcuts');
1111
+ help.addEventListener('click', function () {
1112
+ toggleOverlay(true);
1113
+ });
1114
+
1115
+ /* Wrap rather than insert as a sibling: a surface may host the theme group
1116
+ in a flex row (the board) or in block flow (the guide's rail), and in
1117
+ block flow a bare sibling drops onto its own line. The wrapper makes the
1118
+ pairing hold in either. */
1119
+ var controls = document.createElement('div');
1120
+
1121
+ controls.className = 'kit-controls';
1122
+ groups[g].parentNode.insertBefore(controls, groups[g]);
1123
+ controls.appendChild(groups[g]);
1124
+ controls.appendChild(help);
1125
+ }
1126
+
1056
1127
  document.addEventListener('click', function (event) {
1057
1128
  var target = event.target.closest ? event.target.closest('[data-kit-copy]') : null;
1058
1129