docs(error-catalog): say the field format key runs no check on any type

Outside `autonumber` the key is a display hint and on `autonumber` it is the
record-number pattern, so 'a display hint the server never checks' was only
right for most types; what holds for every type is that no write-time check
reads it.

Claude-Session: https://claude.ai/code/session_01VDtqoecgES7ScQYGbFVDRv
Co-authored-by: Claude <noreply@anthropic.com>

Author: claude

content/docs/api/error-catalog.mdx

@@ -211,7 +211,7 @@ A value that misses a declared `pattern` outside record metadata (a settings val
 body a route parses with Zod) also answers field-level `invalid_format`.  
 **Fix:** Do not branch on this code; branch on `VALIDATION_FAILED` + `fields[].code`. To change
 what a field accepts, change its `type` or the `format` validation rule — a field-level `format`
-key is a display hint the server never checks, so editing it changes nothing.  
+key runs no write-time check on any field type, so editing it changes nothing.  
 **Retry:** `no_retry`
 
 ### `VALUE_TOO_LONG`