@jabworks/condux 0.25.0 → 0.25.2

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@jabworks/condux",
-  "version": "0.25.0",
+  "version": "0.25.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/blueprint/references/diagram-check.mjs

@@ -106,11 +106,18 @@ const distPointToSegment = (px, py, x1, y1, x2, y2) => {
   return Math.hypot(px - nx, py - ny);
 };
 
+// Distance from a point to a box: zero inside it, else to its nearest edge.
+const distPointToBox = (px, py, box) =>
+  Math.hypot(Math.max(box.x0 - px, 0, px - box.x1), Math.max(box.y0 - py, 0, py - box.y1));
+
 // Distance from a box to a segment: zero when the segment enters the box,
-// else the nearest of the box's corners. Label attribution measures this, not
-// the box centre — a long start-anchored label beside a vertical edge has its
-// centre far from the line and its near edge right on it, and real diagrams
-// (the 2026-09-08 reporting one, six of seven labels) are drawn that way.
+// else the nearer of two measures — a box corner to the segment, or a segment
+// endpoint to the box. Label attribution measures this, not the box centre —
+// a long start-anchored label beside a vertical edge has its centre far from
+// the line and its near edge right on it, and real diagrams (the 2026-09-08
+// reporting one, six of seven labels) are drawn that way. Corners alone miss
+// the other shape: an arrow whose tip faces the middle of a wide label's side
+// is far from every corner (section-loop.html's step 1: 63.1 against 7.25).
 const distBoxToSegment = (box, x1, y1, x2, y2) => {
   if (liangBarsky(x1, y1, x2, y2, box)) return 0;
 
@@ -121,7 +128,11 @@ const distBoxToSegment = (box, x1, y1, x2, y2) => {
     [box.x1, box.y1],
   ];
 
-  return Math.min(...corners.map(([px, py]) => distPointToSegment(px, py, x1, y1, x2, y2)));
+  return Math.min(
+    ...corners.map(([px, py]) => distPointToSegment(px, py, x1, y1, x2, y2)),
+    distPointToBox(x1, y1, box),
+    distPointToBox(x2, y2, box),
+  );
 };
 
 const fmt = (n) => Math.round(n * 10) / 10;

package/skills/workflow/SKILL.md

@@ -18,8 +18,8 @@ No under-planning for a cross-cutting feature.
 ## Live Context
 
 ```!
-git status --short
-git log --oneline -5
+git status --short 2>/dev/null || echo "(not a git repository yet)"
+git log --oneline -5 2>/dev/null || echo "(no commits yet)"
 ```
 
 ## Operating Rules
@@ -106,6 +106,15 @@ Every tier ends with `preflight` then `finalize` — no exceptions.
 After the user picks, load **only** that skill, run it, then return to the nearest
 checkpoint and re-present the menu until the user chooses Done.
 
+**When the question tool caps the options.** CP-1 and CP-3 have five rows, and
+some hosts' question tools take four (Claude Code's AskUserQuestion does). The
+first four rows go on buttons, recommended first. The fifth row rides in the
+free-text slot the tool adds ("Other"), and the question text names it:
+"Plan ready — how do we proceed? (or type 'revise' to rework the plan)" for
+CP-1, "(or say done)" for CP-3. Never merge two rows into one button to make
+room — "Use agents" for the two agent rows is exactly the erosion this rule
+prevents. A host with no cap, or a plain-text menu, shows every row.
+
 ### CP-1 — Plan ready
 
 *After draft-plan sign-off (LARGE) or the inline plan (MEDIUM). Plan review already
@@ -248,6 +257,7 @@ Stop if you catch yourself doing any of these:
 | Tests / lint / typecheck mid-implementation | Save it all for `finalize` |
 | Spawning agents for a task you can just do | Default is to implement yourself |
 | Omitting the subagent options from a checkpoint menu | The default shapes the recommendation, never the menu — present every CP-1 row |
+| Merging or dropping rows to fit a four-option question tool | Four rows on buttons, the fifth named in the question text and taken through "Other" |
 | Silently skipping discovery on a LARGE task | Ask — it's a soft gate, not a free pass |
 | Rewriting a test spec to make it pass | Stop and ask — never silently edit specs |
 | Auto-running code-review, commits, or agents | They're checkpoint choices; run only when picked |