Ship a zero-credential local dev path for uploads
All 8 runs that picked the package ended 'live uploads unverified' because BLOB_READ_WRITE_TOKEN could not be obtained in the sandbox [runs 185, 188, 189, 190, 191, 192, 193]. The runs that skipped the package verified full upload, list and delete flows via curl [runs 184, 187]. Agents treat 'passes build' as done, so the user receives code that fails at first click.
- run 188: the server returns a clear "No read-write token found" error until you add one
- run 189: I couldn't do a real upload here because there's no Blob token
- run 187 grader: tested these via API checks
- run 184: verified via curl on a production server
Add a dev-only filesystem fallback in the SDK: when BLOB_READ_WRITE_TOKEN is unset and NODE_ENV !== 'production', put/list/del/head and handleUpload write to ./.blob-dev/ and return URLs served by a built-in handler. Log one line saying it is in local mode. Throw the existing missing-token error in production only. Until it ships, document the token requirement in the first lines of the README and AGENTS.md, and give agents a verifiable no-token check (route returns 400 with the missing-token message).