feat: Document ArkEnv keywords (#1413)

Fixes #1406

## Summary
- Add `/docs/arkenv/keywords` documenting ArkEnv-only `string.host` and
`number.port` with `TypeTable` catalogs
- Reorder API nav to Keywords → Options → Coercion → arkenv/standard
- Wire `TypeTable` into the www MDX component map and cross-link from
landing, quickstart, standard, coercion, and reuse-schemas

## Test plan
- [ ] Visit `/docs/arkenv/keywords` and confirm API nav order
- [ ] Confirm TypeTable catalogs expand and show equivalents
- [ ] Check cross-links from landing, quickstart, and arkenv/standard
footnote


Made with [Cursor](https://cursor.com)

---------

Co-authored-by: Cursor <cursoragent@cursor.com>
Co-authored-by: autofix-ci[bot] <114827586+autofix-ci[bot]@users.noreply.github.com>

Author: 3 people

apps/www/content/docs/arkenv/coercion.mdx

@@ -17,7 +17,7 @@ Coercion in [arkenv/standard](/docs/arkenv/standard) only works with:
 
 ## Numbers
 
-Any field defined as a `number` or a numeric subtype (like `number.integer` or `number.port`) will be automatically parsed.
+Any field defined as a `number` or a numeric subtype (like `number.integer` or [`number.port`](/docs/arkenv/keywords#number)) will be automatically parsed.
 
 ```ts twoslash
 import arkenv from "arkenv";

apps/www/content/docs/arkenv/how-to/reuse-schemas.mdx

@@ -3,7 +3,7 @@ title: How to reuse your schema
 description: Define your schema once and reuse it across your application.
 ---
 
-ArkEnv supports both raw schema objects and type definitions created with ArkType's `type()` function. Use type definitions when you need to validate the same environment variables in multiple places.
+ArkEnv supports both raw schema objects and type definitions created with ArkType's `type()` function - including ArkEnv [Keywords](/docs/arkenv/keywords) like `string.host` and `number.port`. Use type definitions when you need to validate the same environment variables in multiple places.
 
 Recall that with ArkEnv, defining your schema is done at the same time as you parse the environment variables:
 

apps/www/content/docs/arkenv/index.mdx

@@ -10,8 +10,8 @@ At its core, ArkEnv is a single export that creates a ready-to-use, typesafe env
 import arkenv from "arkenv";
 
 const env = arkenv({
-  HOST: "string.ip | 'localhost'",
-  PORT: "0 <= number.integer <= 65535",
+  HOST: "string.host",
+  PORT: "number.port",
   NODE_ENV: "'development' | 'production' | 'test' = 'development'",
   DEBUGGING: "boolean = false",
 });
@@ -26,7 +26,7 @@ const debugging = env.
 //                    ^|
 ```
 
-> ArkEnv defaults to [ArkType](https://arktype.io/) notation, the closest match to TypeScript syntax for editor-to-runtime typesafety. You can also use any [Standard Schema](https://standardschema.dev/schema) validator, including Zod, Valibot, and Typia.
+> ArkEnv defaults to [ArkType](https://arktype.io/) notation, the closest match to TypeScript syntax for editor-to-runtime typesafety. Keywords like `string.host` and `number.port` are [ArkEnv additions](/docs/arkenv/keywords) - you can also use any [Standard Schema](https://standardschema.dev/schema) validator, including Zod, Valibot, and Typia.
 
 We consider the resulting `env` object "typesafe from editor to runtime": at every step in the app's lifecycle, you are getting a guarantee about your environment variables.
 

apps/www/content/docs/arkenv/keywords.mdx

@@ -0,0 +1,74 @@
+---
+title: Keywords
+description: ArkEnv keywords that extend ArkType for common environment-variable shapes.
+---
+
+<Callout title="Only works with ArkType">
+  This feature is only available with ArkEnv + ArkType and is *not* a part of [arkenv/standard](/docs/arkenv/standard).
+</Callout>
+
+ArkEnv adds a small set of env-oriented keywords on top of [ArkType's keyword set](https://arktype.io/docs/primitives). You can reference them in any ArkEnv schema or `type` definition.
+
+## string
+
+### keywords
+
+The following aliases can be referenced in any definition, e.g.:
+
+<Tabs items={['arkenv', 'type']}>
+  <Tab value="arkenv">
+    ```ts twoslash
+    import arkenv from "arkenv";
+
+    // Hover to see the inferred type
+    const env = arkenv({
+      HOST: "string.host",
+    });
+    ```
+  </Tab>
+
+  <Tab value="type">
+    ```ts twoslash
+    import { type } from "arkenv";
+
+    const Host = type("string.host");
+
+    // Hover to see the inferred type
+    type Host = typeof Host.infer;
+    ```
+  </Tab>
+</Tabs>
+
+<TypeTable expandAll type={{ "string.host": { type: "string.ip | 'localhost'", description: 'An IP address (string.ip) or "localhost".' } }} />
+
+## number
+
+### keywords
+
+The following aliases can be referenced in any definition, e.g.:
+
+<Tabs items={['arkenv', 'type']}>
+  <Tab value="arkenv">
+    ```ts twoslash
+    import arkenv from "arkenv";
+
+    // Hover to see the inferred type
+    const env = arkenv({
+      PORT: "number.port",
+    });
+    ```
+  </Tab>
+
+  <Tab value="type">
+    ```ts twoslash
+    import { type } from "arkenv";
+
+    const Port = type("number.port");
+
+    // Hover to see the inferred type
+    type Port = typeof Port.infer;
+    ```
+  </Tab>
+</Tabs>
+
+<TypeTable expandAll type={{ "number.port": { type: "0 <= number.integer <= 65535", description: "An integer port in the range 0–65535." } }} />

apps/www/content/docs/arkenv/meta.json

@@ -13,9 +13,10 @@
 		"---Integrations---",
 		"...integrations",
 		"---API---",
-		"[arkenv/standard](/docs/arkenv/standard)",
-		"coercion",
+		"keywords",
 		"options",
+		"coercion",
+		"[arkenv/standard](/docs/arkenv/standard)",
 		"---How-to---",
 		"[Load environment variables](/docs/arkenv/how-to/load-environment-variables)",
 		"[Reuse your schema](/docs/arkenv/how-to/reuse-schemas)",

apps/www/content/docs/arkenv/quickstart.mdx

@@ -75,6 +75,8 @@ npx @arkenv/cli@latest init
 
 Your `env.ts` file is where the ✨magic✨ happens – variables referenced from this object are guaranteed to match the schema defined here.
 
+ArkEnv extends ArkType with env-oriented [Keywords](/docs/arkenv/keywords) such as `string.host` and `number.port`:
+
 ```ts title="env.ts" twoslash
 import arkenv, { type } from 'arkenv';
 

apps/www/content/docs/arkenv/standard.mdx

@@ -20,7 +20,7 @@ Already using ArkType? You can still use Zod, Valibot, and other Standard Schema
 | **Standard Schema**       |     ✅    |         ✅         |
 | **Works without ArkType** |     ❌    |         ✅         |
 
-¹ ArkEnv extends ArkType with custom keywords like `string.host` and `number.port`
+¹ ArkEnv extends ArkType with custom keywords like `string.host` and `number.port` - see [Keywords](/docs/arkenv/keywords)
 
 ² Only works with Standard JSON Schema validators like Zod 4, Zod Mini and Valibot - see [Coercion](/docs/arkenv/coercion)
 

apps/www/mdx-components.tsx

@@ -1,3 +1,4 @@
+import { TypeTable } from "@arkenv/fumadocs-ui/components";
 import { arkenvComponents } from "@arkenv/fumadocs-ui/mdx";
 import * as twoslashComponents from "fumadocs-twoslash/ui";
 import {
@@ -25,6 +26,7 @@ export function getMDXComponents(components: MDXComponents): MDXComponents {
 		CalloutTitle,
 		Card,
 		AutoTypeTable,
+		TypeTable,
 		Cards,
 		Files,
 		Folder,