@plainconceptsplatform/workflows 1.21.5 → 1.21.6

package/loops/actions/merge-train/merge-train.sh

@@ -410,10 +410,18 @@ for line in "${candidates[@]}"; do
     continue
   fi
 
-  meta=$(gh pr view "$pr" --repo "$REPO" --json reviewDecision,commits,closingIssuesReferences 2>/dev/null || echo '{}')
+  meta=$(gh pr view "$pr" --repo "$REPO" --json reviewDecision,commits,closingIssuesReferences,body 2>/dev/null || echo '{}')
   review_decision=$(jq -r '.reviewDecision // ""' <<<"$meta")
   head_committed=$(jq -r '[.commits[]?.committedDate] | max // ""' <<<"$meta")
   linked_issue=$(jq -r '.closingIssuesReferences[0].number // ""' <<<"$meta")
+  # GitHub links closing keywords only on pull requests into the default branch, so a stack
+  # child (into feat/N) has none. The gate reads `Closes #N` from the body instead
+  # (identify-gate-subject); the train must find the same issue, or it misses the attempt the
+  # gate recorded there, counts a failed gate as a silent one and never retries it.
+  if [ -z "$linked_issue" ]; then
+    linked_issue=$(jq -r '.body // ""' <<<"$meta" |
+      grep -oiE '(close[sd]?|fixe?[sd]?|resolve[sd]?) +#[0-9]+' | grep -oE '[0-9]+' | head -n 1 || true)
+  fi
 
   # The latest verdict on the pull request or its issue, and how many retries it has had.
   verdicts=$(

package/loops/actions/verify-route-matrix/verify-route-matrix.sh

@@ -1951,6 +1951,11 @@ fi
 if ! grep -qF 'contains($prefix)' "$ROUTER_YML" || ! grep -qF 'REFINE_PREFIX: "Refinement update"' "$ROUTER_YML"; then
   LEAD_OK=0; echo "FAIL: the refine auto-accept must find the questions by refine's visible prefix, not only the stripped marker" >&2
 fi
+# A stack child (into feat/N) has no closingIssuesReferences; the train must read `Closes #N` from the body like the
+# gate does, or a failed gate's attempt on the issue is invisible and the child is parked as a silent gate forever.
+if [ -f "${HERE}/../merge-train/merge-train.sh" ] && ! grep -qF "(close[sd]?|fixe?[sd]?|resolve[sd]?) +#[0-9]+" "${HERE}/../merge-train/merge-train.sh"; then
+  LEAD_OK=0; echo "FAIL: the merge train must find a stack child's issue from 'Closes #N' in the body" >&2
+fi
 if [ "$LEAD_OK" -eq 1 ]; then PASS=$((PASS + 1)); else FAIL=$((FAIL + 1)); fi
 # The harness plugins only load with .opencode/node_modules installed; without it every CI run
 # spawned untiered workers on the session's model. And the tier model a worker pins has to be one

package/loops/workflows/release-tag.yml

@@ -120,7 +120,10 @@ jobs:
       # The tag above was created with GITHUB_TOKEN, so its push starts no workflow: a release does
       # not ship by itself. A workflow_dispatch is the exception GitHub allows that token, so a
       # release that asked for a deploy starts DEPLOY_WORKFLOW on the tag explicitly. The deploy
-      # workflow's own `pro` environment rules (required reviewers) still apply.
+      # workflow's own `pro` environment rules (required reviewers) still apply. The tagged commit is
+      # the one the release pull request just merged, so its main run is usually still building PRE:
+      # the platform template's deploy waits for that run, skips the CI it passed and promotes its
+      # image, rather than test the same commit again.
       - name: Deploy the release to production
         if: steps.release.outputs.deploy == 'true'
         env:

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@plainconceptsplatform/workflows",
-  "version": "1.21.5",
+  "version": "1.21.6",
   "description": "Install and update Platform GitHub agentic workflows.",
   "keywords": [
     "github-actions",