chore(i18n): bank the malformed Blob token message

packages/core/src/env.ts goes from 51 to 55: the four fragments of the
message the schema now raises for a BLOB_READ_WRITE_TOKEN that names no
store. It is emitted by assertEnv() before there is a board, a member or a
Translator, like the boot-time strings already banked in this file.

Also records what one of the strings already banked in
blob-file-store.ts actually is: BLOB_NO_CREDENTIALS holds the sentence
@vercel/blob throws, matched on so the driver can replace that error with
one naming the store. It is a sentinel for somebody else's string, not copy,
and rephrasing it would stop the match — worth saying where the count is
explained, since it looks like a message and is not one.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_015WBLHKvRatuUufybYpgER1

Author: claude

docs/internationalisation.md

@@ -289,16 +289,16 @@ configuration that would fail silently says so there or nowhere: refusing
 25 where the egress is blocked and every message would hang until the function
 timed out.
 
-That entry went from 27 to 51 when the Vercel template stopped asking an
+That entry went from 27 to 55 when the Vercel template stopped asking an
 operator for values its linked integrations already publish. `env.ts` now
 derives `CACHE_DRIVER`, `FILESTORE_DRIVER`, `REDIS_URL` and
 `DIRECT_DATABASE_URL` from those, and refuses to boot when it cannot — naming
 every variable it searched, because that name is the only clue an operator has
 when their store publishes something this board has never heard of. Five
-refusals account for the whole raise: the counter charges per quoted fragment,
-so a message wrapped over eight lines is eight strings and not eight messages.
-Each one is read in a deploy log, by the person who started the deploy, in the
-same language as the log around it. See
+refusals and one malformed-credential message account for the whole raise: the
+counter charges per quoted fragment, so a message wrapped over eight lines is
+eight strings and not eight messages. Each one is read in a deploy log, by the
+person who started the deploy, in the same language as the log around it. See
 [Running on Vercel](./vercel.md#when-a-derivation-cannot-resolve) for what each
 refusal means.
 
@@ -309,6 +309,15 @@ tell apart and a first-upload failure to explain when the platform supplies
 neither — all of it thrown as `ConfigurationError` from a driver constructed
 at boot, and read by whoever ran the deploy or the backup.
 
+One of that file's counted strings is not copy in any sense and must not be
+edited as though it were: `BLOB_NO_CREDENTIALS` is the literal sentence
+`@vercel/blob` throws when it can find no credential, and the driver matches
+on it to replace that error with one that names the store and the cause. It
+is a sentinel for somebody else's string, and translating or rephrasing it
+would silently stop the match. A test asserts the same literal is still
+present in the installed SDK, so a reword upstream fails the build rather
+than passing quietly.
+
 The file store's count is not copy at all — `url()` builds an object
 URL per storage shape, and the counter reads the template's fragments as prose.
 Neither surface has ever rendered to a member.

scripts/i18n-baseline.json

@@ -61,7 +61,7 @@
   "packages/avatars/src/index.ts": 4,
   "packages/core/src/cache.ts": 2,
   "packages/core/src/config.ts": 2,
-  "packages/core/src/env.ts": 51,
+  "packages/core/src/env.ts": 55,
   "packages/core/src/errors.ts": 7,
   "packages/core/src/metrics.ts": 1,
   "packages/core/src/permissions.ts": 53,