@bleedingdev/modern-js-main-doc 3.2.0-ultramodern.99 → 3.4.0-ultramodern.1

package/docs/en/apis/app/commands.mdx

@@ -8,12 +8,12 @@ UltraModern.js has some built-in commands that can help you quickly start a deve
 
 Through this chapter, you can learn about the built-in commands of UltraModern.js and how to use them.
 
-## ultramodern dev
+## modern dev
 
-The `ultramodern dev` command is used to start a local development server and compile the source code in the development environment.
+The `modern dev` command is used to start a local development server and compile the source code in the development environment.
 
 ```bash
-Usage: ultramodern dev [options]
+Usage: modern dev [options]
 
 Options:
   -e --entry <entry>    compiler by entry
@@ -23,10 +23,10 @@ Options:
   --api-only            only start API service
 ```
 
-After running `ultramodern dev`, UltraModern.js will watch source file changes and apply hot module replacement.
+After running `modern dev`, UltraModern.js will watch source file changes and apply hot module replacement.
 
 ```bash
-$ ultramodern dev
+$ modern dev
 
 info    Starting dev server...
 
@@ -38,10 +38,10 @@ info    Starting dev server...
 
 In multi-page (MPA) projects, the `--entry` option can be added to specify one or more pages to compile. In this way, only part of the code in the project will be compiled, and the dev startup speed will be faster.
 
-For example, execute `ultramodern dev --entry`, the entry selector will be displayed in the command line interface:
+For example, execute `modern dev --entry`, the entry selector will be displayed in the command line interface:
 
 ```text
-$ ultramodern dev --entry
+$ modern dev --entry
 
 ? Please select the entry that needs to be built
 ❯ ◯ foo
@@ -57,22 +57,22 @@ You can also specify the page name through parameters after `--entry`, and the n
 
 ```bash
 # Compile foo page
-ultramodern dev --entry foo
+modern dev --entry foo
 
 # Compile foo and bar pages
-ultramodern dev --entry foo,bar
+modern dev --entry foo,bar
 ```
 
-## ultramodern start
+## modern start
 
-`ultramodern start` is an alias of `ultramodern dev` command, the usage of the two are exactly the same.
+`modern start` is an alias of `modern dev` command, the usage of the two are exactly the same.
 
-## ultramodern build
+## modern build
 
-The `ultramodern build` command will build production-ready artifacts in the `dist/` directory by default. You can specify the output directory by modifying the configuration [`output.distPath`](/configure/app/output/dist-path).
+The `modern build` command will build production-ready artifacts in the `dist/` directory by default. You can specify the output directory by modifying the configuration [`output.distPath`](/configure/app/output/dist-path).
 
 ```bash
-Usage: ultramodern build [options]
+Usage: modern build [options]
 
 Options:
   -c --config <config>  specify the configuration file, which can be a relative or absolute path
@@ -80,80 +80,70 @@ Options:
   -w --watch            turn on watch mode, watch for changes and rebuild
 ```
 
-## ultramodern new
+## modern runtime status
 
-The `ultramodern new` command is used to enable features in an existing project.
-
-For example, add application entry, enable some optional features such as BFF, micro frontend, etc.
+The `modern runtime status` command reads the runtime status endpoint and prints the response. It targets `http://127.0.0.1:8080/_modern/runtime/status` by default.
 
 ```bash
-Usage: ultramodern new [options]
+Usage: modern runtime status [options]
 
 Options:
-  --config-file <configFile>  specify the configuration file, which can be a relative or absolute path
-  --lang <lang>          set the language (zh or en) for the new command.
-  -d, --debug            using debug mode to log something (default: false)
-  -c, --config <config>  set default generator config(json string)
-  --dist-tag <tag>       use specified tag version for its generator
-  --registry             set npm registry url to run npm command
-  -h, --help             show command help
+  --endpoint <endpoint>  runtime status endpoint URL or path
+  --token <token>        runtime status auth token
+  --token-env <name>     environment variable name that stores runtime status auth token (default: "MODERN_RUNTIME_SIGNAL_TOKEN")
+  --header-name <name>   auth header name (default: "x-modernjs-runtime-signal-token")
+  --timeout <ms>         request timeout in milliseconds (default: "5000")
+  --json                 output as JSON format for machine reading
+  -h, --help             display help for command
 ```
 
