Point Dockerfile at production card_backend dataset

Switch the default HF_DATASET_REPO from j-chim/temp_evalcard_backend
(temp Space target) to evaleval/card_backend (production). Local
testing can override via --build-arg HF_DATASET_REPO=... while the
production dataset is being populated with duckdb/v1/*.parquet by
the backend pipeline action.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

Dockerfile

@@ -13,7 +13,7 @@ ARG PNPM_VERSION=10.25.0
 # which dataset to clone and to apply lean cache mode (skip JSON-fallback
 # artifacts). Override at build time via `--build-arg HF_DATASET_REPO=...`.
 ARG DATA_BACKEND=duckdb
-ARG HF_DATASET_REPO=https://huggingface.co/datasets/j-chim/temp_evalcard_backend
+ARG HF_DATASET_REPO=https://huggingface.co/datasets/evaleval/card_backend
 # Static prerender (`next build`) executes route handlers, which call
 # `getModelCards` etc. → `lib/duckdb-data.ts`, which requires
 # `LOCAL_PIPELINE_OUTPUT`. The cache populated by `cache-hf-data.mjs`