chore: publish prerelease -next.5

Signed-off-by: tunnckoCore <5038030+tunnckoCore@users.noreply.github.com>

Author: tunnckoCore

README.md

@@ -170,7 +170,7 @@ They are built around the network, Zagora is built around functions with excelle
 ### Why Zagora over oRPC/tRPC/neverthrow/effect.ts?
 
 - Zagora is focused on producing "just functions", not networks, routers, or groups.
-- oRPC and tRPC does not "support" creating synchornous functions, they always are async
+- oRPC and tRPC does not "support" creating synchornous functions, they are always async
   + in contrast, Zagora does not use `async/await` anywhere in the codebase, but `instanceof Promise` checks
   + the return type of Zagora procedures is dynamically inferred based on many factors
   - return type is NOT a union like `ZagoraResult | Promise<ZagoraResult>` which gives amazing DX

bun.lock

@@ -1,6 +1,6 @@
 {
   "name": "zagora",
-  "version": "1.0.0-next.4",
+  "version": "1.0.0-next.5",
   "license": "Apache-2.0",
   "description": "A minimalist & robust way to create type-safe and error-safe never throwing functions & libraries in TypeScript - with input/output validation and typed errors. Based on StandardSchema-compliant validation libraries. No batteries, no routers, it's just functions that you can export and use. Simple but robust alternative to oRPC and tRPC, no network layer.",
   "repository": {
@@ -70,6 +70,7 @@
     "biome-config-xaxa": "^0.2.1",
     "bun-types": "^1.3.3",
     "is-ci": "^4.1.0",
+    "sherif": "^1.9.0",
     "simple-pre-commit": "^1.2.1",
     "tsdown": "^0.16.6",
     "tsgo-dev": "^2025.11.23",