-### Add Entry
+If `--endpoint` is a path, it is resolved against `http://127.0.0.1:8080`. If `--token` is omitted, the command reads the token from the environment variable named by `--token-env`.
 
-In the project, execute the `new` command to add entries as follows:
+By default, the command formats the response as readable key/value lines. Add `--json` to print the raw JSON payload.
 
-```text
-$ npx ultramodern new
-? Please select the operation you want: Create Element
-? Please select the type of element to create: New "entry"
-? Please fill in the entry name: entry
+```bash
+modern runtime status --json
 ```
 
-### Enable Features
+## modern runtime fallback-signal
 
-In the project, execute the `new` command to enable features as follows:
+The `modern runtime fallback-signal` command posts a runtime fallback signal to the canary contract-gate endpoint. It targets `http://127.0.0.1:8080/_modern/contract-gates/runtime-fallback` by default.
 
-```text
-$ npx ultramodern new
-? Please select the operation you want: Enable Features
-? Please select the feature name: (Use arrow keys)
-❯ Enable BFF
-  Enable SSG
-  Enable Micro Frontend
+```bash
+Usage: modern runtime fallback-signal [options]
+
+Options:
+  --app <appName>          remote app name
+  --endpoint <endpoint>    runtime fallback signal endpoint URL or path
+  --reason <reason>        fallback reason (default: "runtime_fallback")
+  --phase <phase>          fallback phase (default: "load")
+  --entry <entry>          remote entry URL
+  --runtime-digest <digest>  runtime digest value
+  --metadata <json>        metadata JSON object string
+  --token <token>          runtime signal auth token
+  --token-env <name>       environment variable name that stores runtime signal auth token (default: "MODERN_RUNTIME_SIGNAL_TOKEN")
+  --header-name <name>     auth header name (default: "x-modernjs-runtime-signal-token")
+  --timeout <ms>           request timeout in milliseconds (default: "5000")
+  --json                   output as JSON format for machine reading
+  -h, --help               display help for command
 ```
 
-:::tip
-The `--config` parameter needs to use a JSON string.
+The request body always includes `appName`, `reason`, and `phase`. It includes `entry`, `runtimeDigest`, and `metadata` only when those options are provided. `--metadata` must be a JSON object string.
 
-pnpm does not support the use of JSON strings as parameter values currently. Use `npm new` to turn on.【[Relate Issue](https://github.com/pnpm/pnpm/issues/3876)】
-:::
+```bash
+modern runtime fallback-signal --app crm-shell --reason remote_load_failed --phase load --json
+```
 
 import ServeCommand from '@site-docs-en/components/serve-command';
 
 <ServeCommand />
 
-## ultramodern upgrade
-
-Execute the command `npx ultramodern upgrade` in the project, by default, dependencies in the `package.json` are updated to the latest version.
-
-```bash
-Usage: ultramodern upgrade [options]
-
-Options:
-  --config <config> specify the configuration file, which can be a relative or absolute path
-  --registry <registry>  specify npm registry (default: "")
-  -d,--debug             using debug mode to log something (default: false)
-  --cwd <cwd>            app directory (default: "")
-  -h, --help             show command help
-```
-
-## ultramodern inspect
+## modern inspect
 
-The `ultramodern inspect` command is used to view the UltraModern.js config, [Rsbuild config](https://v2.rsbuild.rs/config/index) and Rspack config of the project.
+The `modern inspect` command is used to view the UltraModern.js config, [Rsbuild config](https://v2.rsbuild.rs/config/index) and Rspack config of the project.
 
 ```bash
-Usage: ultramodern inspect [options]
+Usage: modern inspect [options]
 
 Options:
   --env <env>           view the configuration in the target environment (default: "development")
@@ -163,14 +153,14 @@ Options:
   -h, --help            show command help
 ```
 
-After executing the command `npx ultramodern inspect` in the project root directory, the following files will be generated in the `dist` directory of the project:
+After executing the command `npx modern inspect` in the project root directory, the following files will be generated in the `dist` directory of the project:
 
 - `modern.js.config.mjs`:The Modern.js configuration currently used.
 - `rsbuild.config.mjs`: The Rsbuild config to use at build time.
 - `rspack.config.web.mjs`: The Rspack config used by to use at build time.
 
 ```bash
