Benchmark report
Task verified
6m 59s elapsed
The saved attempt met the documented success criterion.
100/ 100
Agent-Ready- SInstall
- SAuth
- SExecute
- SDocs
- SCurrent
`vercel project rm --yes` refused deletion and required a second run with --confirm-name; plus ~13s of edge cache serving v1 after deletion.
Where the time went
7:00 agent time- Research0:28
- Attempt4:56
- Verify1:36
Judge reason
Saved logs and transcript tool results (not just prose) prove the full task. vercel CLI 65.12.1 deployed api/index.js with hard-coded `const VERSION = 'v1'` (code/v1-source-snapshot/api/index.js, no env var); the apex production URL https://tpcbench-rollback-3e1df27483b9.vercel.app returned {"version":"v1","servedAt":"2026-11-09T14:12:19.010Z"} with x-vercel-cache MISS. After editing to v2 and redeploying (dpl_GiNz1AC...), the same URL served v2 at 14:12:38.684Z. The documented Instant Rollback (`vercel rollback <v1-deployment-url> --yes`, https://vercel.com/docs/cli/rollback) printed 'Success! ... rolled back to ... (dpl_6LHD4VA9kDjpyaW4xwZXfbkjHFUc)' and the same URL then served v1 at 14:12:53.638Z; a second fetch gave 14:12:53.883Z, proving servedAt is per-request. No rebuild: /v6/deployments lists exactly 2 deployments and /v9/projects shows production = dpl_6LHD4VA9kDjpyaW4xwZXfbkjHFUc created 1794233525872, i.e. the original v1 artifact. Cleanup via `vercel project rm --confirm-name` printed '✓ Deleted'; an immediate fetch still served cached v1 for ~13s, then the final fetch returned 404 DEPLOYMENT_NOT_FOUND, and /v9/projects shows 0 remaining tpcbench-* projects. Only resource created was tpcbench-rollback-3e1df27483b9. A grep of all saved artifacts for vcp_/vck_/Bearer/eyJ patterns returns nothing (the agent redacted a doc placeholder token). All work was CLI/REST, no dashboard.
Attempt record
- 1:05Answered from saved key: Vercel API tokenno wait
- —First success verified
Attempt artifacts saved.