From 42877c0fa05e9e6eb47d1398268beb57bf9adc59 Mon Sep 17 00:00:00 2001
From: bordumb <bordumbb@gmail.com>
Date: Sat, 18 Jul 2026 15:14:37 +0100
Subject: [PATCH] ci: verify-HEAD routing test accepts either verdict; npm
 publish skips already-published versions

Auths-Id: did:keri:EB5cPHY0t-ejNC_rUzPS1dclTvd6kG-R9mQzjozCuGgd
Auths-Device: did:keri:EB5cPHY0t-ejNC_rUzPS1dclTvd6kG-R9mQzjozCuGgd
Auths-Anchor-Seq: 1
---
 .github/workflows/publish-node.yml            | 16 ++++++++++++++++
 crates/auths-cli/tests/cases/verify_commit.rs | 14 +++++++++++---
 2 files changed, 27 insertions(+), 3 deletions(-)

diff --git a/.github/workflows/publish-node.yml b/.github/workflows/publish-node.yml
index acec057cc..61697fff1 100644
--- a/.github/workflows/publish-node.yml
+++ b/.github/workflows/publish-node.yml
@@ -162,11 +162,27 @@ jobs:
       - name: Upgrade npm for trusted publishing
         run: npm install -g npm@latest
 
+      # A re-pushed tag re-fires this workflow; npm refuses republishing an
+      # existing version, so an already-published version is a SKIP, not a failure.
+      - name: Skip if this version is already on npm
+        id: published
+        working-directory: packages/auths-node
+        run: |
+          VERSION=$(node -p "require('./package.json').version")
+          if npm view "@auths-dev/sdk@$VERSION" version >/dev/null 2>&1; then
+            echo "exists=true" >> "$GITHUB_OUTPUT"
+            echo "@auths-dev/sdk@$VERSION already on npm — skipping republish"
+          else
+            echo "exists=false" >> "$GITHUB_OUTPUT"
+          fi
+
       - name: Publish platform packages
+        if: steps.published.outputs.exists != 'true'
         working-directory: packages/auths-node
         run: npx napi prepublish -t npm --no-gh-release
 
       - name: Publish main package
+        if: steps.published.outputs.exists != 'true'
         working-directory: packages/auths-node
         run: |
           if [ "${{ github.event_name }}" = "workflow_dispatch" ] && [ "${{ github.event.inputs.target }}" = "dry-run" ]; then
diff --git a/crates/auths-cli/tests/cases/verify_commit.rs b/crates/auths-cli/tests/cases/verify_commit.rs
index cffb7d758..3315fa4c7 100644
--- a/crates/auths-cli/tests/cases/verify_commit.rs
+++ b/crates/auths-cli/tests/cases/verify_commit.rs
@@ -44,10 +44,18 @@ fn test_verify_commit_json_output_error() {
 // Tests for the unified `auths verify` command routing to commit verification
 #[test]
 fn test_unified_verify_routes_head_to_commit_verify() {
-    // `auths verify HEAD` routes to commit verification. Without a trusted, trailer-bearing
-    // commit it fails (non-zero exit), but that is a routing success — not a clap parse error.
+    // `auths verify HEAD` routes to commit verification. The VERDICT depends on the
+    // checkout this test runs in: an unsigned or untrusted HEAD fails, while a fully
+    // signed, root-pinned checkout (CI on main, now that every commit is signed)
+    // legitimately succeeds. Routing is what this test pins: either verdict exits
+    // 0 or 1 — never clap's usage-error exit 2.
     let mut cmd = Command::cargo_bin("auths").unwrap();
     cmd.arg("verify").arg("HEAD");
 
-    cmd.assert().failure();
+    let output = cmd.output().unwrap();
+    let code = output.status.code().unwrap_or(-1);
+    assert!(
+        code == 0 || code == 1,
+        "verify HEAD must route to commit verification (exit {code}; 2 = clap parse error)"
+    );
 }