-➜ npx ultramodern inspect
+➜ npx modern inspect
 
 Inspect config succeed, open following files to view the content:
 
@@ -184,7 +174,7 @@ Inspect config succeed, open following files to view the content:
 By default, the inspect command will output the development configs, you can use the `--env production` option to output the production configs:
 
 ```bash
-ultramodern inspect --env production
+modern inspect --env production
 ```
 
 ### Verbose content
@@ -192,7 +182,7 @@ ultramodern inspect --env production
 By default, the inspect command will omit the function content in the config object, you can use the `--verbose` option to output the full content of the function:
 
 ```bash
-ultramodern inspect --verbose
+modern inspect --verbose
 ```
 
 ### SSR Configuration
@@ -200,7 +190,7 @@ ultramodern inspect --verbose
 If the project has enabled SSR, an additional `rspack.config.node.mjs` file will be generated in the `dist/`, corresponding to the Rspack configuration at SSR build time.
 
 ```bash
-➜ npx ultramodern inspect
+➜ npx modern inspect
 
 Inspect config succeed, open following files to view the content:
 

package/docs/en/community/blog/v2-release-note.mdx

@@ -86,20 +86,20 @@ title: Modern.js v2 发布
 
 大家对 Modern.js 框架的第一印象可能是「一个大而全的框架」，但事实上，为了避免变得臃肿，**Modern.js 采取了渐进式设计**，将所有功能建立在灵活的插件系统之上，因此具备按需启用和可插拔的能力。
 
-Modern.js 期望能支持不同规模的项目研发，考虑到中大型项目和小型项目对功能的诉求存在差异，**Modern.js 的大多数功能都是按需启用的**。在创建项目时，Modern.js 默认只安装核心模块，使 npm 依赖保持轻量；当需要用到额外功能时，你可以通过 ultramodern new 命令一键开启，并自动安装相关依赖。
+Modern.js 期望能支持不同规模的项目研发，考虑到中大型项目和小型项目对功能的诉求存在差异，**Modern.js 的大多数功能都是按需启用的**。在创建项目时，Modern.js 默认只安装核心模块，使 npm 依赖保持轻量；当需要用到额外功能时，你可以通过 modern new 命令一键开启，并自动安装相关依赖。
 
-![ultramodern new 命令](https://lf3-static.bytednsdoc.com/obj/eden-cn/zq-uylkvT/ljhwZthlaukjlkulzlp/v2-release/modern-new-code.png)
+![modern new 命令](https://lf3-static.bytednsdoc.com/obj/eden-cn/zq-uylkvT/ljhwZthlaukjlkulzlp/v2-release/modern-new-code.png)
 
-<div style={{ textAlign: 'center', fontStyle: 'italic' }}>ultramodern new 命令</div>
+<div style={{ textAlign: 'center', fontStyle: 'italic' }}>modern new 命令</div>
 
 比如：
 
 - 对于基础的开发场景，项目中只需安装 Modern.js 的 CLI 工具 `@modern-js/app-tools`，即具备了开发调试、生产构建的能力。
-- 当你需要在应用中增加一些 BFF 接口时，可以执行 ultramodern new 命令来启用 BFF 功能。启用后，Modern.js 会自动安装所需的 BFF 插件，以及某个 Node.js 框架对应的插件（如 Koa / Express）：
+- 当你需要在应用中增加一些 BFF 接口时，可以执行 modern new 命令来启用 BFF 功能。启用后，Modern.js 会自动安装所需的 BFF 插件，以及某个 Node.js 框架对应的插件（如 Koa / Express）：
 
 ![](https://lf3-static.bytednsdoc.com/obj/eden-cn/zq-uylkvT/ljhwZthlaukjlkulzlp/v2-release/bff-plugins.png)
 
-目前，你可以通过 `ultramodern new` 命令来按需开启以下功能，未来我们也会将更多功能加入到 `new` 命令中，使其能够被便捷地集成。
+目前，你可以通过 `modern new` 命令来按需开启以下功能，未来我们也会将更多功能加入到 `new` 命令中，使其能够被便捷地集成。
 
 ![](https://lf3-static.bytednsdoc.com/obj/eden-cn/zq-uylkvT/ljhwZthlaukjlkulzlp/v2-release/modern-new.png)
 

package/docs/en/community/blog/v3-release-note.mdx

@@ -339,7 +339,7 @@ For more on config-based routing, see the docs: [Config-Based Routing](/guides/b
 
 #### Route Debugging
 
-Run the `npx ultramodern routes` command to generate a complete route structure analysis report in the `dist/routes-inspect.json` file.
+Run the `npx modern routes` command to generate a complete route structure analysis report in the `dist/routes-inspect.json` file.
 
 The report displays each route's path, component file, data loader, error boundary, loading component, and other details, helping developers quickly understand the project's route configuration and troubleshoot routing issues. The structured JSON format is also easy for AI agents to understand and analyze, improving the efficiency of AI-assisted development.
 

package/docs/en/community/releases.mdx

@@ -24,8 +24,4 @@ Modern.js follows the [Semantic Versioning](https://semver.org) specification.
 
 ## Version Upgrade
 
-When you need to upgrade the Modern.js version in your project, you can use the `ultramodern upgrade` command, refer to [Upgrade](/guides/get-started/upgrade).
-
-```bash
-npx ultramodern upgrade
-```
+Modern.js 3.0 no longer ships the `modern upgrade` command. When you need to upgrade a project, follow the manual migration steps in [Upgrade](/guides/get-started/upgrade).

package/docs/en/components/build-output.mdx

@@ -3,7 +3,7 @@ To build the production artifacts of the project, run `pnpm run build` in the pr
 ```bash
 $ pnpm run build
 
