Add ci-failure-triage skill

.github/workflows/ci.yml

@@ -160,17 +160,14 @@ jobs:
         run: node scripts/check-rust-kernel-parity.mjs --api-only
 
   authoring-smoke:
-    # Drift guard: scaffold -> install -> build -> harness end to end. Reds the
-    # build the moment the `runx new` authoring path breaks (stale package pins,
-    # toolkit drift, broken templates), so it can never silently rot again.
+    # Drift guard: scaffold -> harness end to end. Reds the build the moment the
+    # `runx new` native scaffold breaks (broken templates, harness regressions),
+    # so the authoring path can never silently rot. Native skills carry no npm
+    # deps and no build step, so this is scaffold then harness, nothing else.
     runs-on: ubuntu-latest
     steps:
       - name: Checkout
         uses: actions/checkout@v6
-      - name: Setup pnpm
-        uses: pnpm/action-setup@v5
-        with:
-          version: 10.18.2
       - name: Setup Node
         uses: actions/setup-node@v6
         with:
@@ -184,7 +181,7 @@ jobs:
       - name: Build runx
         working-directory: crates
         run: cargo build -p runx-cli
-      - name: Scaffold, install, build, harness
+      - name: Scaffold and harness
         env:
           RUNX_RECEIPT_SIGN_KID: ci-authoring-smoke
           RUNX_RECEIPT_SIGN_ED25519_SEED_BASE64: QkJCQkJCQkJCQkJCQkJCQkJCQkJCQkJCQkJCQkJCQkI=
@@ -193,10 +190,7 @@ jobs:
           set -euo pipefail
           RUNX="$GITHUB_WORKSPACE/crates/target/debug/runx"
           "$RUNX" new authoring-smoke --directory "$RUNNER_TEMP/authoring-smoke"
-          cd "$RUNNER_TEMP/authoring-smoke"
-          pnpm install
-          "$RUNX" tool build --all --json
-          "$RUNX" harness . --json
+          "$RUNX" harness "$RUNNER_TEMP/authoring-smoke" --json
 
   checks:
     runs-on: ubuntu-latest

.github/workflows/frantic-github-thread-sync.yml

@@ -4,6 +4,12 @@ env:
   FORCE_JAVASCRIPT_ACTIONS_TO_NODE24: true
 
 on:
+  # The venue fires repository_dispatch (board-sync) on board mutations so the drain
+  # runs promptly. The cron below is the backstop: GitHub throttles high-frequency
+  # schedules (they fire roughly hourly under load), so this event is what makes the
+  # sync low-latency and reliable rather than schedule-only.
+  repository_dispatch:
+    types: [board-sync]
   workflow_dispatch:
     inputs:
       after_event_id:

.github/workflows/release.yml

@@ -307,25 +307,6 @@ jobs:
             fi
             ( cd "$dir" && npm publish --access public --tag latest )
           done
-      - name: Publish workspace JS packages
-        # The cli-v* release also publishes the workspace JS packages the `runx new`
-        # authoring toolkit depends on, so they can never lag the binary again
-        # (the prior drift root cause). pnpm publish resolves the workspace:
-        # protocol to concrete versions; the list is dep-ordered (contracts first).
-        env:
-          NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}
-          NPM_CONFIG_PROVENANCE: "true"
-        run: |
-          set -euo pipefail
-          for dir in packages/contracts packages/authoring; do
-            name=$(node -p "require('./${dir}/package.json').name")
-            version=$(node -p "require('./${dir}/package.json').version")
-            if npm view "${name}@${version}" version >/dev/null 2>&1; then
-              echo "${name}@${version} already published; skipping"
-              continue
-            fi
-            pnpm --filter "${name}" publish --no-git-checks --access public --tag latest
-          done
 
   publish-crates:
     needs: [prepare, github-release]

CONTRIBUTING.md

@@ -120,13 +120,7 @@ Use `runx new <name>` when you already have the runx CLI available locally and w
 runx new docs-demo
 ```
 
-Use `npm create @runxhq/skill@latest <name>` for a cold start from npm:
-
-```bash
-npm create @runxhq/skill@latest docs-demo
-```
-
-Both entry points go through the same scaffolder. Community skills should be authored as standalone packages; the runx repo itself is the first-party lane for official skills, runtime code, tests, and examples.
+Community skills should be authored as standalone packages; the runx repo itself is the first-party lane for official skills, runtime code, tests, and examples.
 
 The first runnable example is documented in [docs/getting-started.md](docs/getting-started.md). The generated package export index is in [docs/api-surface.md](docs/api-surface.md).