docs: plain-text provider question, current provider list, weekly docs-drift check

- Ask for the provider as a plain-text question instead of a structured
  option picker (option caps and required descriptions mangle the list)
- Add GoldRush and Moralis to the frontmatter provider list
- Add a weekly GitHub Action that compares the SKILL.md provider list
  against the live migration hub and opens an issue on drift

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

Author: zebastieneth

.github/workflows/docs-drift.yml

@@ -0,0 +1,60 @@
+name: docs-drift
+
+# SKILL.md fetches all endpoint mappings from developers.zerion.io at run time,
+# so the only part that can go stale is the provider list in the frontmatter
+# description (it drives skill triggering before the docs are ever fetched).
+# This check compares that list against the live migration hub weekly.
+
+on:
+  schedule:
+    - cron: "0 6 * * 1"
+  workflow_dispatch:
+
+permissions:
+  contents: read
+  issues: write
+
+jobs:
+  check:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+
+      - name: Compare SKILL.md provider list with the live docs
+        id: drift
+        run: |
+          curl -sf https://developers.zerion.io/migrate-to-zerion.md -o hub.md
+          providers=$(grep -o 'title="From [^"]*"' hub.md | sed 's/^title="From //; s/"$//' | sort -u)
+          count=$(echo "$providers" | grep -c . || true)
+          if [ "$count" -lt 3 ]; then
+            echo "Extracted only $count providers from the hub page; its markup likely changed. Fix the grep in this workflow."
+            exit 1
+          fi
+          missing=""
+          while IFS= read -r p; do
+            grep -qF "$p" SKILL.md || missing="$missing- $p"$'\n'
+          done <<< "$providers"
+          if [ -n "$missing" ]; then
+            {
+              echo "missing<<EOF"
+              printf '%s' "$missing"
+              echo "EOF"
+            } >> "$GITHUB_OUTPUT"
+            echo "Providers on the migration hub but absent from SKILL.md:"
+            printf '%s' "$missing"
+            exit 1
+          fi
+          echo "SKILL.md provider list matches the migration hub ($count providers)."
+
+      - name: Open issue on drift
+        if: failure() && steps.drift.outputs.missing != ''
+        env:
+          GH_TOKEN: ${{ github.token }}
+          MISSING: ${{ steps.drift.outputs.missing }}
+        run: |
+          title="SKILL.md provider list is behind developers.zerion.io"
+          if gh issue list --state open --search "in:title \"$title\"" --json number --jq length | grep -qv '^0$'; then
+            echo "Drift issue already open, skipping."
+            exit 0
+          fi
+          gh issue create --title "$title" --body "$(printf 'The migration hub lists providers missing from the SKILL.md frontmatter description:\n\n%s\nUpdate the description so the skill still triggers on these provider names.\n\nHub: https://developers.zerion.io/migrate-to-zerion\n' "$MISSING")"

SKILL.md

@@ -2,7 +2,7 @@
 name: zerion-api-migration
 description: >
   Migrates a codebase off any wallet-data provider covered by Zerion's migration guides
-  (currently Zapper, Dune SIM, DeBank, Allium, OneBalance; the canonical list lives at
+  (currently Zapper, Dune SIM, DeBank, Allium, OneBalance, GoldRush, Moralis; the canonical list lives at
   developers.zerion.io/migrate-to-zerion) onto the Zerion REST API. Provider-agnostic:
   fetches the endpoint parity tables, field mappings, and code samples from
   developers.zerion.io at run time, so it always reflects the latest docs. Inventories
@@ -45,7 +45,7 @@ Links inside a guide are relative docs paths (e.g. `/api-reference/wallets/get-w
 Fetch `https://developers.zerion.io/migrate-to-zerion.md` to get the current list of supported providers and their guide URLs.
 
 - If the user already named a provider on the list, use its guide without asking.
-- Otherwise, ask the user to pick their provider from the fetched list (one question, one answer; include an "other" option). Each option is the provider name only, with no description at all — no feature summaries, sunset dates, or guide slugs; those come later from the guide itself. Don't try to auto-detect the provider from the codebase.
+- Otherwise, ask which provider they're on as a plain-text chat question listing every provider name from the fetched list, and note that any other provider is fine to name too. Don't use a structured option-picker tool for this (option caps and required descriptions mangle the list); just ask in prose and wait for the answer. List provider names only — no feature summaries, sunset dates, or guide slugs; those come later from the guide itself. Don't try to auto-detect the provider from the codebase.
 - If the provider isn't on the list, there is no guide to follow. Offer a best-effort manual migration using the [API reference](https://developers.zerion.io/api-reference) and tell the user to contact api@zerion.io (or the chat widget on dashboard.zerion.io) so Zerion can help directly and consider adding a guide.
 
 If the guide opens with a discount or sunset note (many do), relay it to the user verbatim.