-> ultramodern build
+> modern build
 
   Modern.js Framework
 

package/docs/en/components/debug-app.mdx

@@ -2,7 +2,7 @@ Run `pnpm run dev` in the project to start the project:
 
 ```bash
 $ pnpm run dev
-> ultramodern dev
+> modern dev
 
   Modern.js Framework
 

package/docs/en/components/deploy-command.mdx

@@ -1,9 +1,9 @@
-## ultramodern deploy
+## modern deploy
 
-The `ultramodern deploy` command is used to generate artifacts required for the deployment platform.
+The `modern deploy` command is used to generate artifacts required for the deployment platform.
 
 ```bash
-Usage: ultramodern deploy [options]
+Usage: modern deploy [options]
 
 Options:
   -c --config <config>  Specify configuration file path, either relative or absolute

package/docs/en/components/init-app.mdx

@@ -1,4 +1,10 @@
-UltraModern.js provides the BleedingDev create package to create projects. It does not require global installation and can be run on-demand using `pnpm dlx`.
+UltraModern.js provides the BleedingDev create package to create SuperApp
+workspaces. It does not require global installation and can be run on-demand
+using `pnpm dlx`.
+
+The supported pnpm command is the scoped package specifier:
+`pnpm dlx @bleedingdev/modern-js-create <target>`. Do not shorten it to
+`pnpm dlx modern-js-create`; there is no unscoped package by that name.
 
 You can initialize the empty directory you are already in:
 
@@ -10,33 +16,13 @@ pnpm dlx @bleedingdev/modern-js-create .
 You can also create a project directly in a new directory:
 
 ```bash
-pnpm dlx @bleedingdev/modern-js-create myapp
-```
-
-TanStack Router is scaffolded by default. To force React Router compatibility:
-
-```bash
-pnpm dlx @bleedingdev/modern-js-create myapp --router react-router
-```
-
-Tailwind CSS v4 is scaffolded by default. To opt out:
-
-```bash
-pnpm dlx @bleedingdev/modern-js-create myapp --no-tailwind
-```
-
-Effect HttpApi BFF is scaffolded by default.
-
-To initialize BFF scaffold with Hono runtime:
-
-```bash
-pnpm dlx @bleedingdev/modern-js-create myapp --bff-runtime hono
+pnpm dlx @bleedingdev/modern-js-create my-super-app
 ```
 
 To initialize with workspace protocol dependencies (for local monorepo testing of unreleased Modern.js packages):
 
 ```bash
-pnpm dlx @bleedingdev/modern-js-create myapp --workspace
+pnpm dlx @bleedingdev/modern-js-create my-super-app --workspace
 ```
 
 The BleedingDev create package will directly create the application without providing an interactive Q & A interface:
