@jabworks/condux 0.24.0 → 0.24.1

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@jabworks/condux",
-  "version": "0.24.0",
+  "version": "0.24.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/subagent-execution/references/task-brief.sh

@@ -21,11 +21,14 @@ mkdir -p "$SCRATCH_DIR"
 SLUG=$(basename "$PLAN_FILE" .md)
 BRIEF_FILE="$SCRATCH_DIR/${SLUG}-task-${TASK_N}-brief.md"
 
+# A card is a `## Task N:` heading (draft-plan's plan-template.md) or the older
+# `### Task N:`. The card ends at the next card of either shape, or at any
+# other `## ` section — a trailing "## Verification" is not part of the brief.
 awk -v n="$TASK_N" '
   BEGIN { found = 0 }
-  /^### Task [0-9]+:/ {
+  /^##+ Task [0-9]+:/ || /^## / {
     if (found) exit
-    if ($0 ~ ("^### Task " n ":")) { found = 1 }
+    if ($0 ~ ("^##+ Task " n ":")) { found = 1 }
   }
   found { print }
 ' "$PLAN_FILE" > "$BRIEF_FILE"

package/skills/technical-spec/SKILL.md

@@ -23,7 +23,7 @@ to place the spec.
   {feature-slug}/           # cross-cutting, or scaffolded from the repo root
   apps/web/
     {feature-slug}/         # scaffolded while working in apps/web
-      index.md              # purpose, TOC, last updated, commit hash, changelog  ← scaffold creates this
+      index.md              # purpose, TOC, last updated, PR stamp, changelog  ← scaffold creates this
       decisions.md          # Design decisions with context + rationale
       api.md                # Endpoints, types, external APIs consumed
       fields.md             # Field mappings: BE/3rd-party → UI, or forwarding chains
@@ -86,10 +86,16 @@ bash path/to/skill/references/scaffold.sh "WanConfig"
 ```
 
 The script outputs one line:
-- `created:/abs/path/to/specs/wan-config commit:abc1234 date:2026-06-24` — new spec, `index.md` written
-- `exists:/abs/path/to/specs/wan-config commit:abc1234 date:2026-06-24` — spec already exists
+- `created:/abs/path/to/specs/wan-config date:2026-06-24 commit:PR #pending` — new spec, `index.md` written
+- `exists:/abs/path/to/specs/wan-config date:2026-06-24 commit:PR #pending` — spec already exists
 
-Parse `commit`, `date`, and the **absolute spec path** from the output — use the absolute path when writing content files and launching the preview server.
+Parse `date` and the **absolute spec path** from the output — use the absolute path when writing content files and launching the preview server.
+
+The `**Commit:**` stamp names the PR that carries the change (`PR #153`), never
+a commit hash: a hash written on a feature branch is orphaned by the
+squash-merge that lands it, so it resolves only in clones that had the branch.
+The scaffold writes `PR #pending`; replace it with the number once the PR is
+open, and use the same form in changelog lines.
 
 ## After Scaffold: Writing Content Files
 
@@ -131,7 +137,7 @@ path that resolves nowhere.
 When scaffold output is `exists:`:
 1. Read `index.md` to see current state and which files exist
 2. Update only files with new or changed content
-3. Bump `Last updated` and `Commit` in `index.md` using values from scaffold output
+3. Bump `Last updated` in `index.md` from scaffold output; set `Commit` to the PR carrying this change (`PR #pending` until it is open)
 4. Append to the `## Changelog` in `index.md`
 
 ## Live HTML Preview & Review (Optional)
@@ -188,7 +194,8 @@ feedback file, if a decision is submitted).
 | Mistake | Fix |
 |---------|-----|
 | Skipping the notification/confirmation | Always announce before writing, wait for approval |
-| Not using scaffold output for date/commit | Parse them from the script — don't run git separately |
+| Not using scaffold output for the date | Parse it from the script — don't run git separately |
+| Stamping a commit hash | The stamp is `PR #N` — a branch hash is orphaned by squash-merge; `PR #pending` until the PR is open |
 | Rewriting all files on update | Read `index.md` first, only touch files with new content |
 | Vague decisions | Each decision needs context + rationale + consequences |
 | Creating empty placeholder files | Only create a file when it has real content |

package/skills/technical-spec/references/scaffold.sh

@@ -38,7 +38,12 @@ if [[ -z "$SLUG" || ! "$SLUG" =~ ^[a-z0-9]+(-[a-z0-9]+)*$ ]]; then
 fi
 
 DATE=$(date +%Y-%m-%d)
-COMMIT=$(git rev-parse --short HEAD 2>/dev/null || echo "no-git")
+# The stamp names the PR that carries the spec, not a commit. A hash taken
+# here is HEAD on a feature branch, and a squash-merge orphans it the moment
+# the PR lands — it resolves only in clones that had the branch. The PR number
+# is not known until the PR is open, so the scaffold writes a placeholder for
+# the author to replace; a spec still stamped `PR #pending` is unfinished.
+COMMIT="PR #pending"
 REPO_ROOT=$(git rev-parse --show-toplevel 2>/dev/null)
 [[ -z "$REPO_ROOT" ]] && REPO_ROOT="${PWD}"
 
@@ -76,7 +81,7 @@ case "$SPEC_DIR" in
 esac
 
 if [[ -d "$SPEC_DIR" ]]; then
-  echo "exists:$SPEC_DIR commit:$COMMIT date:$DATE"
+  echo "exists:$SPEC_DIR date:$DATE commit:$COMMIT"
   exit 0
 fi
 
@@ -110,4 +115,4 @@ cat > "$SPEC_DIR/index.md" <<EOF
 - $DATE ($COMMIT): Initial spec
 EOF
 
-echo "created:$SPEC_DIR commit:$COMMIT date:$DATE"
+echo "created:$SPEC_DIR date:$DATE commit:$COMMIT"

package/skills/technical-spec/references/templates.md

@@ -20,7 +20,7 @@ follow. Write each table row as a claim someone could check, not a label.
 > shows for the spec — without it the spec is listed with no description.
 
 **Last updated:** {YYYY-MM-DD}
-**Commit:** {short-hash}
+**Commit:** PR #{N}
 **Status:** draft | review | stable
 
 ## Contents
@@ -31,9 +31,14 @@ follow. Write each table row as a claim someone could check, not a label.
 | [Quirks](quirks.md) | what will bite you, and whether it is mitigated |
 
 ## Changelog
-- {YYYY-MM-DD} ({short-hash}): Initial spec
+- {YYYY-MM-DD} (PR #{N}): Initial spec
 ```
 
+The stamp names the PR that carries the change, never a commit hash: a hash
+written on a feature branch is orphaned by the squash-merge that lands it.
+The scaffold writes `PR #pending`; replace it once the PR is open, and use the
+same form in changelog lines.
+
 The Contents table answers *which file do I open* — one row per concern file
 that actually exists, each `Answers` cell saying what a reader comes to it
 for. Files that don't exist get no row.