@jabworks/condux 0.18.0 → 0.19.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@jabworks/condux",
-  "version": "0.18.0",
+  "version": "0.19.0",
   "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/SKILL.md

@@ -46,17 +46,19 @@ product family.
 │  Standalone: open in the browser (xdg-open / open). If neither   │
 │  works (headless, SSH), print the absolute paths and continue —  │
 │  never fail on delivery.                                         │
-│  Inside /discovery: open NOTHING. Link the file from the design  │
-│  doc and let the running preview reload — see Inside the         │
-│  Workflow.                                                       │
+│  Inside /discovery: open NOTHING. Cite the file's path in the    │
+│  design doc as inline code and let the running preview reload —  │
+│  see Inside the Workflow.                                        │
 │  Either way, always state which mode was produced                │
 │  and offer the flip: "wireframe mode — say 'promote to render'   │
 │  for the full house look" (or the reverse). The mode is never    │
 │  chosen silently.                                                │
 │                                                                  │
-│  Step 4: LINK                                                    │
-│  Reference the files from the design doc or task card that       │
-│  motivated them, so the visual target travels with the design.   │
+│  Step 4: CITE                                                    │
+│  Cite the files' paths (inline code, git-root-relative) in the   │
+│  design doc or task card that motivated them, so the visual      │
+│  target travels with the design. Never a clickable relative      │
+│  link — those 404 in the review preview.                         │
 └──────────────────────────────────────────────────────────────────┘
 ```
 
@@ -113,12 +115,17 @@ mockup into the spec directory first and cite the committed copy.
   | What states are legal and what moves between them? | state machine |
   | What goes where on a screen, and in what order does it read? | wireframe |
 
-  **Inside discovery, deliver by linking — never by opening.** The reader
+  **Inside discovery, deliver by citing — never by opening.** The reader
   already has the design preview open (discovery launches it at §1 and it
-  live-reloads on every write). Add the mockup's path to the design doc and the
-  link appears there. A tab per section is the interruption this avoids;
-  standalone invocations keep opening on deliver. Side-by-side option *picking*
-  stays with discovery's own mockup-picker.
+  live-reloads on every write). Add the mockup's git-root-relative path to the
+  design doc as inline code and the citation appears there; the reader opens
+  the file from the editor or filesystem. Never a clickable relative link —
+  the annotate server serves only the review page and `/api/*`, so relative
+  links 404 in the preview. And never an inlined copy of the diagram beside
+  the artifact: one fact, two homes is how the copies drift. A tab per section
+  is the interruption this avoids; standalone invocations keep opening on
+  deliver. Side-by-side option *picking* stays with discovery's own
+  mockup-picker.
 - **/draft-plan** task cards may cite mockup paths so an implementer sees the
   visual target for their task.
 - Standalone asks ("mock this up", "visualize the data model") run the same

package/skills/discovery/SKILL.md

@@ -59,8 +59,8 @@ Accept either answer, same as any other soft gate in this skill.
 │  §1 is approaches-and-tradeoffs; the rest follow the design.   │
 │  Full contract: The Section Card, below.                        │
 │  Does a section's decision turn on one of blueprint's five     │
-│  questions? Load `blueprint` — the artifact is linked from     │
-│  the design doc, not opened in a new tab.                       │
+│  questions? Load `blueprint` — the artifact path is cited      │
+│  in the design doc as inline code, not opened in a new tab.    │
 │                                                                  │
 │  Step 4: DETAIL ROUND — feed the spec                           │
 │  With the approach chosen, ask ONE more batch, grouped by      │
@@ -180,7 +180,7 @@ before they are inside it. Then create the design file and open the preview
 ## §n of N · <name>                    ← position, always
 <one line: what this section decides>
 
-<the evidence — table, list, or a linked artifact. Never a wall.>
+<the evidence — table, list, or a cited artifact path. Never a wall.>
 
 **Recommendation:** <X>, because <one sentence>.
 <the decision, as named options>
@@ -201,8 +201,12 @@ the design existed only as scrollback, so the thread was lost between them. The
 **Visuals.** Load `blueprint` when a section's decision turns on one of its five
 questions — what entities exist · what happens in what order · what talks to
 what · what states are legal · what goes where on a screen. Inside discovery
-the artifact is *linked from the design doc*, never opened in its own tab: the
-running preview reloads and shows the link, so the reader stays where they are.
+the artifact's git-root-relative path is *cited in the design doc as inline
+code* (e.g. `.condux/designs/assets/checkout-flow.html`), never opened in its
+own tab and never written as a clickable relative link — the annotate server
+serves only the review page and `/api/*`, so a relative link 404s in the
+preview. The preview reloads and shows the citation; the reader opens the
+file from the editor or filesystem.
 
 ## The Design File and the Live Preview (Step 3 onward)
 
@@ -283,11 +287,15 @@ Honour an `AGENTS.md` path override if the project defines one.
 
 For full design mockups — UI wireframes and renders in the house token
 language, data-model / flow / architecture diagrams — load the `blueprint`
-skill; the design doc links the files it produces, and the running preview
-shows the link rather than a new tab opening. At sign-off, offer to
-promote the chosen wireframes to render mode (a style-block swap). For
-*picking between* side-by-side options in the browser, see
-`references/mockup-picker.md` (it can point at blueprint's files).
+skill; the design doc cites the paths of the files it produces as inline
+code, and the running preview shows the citation rather than a new tab
+opening. At sign-off, offer to promote the chosen wireframes to render mode
+(a style-block swap). If the spec references a blueprint artifact, promote
+the file too: copy it into the spec directory and cite the committed path —
+a committed spec may never point into `.condux/`, which is gone on any other
+clone (workflow's citation-direction rule). For *picking between*
+side-by-side options in the browser, see `references/mockup-picker.md` (it
+can point at blueprint's files).
 
 ## Design Review Loop
 

package/skills/discovery/references/design-template.md

@@ -31,7 +31,7 @@ feature: <slug>
 |---|---|
 | <alternative> | <one line> |
 
-<evidence — table, list, or a linked blueprint artifact. Never a wall.>
+<evidence — table, list, or a cited blueprint artifact path. Never a wall.>
 
 ## Constraints & out of scope                [accumulates — rows added any time]