@@ -44,7 +30,7 @@ The BleedingDev create package will directly create the application without prov
 ```bash
 🚀 Welcome to UltraModern.js
 
-📦 Creating project "myapp"...
+📦 Creating project "my-super-app"...
 
 ✨ Project created successfully! 🎉
 
@@ -52,7 +38,7 @@ The BleedingDev create package will directly create the application without prov
 
 📁 Enter the project directory:
 
-  cd myapp
+  cd my-super-app
 
 🔧 Initialize Git repository:
 
@@ -71,37 +57,23 @@ Now, the project structure is as follows:
 
 ```
 .
-├── biome.json
-├── modern.config.ts
+├── apps
+│   └── shell-super-app
 ├── package.json
-├── README.md
-├── src
-│   ├── modern-app-env.d.ts
-│   ├── modern.runtime.ts
-│   └── routes
-│       ├── index.css
-│       ├── layout.tsx
-│       └── page.tsx
-└── tsconfig.json
-```
-
-Tailwind CSS v4 is generated by default; pass `--no-tailwind` to omit `postcss.config.mjs`, `tailwind.config.ts`, and the Tailwind import.
-
-By default, `modern.config.ts` enables `@modern-js/plugin-bff`, generates `api/effect/index.ts` + `shared/effect/api.ts`, and sets `bff.runtimeFramework` to `effect`.
-When `--bff-runtime hono` is enabled, `modern.config.ts` enables `@modern-js/plugin-bff`, generates `api/lambda/hello.ts`, and sets `bff.runtimeFramework` to `hono`.
-When `--workspace` is enabled, `@modern-js/*` dependencies use `workspace:*` versions for local monorepo linkage.
-
-It creates a simple production-ready UltraModern app by default and installs
-the published BleedingDev package aliases:
-
-```bash
-pnpm dlx @bleedingdev/modern-js-create myapp
+├── packages
+│   ├── shared-contracts
+│   ├── shared-design-tokens
+│   └── shared-effect-client
+├── scripts
+├── topology
+└── verticals
 ```
 
-Create a SuperApp workspace only when you need independently owned verticals:
+The default workspace starts shell-only and installs the published BleedingDev
+package aliases:
 
 ```bash
-pnpm dlx @bleedingdev/modern-js-create my-super-app --ultramodern-workspace
+pnpm dlx @bleedingdev/modern-js-create my-super-app
 ```
 
 From a generated SuperApp workspace, add a business MicroVertical in place:

package/docs/en/components/prerequisites.mdx

@@ -9,7 +9,7 @@ import NodeVersion from '@site-docs-en/components/nodeVersion.mdx';
 It is recommended to use [pnpm](https://pnpm.io/installation) to manage dependencies:
 
 ```bash
-mise use pnpm@11.4.0
+mise use pnpm@11.7.0
 ```
 
 :::note

package/docs/en/components/serve-command.mdx

@@ -1,9 +1,9 @@
-## ultramodern serve
+## modern serve
 
-The `ultramodern serve` command is used to start an UltraModern.js project in the production environment. It can also be used to preview the artifacts built for the production environment locally. Please note that you need to execute the [`build`](/apis/app/commands#ultramodern-build) command beforehand to generate the corresponding artifacts.
+The `modern serve` command is used to start an UltraModern.js project in the production environment. It can also be used to preview the artifacts built for the production environment locally. Please note that you need to execute the [`build`](/apis/app/commands#modern-build) command beforehand to generate the corresponding artifacts.
 
 ```bash
-Usage: ultramodern serve [options]
+Usage: modern serve [options]
 
 Options:
   -c --config <config>  specify the configuration file, which can be a relative or absolute path

package/docs/en/configure/app/bff/effect.mdx

@@ -123,13 +123,35 @@ export default defineConfig({
 }
 ```
 
-- **Default:** `{ enabled: true }`
+- **Default:**
+
+```ts
+{
+  enabled: true,
+  requireEnvelope: false,
+  envelopeHeader: 'x-modernjs-data-envelope',
+  validateOrigin: true,
+  requireTraceContext: false,
+  batch: {
+    enabled: true,
+    endpoint: '/_data/batch',
+    maxBatchSize: 16,
+    maxBatchBytes: 64 * 1024,
+    flushIntervalMs: 8,
+    maxConcurrency: 4,
+    requestTimeoutMs: 10000,
+    allowedMethods: ['GET'],
+  },
+}
+```
 
 Configure request-envelope validation for Effect runtime.
 
 Generated Effect client requests batching against `${bff.prefix}${batch.endpoint}` (for example, `/bff-api/_data/batch`).
 
-When `validateOrigin` is enabled, runtime compares envelope origin with request `Origin` header first, then falls back to request URL origin.
+Envelope validation is enabled by default but optional: requests without an envelope pass unless `requireEnvelope` is `true`. If an envelope is present, runtime validates it against the configured namespace, origin, trace, and selection policy. `expectedNamespace` is unset by default, and `selection` has no default limits unless configured.
+
+Origin validation is enabled by default. Runtime compares envelope origin with request `Origin` header first, then falls back to request URL origin; set `validateOrigin: false` to disable that comparison.
 
 ```ts title="modern.config.ts"
 export default defineConfig({
@@ -149,4 +171,6 @@ export default defineConfig({
 });
 ```
 
-`batch.flushIntervalMs` controls client-side micro-batch window in generated Effect client. `maxConcurrency` and `requestTimeoutMs` are applied by the server batch gateway when dispatching items.
+`batch.flushIntervalMs` controls the client-side micro-batch window in the generated Effect client. `maxConcurrency` and `requestTimeoutMs` are applied by the server batch gateway when dispatching items.
+
+The generated `effectBff.client.*` API only exists for loader-materialized `@api/effect/*` imports. Directly importing the server entry (`api/effect/index`) exposes the Effect BFF definition; its `client` property is a placeholder that fails on operation access.

package/docs/en/configure/app/performance/rsdoctor.mdx

@@ -11,22 +11,23 @@ type RsdoctorConfig =
   | boolean
   | {
       enabled?: boolean;
+      disableClientServer?: boolean;
     };
 ```
 
-- **Default:** `true` in production build, `false` in development mode.
+- **Default:** `undefined`, Rsdoctor is disabled unless this option is configured.
 
-Configure Rsdoctor diagnostics in Modern.js build.
+Configure Rsdoctor diagnostics in Modern.js build. Set this option to `true` to enable Rsdoctor:
 
 ```ts title="modern.config.ts"
 export default defineConfig({
   performance: {
-    rsdoctor: false,
+    rsdoctor: true,
   },
 });
 ```
 
-You can also use object form:
+You can also use object form. When an object is provided, Rsdoctor is enabled unless `enabled` is set to `false`:
 
 ```ts title="modern.config.ts"
 export default defineConfig({
@@ -37,3 +38,5 @@ export default defineConfig({
   },
 });
 ```
+
+To disable Rsdoctor after enabling it in shared config, set `rsdoctor` to `false` or set `enabled` to `false`.

package/docs/en/configure/app/tools/ts-checker.mdx

@@ -2,6 +2,8 @@
 title: tsChecker
 ---
 
+import { PackageManagerTabs } from '@theme';
+
 # tools.tsChecker
 
 - **Type:** `Object | Function`
@@ -14,6 +16,8 @@ const defaultOptions = {
     memoryLimit: 8192,
     // use tsconfig of user project
     configFile: tsconfigPath,
+    // use TypeScript Go checker by default
+    tsgo: true,
     // use TS-Go native preview of user project
     typescriptPath: require.resolve('@typescript/native-preview/package.json'),
   },
@@ -35,7 +39,7 @@ const defaultOptions = {
 },
 ```
 
-By default, Modern.js type checking is aligned with the TS-Go native preview used by this fork. You can use `output.disableTsChecker` config to disable build-time checking.
+By default, the [@rsbuild/plugin-type-check](https://github.com/rstackjs/rsbuild-plugin-type-check) is enabled for type checking. You can use `output.disableTsChecker` config to disable it.
 
 ## Example
 
@@ -53,4 +57,28 @@ export default {
 };
 ```
 
-> This fork keeps the TypeScript toolchain on `@typescript/native-preview` / `tsgo`; do not install the classic `typescript` compiler for application type checking.
+## TypeScript Go by Default
+
+Type checking runs on [TypeScript Go](https://github.com/microsoft/typescript-go) (`tsgo`) by default in this fork. The capability is provided by [`ts-checker-rspack-plugin`](https://github.com/rstackjs/ts-checker-rspack-plugin), which is integrated by [`@rsbuild/plugin-type-check`](https://github.com/rstackjs/rsbuild-plugin-type-check), and reduces type-checking time by about 5-10x.
+
+`@typescript/native-preview` ships with the builder, so no extra install is needed. To pin your own version, install it in your project:
+
+<PackageManagerTabs command="install @typescript/native-preview -D" />
+
+When `tsgo` is enabled, the default `typescript.typescriptPath` resolves to `@typescript/native-preview/package.json`. If you manually set `typescript.typescriptPath`, it must be an absolute path to `@typescript/native-preview/package.json`.
+
+To fall back to the classic TypeScript checker, set `typescript.tsgo` to `false` and make sure `typescript` is installed in your project:
+
+```ts
+export default {
+  tools: {
+    tsChecker: {
+      typescript: {
+        tsgo: false,
+      },
+    },
+  },
+};
+```
+
+For supported options and limitations, please refer to [ts-checker-rspack-plugin - TypeScript Go support](https://github.com/rstackjs/ts-checker-rspack-plugin#typescript-go-support).

package/docs/en/configure/app/usage.mdx

@@ -86,8 +86,8 @@ export default defineConfig(({ env, command }) => ({
 This function accepts the following parameters:
 
 - `env`: Corresponds to the value of `process.env.NODE_ENV`.
-  - When running `ultramodern dev`, the value of `env` is `development`.
-  - When running `ultramodern build` or `ultramodern serve`, the value of `env` is `production`.
+  - When running `modern dev`, the value of `env` is `development`.
+  - When running `modern build` or `modern serve`, the value of `env` is `production`.
 - `command`: Corresponds to the current command being run, such as `dev`, `build`, or `serve`.
 
 #### Exporting Asynchronous Functions
@@ -117,8 +117,8 @@ For example, if you need to use the `modern.prod.config.js` file when executing
 ```json title="package.json"
 {
   "scripts": {
-    "dev": "ultramodern dev",
-    "build": "ultramodern build --config modern.prod.config.js"
+    "dev": "modern dev",
+    "build": "modern build --config modern.prod.config.js"
   }
 }
 ```
@@ -126,7 +126,7 @@ For example, if you need to use the `modern.prod.config.js` file when executing
 You can also abbreviate the `--config` option as `-c`:
 
 ```bash
-$ ultramodern build -c modern.prod.config.js
+$ modern build -c modern.prod.config.js
 ```
 
 ### Configuring in package.json (Not Recommended)
@@ -187,7 +187,7 @@ The configuration in the `modern.config.local.ts` file will be deeply merged wit
 
 When using `modern.config.local.ts`, please note the following:
 
-- The `modern.config.local.ts` file will only be loaded when executing the `ultramodern dev` commands and will not be loaded during `ultramodern build`.
+- The `modern.config.local.ts` file will only be loaded when executing the `modern dev` commands and will not be loaded during `modern build`.
 - The priority of the `modern.config.local.ts` file is higher than both `modern.config.ts` and the `modernConfig` field in `package.json`.
 - Since `modern.config.local.ts` is only used for local debugging, it is not recommended to commit it to the code repository. Ensure that the project's `.gitignore` file includes `modern.config.local.ts` and similar files.
 

package/docs/en/guides/advanced-features/bff/data-platform.mdx

@@ -55,12 +55,14 @@ export default defineConfig({
 });
 ```
 
-When `validateOrigin` is enabled, Effect runtime validates envelope origin against the incoming `Origin` header (if present), otherwise falls back to request URL origin.
+Envelope validation is enabled by default but does not require an envelope unless `requireEnvelope` is set. Origin validation is enabled by default; set `validateOrigin: false` to skip comparing the envelope origin against the incoming `Origin` header, or the request URL origin when the header is absent.
 
 ## Generated Effect client behavior
 
 When using the generated Effect client (`@api/effect/index`), Modern.js automatically attaches a serialized data envelope header (`x-modernjs-data-envelope`) for same-origin requests.
 
+The generated client is loader-materialized. Import it from `@api/effect/*` in browser or client-bundled code; direct imports of the server entry (`api/effect/index`) expose the Effect BFF definition and only provide a placeholder `client`.
+
 The envelope includes:
 
 - operation metadata