docs(middleware): route auth failures through central error handler

- Reword basic-auth 401 to flow through the central handler
- Reword csrf 403 to flow through the central handler
- Reword ip 403 to flow through the central handler

Author: NeaByteLab

docs/id/middleware/basic-auth.md

@@ -103,7 +103,7 @@ router.use(
 
 ## Penanganan Error
 
-Login yang gagal mengembalikan **401 Unauthorized** dengan header `WWW-Authenticate: Basic realm="Secure Area"`, yang membuat browser menampilkan prompt login. Kredensial diperiksa dalam waktu konstan untuk menghindari kebocoran timing, dan array `users` kosong melempar `Deno.errors.InvalidData` saat middleware dibuat. Untuk membentuk response 401, daftarkan satu handler dengan [`router.catch()`](/id/error-handling/object-details), atau andalkan [perilaku default](/id/error-handling/default-behavior).
+Login yang gagal menghasilkan **401 Unauthorized** dan header `WWW-Authenticate: Basic realm="Secure Area"`, yang membuat browser menampilkan prompt login. Kredensial diperiksa dalam waktu konstan untuk menghindari kebocoran timing, dan array `users` kosong melempar `Deno.errors.InvalidData` saat middleware dibuat. Response 401 dialirkan ke [error handler terpusat](/id/error-handling/object-details), jadi bentuk response di sana atau andalkan [perilaku default](/id/error-handling/default-behavior).
 
 ## Autentikasi Browser
 

docs/id/middleware/csrf.md

@@ -100,6 +100,6 @@ type CsrfRulePredicate = (value: string, ctx: Context) => boolean
 
 ## Penanganan Error
 
-Ketika request diblokir, middleware mengembalikan pesan `Request blocked by CSRF protection` dengan **status code 403**. Untuk membentuk response itu, daftarkan satu handler dengan [`router.catch()`](/id/error-handling/object-details), atau andalkan [perilaku default](/id/error-handling/default-behavior).
+Ketika request diblokir, middleware menghasilkan **403** dan pesan `Request blocked by CSRF protection`. Kegagalan itu dialirkan ke [error handler terpusat](/id/error-handling/object-details), jadi bentuk response di sana atau andalkan [perilaku default](/id/error-handling/default-behavior).
 
 Aturan `origin` atau `secFetchSite` kustom yang melempar gagal pemeriksaannya sendiri dan jatuh aman ke penolakan, dan kesalahannya muncul sebagai event [`csrf:rule-error`](/id/middleware/observability/events#middleware) yang menyebut aturan mana yang rusak alih-alih tetap tersembunyi.

docs/id/middleware/ip.md

@@ -79,4 +79,4 @@ Middleware membaca IP klien yang diresolusi dari `ctx.ip`. Di balik proxy, atur
 
 ## Penanganan Error
 
-Ketika request ditolak, middleware mengembalikan pesan `Access denied by IP restriction` dengan **status code 403**. Untuk membentuk response itu, daftarkan satu handler dengan [`router.catch()`](/id/error-handling/object-details), atau andalkan [perilaku default](/id/error-handling/default-behavior).
+Ketika request ditolak, middleware menghasilkan **403** dan pesan `Access denied by IP restriction`. Kegagalan itu dialirkan ke [error handler terpusat](/id/error-handling/object-details), jadi bentuk response di sana atau andalkan [perilaku default](/id/error-handling/default-behavior).

docs/middleware/basic-auth.md

@@ -103,7 +103,7 @@ router.use(
 
 ## Error Handling
 
-A failed login returns **401 Unauthorized** with a `WWW-Authenticate: Basic realm="Secure Area"` header, which is what makes browsers show the login prompt. Credentials are checked in constant time to avoid timing leaks, and an empty `users` array throws `Deno.errors.InvalidData` when the middleware is created. To shape the 401 response, register a single handler with [`router.catch()`](/error-handling/object-details), or rely on the [default behavior](/error-handling/default-behavior).
+A failed login fails with **401 Unauthorized** and a `WWW-Authenticate: Basic realm="Secure Area"` header, which is what makes browsers show the login prompt. Credentials are checked in constant time to avoid timing leaks, and an empty `users` array throws `Deno.errors.InvalidData` when the middleware is created. The 401 routes through the [central error handler](/error-handling/object-details), so shape the response there or rely on the [default behavior](/error-handling/default-behavior).
 
 ## Browser Authentication
 

docs/middleware/csrf.md

@@ -100,6 +100,6 @@ type CsrfRulePredicate = (value: string, ctx: Context) => boolean
 
 ## Error Handling
 
-When a request is blocked, the middleware returns message `Request blocked by CSRF protection` with **status code 403**. To shape that response, register a single handler with [`router.catch()`](/error-handling/object-details), or rely on the [default behavior](/error-handling/default-behavior).
+When a request is blocked, the middleware fails with **403** and message `Request blocked by CSRF protection`. That failure routes through the [central error handler](/error-handling/object-details), so shape the response there or rely on the [default behavior](/error-handling/default-behavior).
 
 A custom `origin` or `secFetchSite` rule that throws fails its own check and falls safe to a refusal, and the fault surfaces as a [`csrf:rule-error`](/middleware/observability/events#middleware) event naming which rule broke instead of staying hidden.

docs/middleware/ip.md

@@ -85,4 +85,4 @@ The middleware reads the resolved client IP from `ctx.ip`. Behind a proxy, confi
 
 ## Error Handling
 
-When a request is denied, the middleware returns message `Access denied by IP restriction` with **status code 403**. To shape that response, register a single handler with [`router.catch()`](/error-handling/object-details), or rely on the [default behavior](/error-handling/default-behavior).
+When a request is denied, the middleware fails with **403** and message `Access denied by IP restriction`. That failure routes through the [central error handler](/error-handling/object-details), so shape the response there or rely on the [default behavior](/error-handling/default-behavior).