@bleedingdev/modern-js-main-doc 3.2.0-ultramodern.120 → 3.2.0-ultramodern.121

package/docs/en/guides/basic-features/deploy.mdx

@@ -15,12 +15,12 @@ Currently, Modern.js only supports running in a Node.js environment. Support for
 
 ## Build Deployment Products
 
-Running the `ultramodern deploy` command will automatically produce deployment products. This process includes optimizing Bundler build products and their dependencies, detecting the current deployment platform, and automatically generating deployment products that can run on that platform.
+Running the `modern deploy` command will automatically produce deployment products. This process includes optimizing Bundler build products and their dependencies, detecting the current deployment platform, and automatically generating deployment products that can run on that platform.
 
-If you want to generate and test the output locally for a specific deployment platform, you can specify the platform by setting the environment variable: `ultramodern deploy`:
+If you want to generate and test the output locally for a specific deployment platform, you can specify the platform by setting the environment variable: `modern deploy`:
 
 ```bash
-MODERNJS_DEPLOY=netlify npx ultramodern deploy
+MODERNJS_DEPLOY=netlify npx modern deploy
 ```
 
 :::info
@@ -36,10 +36,10 @@ By default, Modern.js outputs builds that can be run in a Node.js environment wh
 Use the following command to build the project:
 
 ```bash
-npx ultramodern deploy
+npx modern deploy
 ```
 
-When running the `ultramodern deploy` command, UltraModern.js will generate runnable products and output the following content in terminal:
+When running the `modern deploy` command, UltraModern.js will generate runnable products and output the following content in terminal:
 
 ```bash
 Static directory: `.output/static`
@@ -67,7 +67,7 @@ Assume that the name in the `package.json` of the current project is `app`. Taki
 {
   "scripts": {
     "build:packages": "pnpm --filter 'app^...' run build",
-    "deploy": "pnpm run build:packages && ultramodern deploy"
+    "deploy": "pnpm run build:packages && modern deploy"
   }
 }
 ```
@@ -78,7 +78,7 @@ If you use Rush as your Monorepo management tool, you can add the following comm
 {
   "scripts": {
     "build:packages": "rush rebuild --to-except app",
-    "deploy": "rushx build:packages && ultramodern deploy"
+    "deploy": "rushx build:packages && modern deploy"
   }
 }
 ```
@@ -108,7 +108,7 @@ Add the following content to `netlify.toml`:
 ```toml
 [build]
   publish = "dist"
-  command = "ultramodern deploy"
+  command = "modern deploy"
 ```
 
 :::info
@@ -125,7 +125,7 @@ Full-stack projects refer to projects that use Custom Web Server, SSR or BFF. Th
 ```toml title="netlify.toml"
 [build]
   publish = "dist"
-  command = "ultramodern deploy"
+  command = "modern deploy"
 
 [functions]
   directory = ".netlify/functions"
@@ -173,7 +173,7 @@ Add the following script in `packages/app/package.json`, before executing the de
 {
   "scripts": {
     "build:packages": "pnpm --filter 'app^...' run build",
-    "deploy": "pnpm run build:packages && ultramodern deploy"
+    "deploy": "pnpm run build:packages && modern deploy"
   }
 }
 ```
@@ -213,7 +213,7 @@ Add the following content to `vercel.json`:
 
 ```json title="vercel.json"
 {
-  "buildCommand": "ultramodern deploy",
+  "buildCommand": "modern deploy",
   "outputDirectory": ".vercel/output"
 }
 ```
@@ -281,7 +281,7 @@ Add the following script to `packages/app/package.json` to run `build` command o
 {
   "scripts": {
     "build:packages": "pnpm --filter 'app^...' run build",
-    "deploy": "pnpm run build:packages && ultramodern deploy"
+    "deploy": "pnpm run build:packages && modern deploy"
   }
 }
 ```
@@ -326,7 +326,7 @@ For branch deployment, follow these steps:
 ```
 "scripts": {
   //...
-  "deploy:gh-pages": "MODERNJS_DEPLOY=ghPages ultramodern deploy && gh-pages -d .output"
+  "deploy:gh-pages": "MODERNJS_DEPLOY=ghPages modern deploy && gh-pages -d .output"
 }
 ```
 
@@ -334,7 +334,7 @@ For branch deployment, follow these steps:
 
 :::info
 
-1. Running `MODERNJS_DEPLOY=ghPages ultramodern deploy` will build the production output for GitHub in the .output directory.
+1. Running `MODERNJS_DEPLOY=ghPages modern deploy` will build the production output for GitHub in the .output directory.
 2. You can refer to the [project](https://github.com/web-infra-dev/modern-js-examples/tree/main/examples/modern-js-deploy-csr)
    :::
 

package/docs/en/guides/basic-features/env-vars.mdx

@@ -16,8 +16,8 @@ The current path prefix of the asset, which is a read-only environment variable.
 
 The current execution environment and is a **read-only** environment variable whose have different values under different execution commands:
 
-- `production`: Default value when running `ultramodern build` or `ultramodern serve`.
-- `development`: Default value when running `ultramodern dev`, also the default value in other cases.
+- `production`: Default value when running `modern build` or `modern serve`.
+- `development`: Default value when running `modern dev`, also the default value in other cases.
 
 ### MODERN_ENV
 

package/docs/en/guides/basic-features/render/_meta.json

@@ -1,10 +1 @@
-[
-  "overview",
-  "ssr",
-  "streaming-ssr",
-  "ssr-cache",
-  "ssg",
-  "rsc",
-  "tanstack-rsc",
-  "before-render"
-]
+["overview", "ssr", "streaming-ssr", "ssr-cache", "ssg", "rsc", "before-render"]

package/docs/en/guides/basic-features/render/overview.mdx

@@ -47,6 +47,5 @@ Modern.js supports combining multiple rendering modes:
 - [Server-Side Rendering (SSR)](/guides/basic-features/render/ssr)
 - [Streaming Server-Side Rendering (Streaming SSR)](/guides/basic-features/render/streaming-ssr)
 - [React Server Components (RSC)](/guides/basic-features/render/rsc)
-- [TanStack Router RSC](/guides/basic-features/render/tanstack-rsc)
 - [Static Site Generation (SSG)](/guides/basic-features/render/ssg)
 - [Rendering Cache](/guides/basic-features/render/ssr-cache)

package/docs/en/guides/basic-features/render/rsc.mdx

@@ -531,4 +531,3 @@ The project's bundle has introduced a non-19 React version, commonly seen in mon
 - [Data Cache](/guides/basic-features/data/data-cache)
 - [Server-Side Rendering (SSR)](/guides/basic-features/render/ssr)
 - [Streaming SSR](/guides/basic-features/render/streaming-ssr)
-- [TanStack Router RSC](/guides/basic-features/render/tanstack-rsc)

package/docs/en/guides/basic-features/routes/config-routes.mdx

@@ -271,7 +271,7 @@ Config routes can be used together with convention routes. You can merge routes
 
 :::info
 
-Current route structure can be viewed through the [`ultramodern routes`](#debugging-routes) command
+Current route structure can be viewed through the [`modern routes`](#debugging-routes) command
 
 :::
 
@@ -319,7 +319,7 @@ Since the final structure after route merging may not be intuitive, Modern.js pr
 
 ```bash
 # Generate route structure analysis report
-npx ultramodern routes
+npx modern routes
 ```
 
 This command will generate the final route structure in the `dist/routes-inspect.json` file, helping you understand the complete route information after merging.

package/docs/en/guides/basic-features/routes/routes.mdx

@@ -474,27 +474,27 @@ For applications with higher performance requirements, prefetching can further e
 
 :::tip
 
-Route data warmup is opt-in. In SSR projects, data returned by the [Data Loader](/guides/basic-features/data/data-fetch) is only prefetched when the matched route explicitly enables it with `handle.navigationWarmup.data`.
+In SSR projects, same-origin route data returned by the [Data Loader](/guides/basic-features/data/data-fetch) is prefetched for matched routes with callable loaders. Set `handle.navigationWarmup.data` to `false` on a route when its loader data should not be requested before navigation.
 
 :::
 
-By default, same-origin links prefetch the route module when the `<Link>` renders and preload when the link enters the viewport. Modern.js skips these automatic warmups on Save-Data or slow network connections.
+By default, same-origin links prefetch the route module and matching loader data when the `<Link>` renders. Modern.js skips these automatic warmups on Save-Data or slow network connections.
 
 The `prefetch` attribute has four optional values:
 
 - `render`: The default value. When the `<Link>` component is rendered, it begins warming the corresponding route module.
 - `intent`: When users focus, hover, or touch the link, it starts warming the corresponding route module. If the intent is canceled before warmup starts, the warmup is canceled.
 - `viewport`: When the `<Link>` component enters the viewport, it begins warming the corresponding route module.
-- `none`: Disables automatic render prefetching. It also disables the default viewport preload unless an explicit `preload` value is provided.
+- `none`: Disables automatic prefetching. It also disables implicit preload unless an explicit `preload` value is provided.
 
-The `preload` attribute accepts the same timing values and defaults to `viewport`. Explicit `preload` values always win, and `preload={false}` disables preload behavior.
+The `preload` attribute accepts the same timing values and defaults to the `prefetch` timing. Explicit `preload` values always win, and `preload={false}` disables preload behavior.
 
-To opt a route into SSR data warmup:
+To opt a route out of SSR data warmup:
 
 ```ts title="routes/page.config.ts"
 export const handle = {
   navigationWarmup: {
-    data: true,
+    data: false,
   },
 };
 ```
@@ -503,7 +503,7 @@ export const handle = {
 
 - `render` allows you to control route-module warmup with the position of the `<Link>` component in the tree.
 - `viewport` lets you defer module warmup until the link is close to becoming actionable.
-- SSR data prefetching is not enabled by default; use `handle.navigationWarmup.data` only for routes whose loader data is safe and useful to fetch before navigation.
+- SSR data prefetching is enabled by default; use `handle.navigationWarmup.data = false` for routes whose loader data is not safe or useful to fetch before navigation.
 
 :::
 

package/docs/en/guides/concept/server.mdx

@@ -26,10 +26,10 @@ Static asset files can be directly hosted by Modern.js' server, but it is highly
 
 Modern.js supports running built artifacts in any Node.js environment. Typically, the CI environment has already installed all application dependencies.
 
-You can run the [`ultramodern build`](/apis/app/commands#ultramodern-build) command to build the application and the [`ultramodern serve`](/apis/app/commands#ultramodern-serve) command to run the Web server, starting the UltraModern.js application.
+You can run the [`modern build`](/apis/app/commands#modern-build) command to build the application and the [`modern serve`](/apis/app/commands#modern-serve) command to run the Web server, starting the UltraModern.js application.
 
 ## Running in Production Environments
 
 When deploying to production, the artifact size should be as small as possible. The aforementioned method for running in CI environments keeps all artifacts from the original project. Therefore, it is not recommended to run the application using the above commands in a production environment.
 
-UltraModern.js offers a standalone deployment solution. When running the [`ultramodern deploy`](/apis/app/commands#ultramodern-deploy) command, the artifacts will include an entry file for running the Web server.
+UltraModern.js offers a standalone deployment solution. When running the [`modern deploy`](/apis/app/commands#modern-deploy) command, the artifacts will include an entry file for running the Web server.

package/docs/en/guides/get-started/quick-start.mdx

@@ -48,7 +48,7 @@ After running `pnpm run dev` again, you can find that the project has completed
 
 In a newly created project, the `@modern-js/app-tools` npm package is installed by default. It is the core package of the Modern.js framework and provides the following capabilities:
 
-- It offers commonly used CLI commands such as `ultramodern dev`, `ultramodern build`, and more.
+- It offers commonly used CLI commands such as `modern dev`, `modern build`, and more.
 - It integrates Rsbuild, providing build capabilities.
 - It integrates Modern.js Server, providing capabilities for development and production servers.
 

package/docs/en/guides/get-started/ultramodern.mdx

@@ -30,7 +30,7 @@ UltraModern.js additions are designed as the default product surface for new Sup
 
 | Area | Modern.js 3.0 baseline | UltraModern.js 3.0 |
 | --- | --- | --- |
-| Build diagnostics | RsDoctor is generally opt-in | Adds `performance.rsdoctor`, default-on diagnostics in production Rspack builds, and `.rsdoctor/ultramodern-diagnostics.json` contract artifact |
+| Build diagnostics | RsDoctor is generally opt-in | Adds a first-class `performance.rsdoctor` config surface (opt-in; the earlier default-on behavior and diagnostics contract artifact were reverted) |
 | Output and static serving | Precompression behavior is app-defined | Enables `output.precompress` by default and serves `.br` / `.gz` variants via `Accept-Encoding` negotiation |
 | BFF runtime and contracts | Standard BFF runtime/client generation | Adds `requestId`-aware producer isolation, fail-fast initialization checks, and operation/trace correlation headers |
 | BFF runtime choices | Hono runtime path only in Modern.js 3.0 baseline (no built-in Effect runtime path) | Sets Effect as default runtime, enforces strict runtime split (`effect` -> `api/effect`, `hono` -> `api/lambda`), and adds Effect-Schema-first contracts plus MF failure-injection reliability coverage |
@@ -103,9 +103,15 @@ every app.
 
 Each app emits `src/routes/ultramodern-route-metadata` with
 `ultramodernLocalisedUrls`. The i18n plugin reads that map in
-`localeDetection.localisedUrls` and serves dynamic backend JSON from
-`/locales/{{lng}}/{{ns}}.json`. The route owner changes localized paths and
-locale resource JSON together.
+`localeDetection.localisedUrls`; this is the explicit non-empty map that enables
+translated path segments on top of `localePathRedirect`. The i18n plugin also
+serves dynamic backend JSON from `/locales/{{lng}}/{{ns}}.json`. The route owner
+changes localized paths and locale resource JSON together.
+
+JSON-LD is optional route metadata, not inferred output. Private and
+non-indexable routes emit no JSON-LD by default. Public route owners can add
+`jsonLd` beside localized paths and use the generated
+`src/routes/ultramodern-jsonld.ts` helpers for common schema.org shapes.
 
 The generated contract writes `.modernjs/ultramodern-generated-contract.json`
 with a `cssFederation` section:

package/docs/en/guides/topic-detail/module-federation/application.mdx

@@ -103,7 +103,7 @@ export default RemoteApp;
 
 ## Start the Application
 
-Now, both the producer and consumer applications are set up. We can run `ultramodern dev` locally to start both applications.
+Now, both the producer and consumer applications are set up. We can run `modern dev` locally to start both applications.
 
 After startup, when the consumer application accesses the `/remote` route, it will enter the producer application. Accessing `http://localhost:8080/remote` will display a complete page of the producer's remote module in the browser.
 

package/docs/en/guides/topic-detail/module-federation/deploy.mdx

@@ -88,10 +88,10 @@ export default createModuleFederationConfig({
 
 ## Local Deployment Verification
 
-Modern.js provides the `ultramodern deploy` command, which can easily generate products that can run in a Node.js environment.
+Modern.js provides the `modern deploy` command, which can easily generate products that can run in a Node.js environment.
 
 ```bash
-ultramodern deploy
+modern deploy
 ```
 
 After executing the command, you can see the following output in the console:

package/docs/en/guides/topic-detail/module-federation/usage.mdx

@@ -154,7 +154,7 @@ The second part, `remoteExpose`, is the `key` configured in the `exposes` field
 
 ## Start the Applications
 
-Now, both the producer and consumer applications are set up. You can run `ultramodern dev` locally to start both applications.
+Now, both the producer and consumer applications are set up. You can run `modern dev` locally to start both applications.
 
 Once started, the imports of the producer's modules in the consumer will no longer throw errors, and the types will be downloaded to the consumer application.
 
@@ -164,7 +164,7 @@ After modifying the producer's code, the consumer will automatically fetch the p
 
 Access `http://localhost:8080/remote`, and you will see that the page includes the `Button` component from the producer's remote module.
 
-We can also execute `ultramodern serve` locally to simulate the production environment.
+We can also execute `modern serve` locally to simulate the production environment.
 
 Because the Module Federation plugin will automatically read Modern.js's `output.assetPrefix` configuration as the access address for remote modules, and this value defaults to `/` after building in the production environment.
 
@@ -180,7 +180,7 @@ export default defineConfig({
     port: 3051,
   },
   output: {
-    // Now this configuration is only used in the local when you run ultramodern serve command.
+    // Now this configuration is only used in the local when you run modern serve command.
     // If you want to deploy the application to the platform, use your own domain name.
     // Module federation will automatically write it to mf-manifest.json, which influences consumer to fetch remoteEntry.js.
     assetPrefix: 'http://127.0.0.1:3051',
@@ -189,10 +189,10 @@ export default defineConfig({
 });
 ```
 
-Now, in the producer, run `ultramodern build && MODERN_MF_AUTO_CORS=true  ultramodern serve`, and in the consumer, run `ultramodern build && ultramodern serve` to simulate the production environment locally and access the remote modules.
+Now, in the producer, run `modern build && MODERN_MF_AUTO_CORS=true  modern serve`, and in the consumer, run `modern build && modern serve` to simulate the production environment locally and access the remote modules.
 
 :::tip
-When using the `ultramodern serve` command, you need to set the `MODERN_MF_AUTO_CORS=true` environment variable when starting the producer project to automatically handle CORS issues and ensure that consumers can properly access the producer's remote module resources.
+When using the `modern serve` command, you need to set the `MODERN_MF_AUTO_CORS=true` environment variable when starting the producer project to automatically handle CORS issues and ensure that consumers can properly access the producer's remote module resources.
 :::
 
 You can refer to this example: [Modern.js & Module Federation Basic Example](https://github.com/web-infra-dev/modern-js-examples/tree/main/examples/module-federation/base).

package/docs/en/guides/troubleshooting/builder.mdx

@@ -23,7 +23,7 @@ Modern.js is internally based on [Rsbuild](https://v2.rsbuild.rs/) and encapsula
 Modern.js provides [inspect command](https://modernjs.dev/en/apis/app/commands.html) to view the final Modern.js configuration and Rspack configuration generated by the project.
 
 ```bash
-➜ npx ultramodern inspect
+➜ npx modern inspect
 
 Inspect config succeed, open following files to view the content:
 

package/docs/en/guides/upgrade/config.mdx

@@ -334,7 +334,7 @@ export default {
 
 ### tools.rsdoctor
 
-**Change**: This configuration has been deprecated. In v3, Modern.js enables Rsdoctor by default in production build. Use [`performance.rsdoctor`](/configure/app/performance/rsdoctor) to configure or disable it.
+**Change**: This configuration has been deprecated. In v3, use [`performance.rsdoctor`](/configure/app/performance/rsdoctor) to opt in to Rsdoctor diagnostics.
 
 **Migration Example**:
 
@@ -350,7 +350,6 @@ tools: {
 // v3
 export default {
   performance: {
-    // enabled by default in production build
     rsdoctor: {
       enabled: true,
     },

package/docs/en/guides/upgrade/other.mdx

@@ -94,7 +94,7 @@ Modern.js 3.0 no longer supports creating Monorepo projects and Modern.js Module
 **Changes**:
 
 - In [v2.53.0](https://github.com/web-infra-dev/modern.js/releases/tag/v2.53.0), the functionality to create Monorepo projects using `@bleedingdev/modern-js-create` was removed
-- In [v2.61.0](https://github.com/web-infra-dev/modern.js/releases/tag/v2.61.0), the functionality to create Modern.js Module projects using `@bleedingdev/modern-js-create` and `ultramodern new` commands was removed
+- In [v2.61.0](https://github.com/web-infra-dev/modern.js/releases/tag/v2.61.0), the functionality to create Modern.js Module projects using `@bleedingdev/modern-js-create` and `modern new` commands was removed
 
 **Handling**:
 
@@ -103,12 +103,12 @@ Modern.js 3.0 no longer supports creating Monorepo projects and Modern.js Module
 
 ## new and upgrade Commands Removed
 
-Modern.js 3.0 removed the `ultramodern new` and `ultramodern upgrade` commands, and you need to perform operations manually according to the documentation.
+Modern.js 3.0 removed the `modern new` and `modern upgrade` commands, and you need to perform operations manually according to the documentation.
 
 **Changes**:
 
-- The `ultramodern new` command is no longer supported in Modern.js 3.0, and you cannot add entries or enable features through commands
-- The `ultramodern upgrade` command is no longer supported in Modern.js 3.0, and you cannot automatically upgrade dependencies through commands
+- The `modern new` command is no longer supported in Modern.js 3.0, and you cannot add entries or enable features through commands
+- The `modern upgrade` command is no longer supported in Modern.js 3.0, and you cannot automatically upgrade dependencies through commands
 
 **Handling**:
 

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

@@ -8,12 +8,12 @@ UltraModern.js 内置了一些命令，可以帮助你快速启动开发服务
 
 通过本章节，你可以了解到 UltraModern.js 内置的命令有哪些，以及如何使用这些命令。
 
-## ultramodern dev
+## modern dev
 
-`ultramodern dev` 命令用于启动一个本地开发服务器，对源代码进行开发环境编译。
+`modern dev` 命令用于启动一个本地开发服务器，对源代码进行开发环境编译。
 
 ```bash
-Usage: ultramodern dev [options]
+Usage: modern dev [options]
 
 Options:
   -e --entry <entry>    指定入口，只编译特定的页面
@@ -23,10 +23,10 @@ Options:
   --api-only            仅启动 API 接口服务
 ```
 
-运行 `ultramodern dev` 后，UltraModern.js 会监听源文件变化并进行模块热更新。
+运行 `modern dev` 后，UltraModern.js 会监听源文件变化并进行模块热更新。
 
 ```bash
-$ ultramodern dev
+$ modern dev
 
 info    Starting dev server...
 
@@ -38,10 +38,10 @@ info    Starting dev server...
 
 在多页面（MPA）项目中，可以添加 `--entry` 参数来指定编译其中的一个或多个页面。这样可以只编译项目中的部分代码，从而提升 dev 启动速度。
 
-比如执行 `ultramodern dev --entry`，在命令行界面中会展示入口选择框：
+比如执行 `modern dev --entry`，在命令行界面中会展示入口选择框：
 
 ```bash
-$ ultramodern dev --entry
+$ modern dev --entry
 
 ? 请选择需要构建的入口
 ❯ ◯ foo
@@ -57,22 +57,22 @@ $ ultramodern dev --entry
 
 ```bash
 # 编译 foo 页面
-ultramodern dev --entry foo
+modern dev --entry foo
 
 # 编译 foo 和 bar 页面
-ultramodern dev --entry foo,bar
+modern dev --entry foo,bar
 ```
 
-## ultramodern start
+## modern start
 
-`ultramodern start` 是 `ultramodern dev` 命令的别名，两者的功能和用法完全一致。
+`modern start` 是 `modern dev` 命令的别名，两者的功能和用法完全一致。
 
-## ultramodern build
+## modern build
 
-`ultramodern build` 命令默认会在 `dist/` 目录下构建出可用于生产环境的产物。你可以通过修改配置 [`output.distPath`](/configure/app/output/dist-path) 指定产物的输出目录。
+`modern build` 命令默认会在 `dist/` 目录下构建出可用于生产环境的产物。你可以通过修改配置 [`output.distPath`](/configure/app/output/dist-path) 指定产物的输出目录。
 
 ```bash
-Usage: ultramodern build [options]
+Usage: modern build [options]
 
 Options:
   -c --config <config>  指定配置文件路径，可以为相对路径或绝对路径
@@ -80,80 +80,70 @@ Options:
   -w --watch  开启 watch 模式, 监听文件变更并重新构建
 ```
 
-## ultramodern new
+## modern runtime status
 
-`ultramodern new` 命令用于在已有项目中添加项目元素。
-
-比如添加应用入口、启用一些可选功能如 BFF、微前端开发模式等。
+`modern runtime status` 命令用于读取运行时状态端点并打印响应。默认请求 `http://127.0.0.1:8080/_modern/runtime/status`。
 
 ```bash
-Usage: ultramodern new [options]
+Usage: modern runtime status [options]
 
 Options:
-  --config-file <configFile>  指定配置文件路径，可以为相对路径或绝对路径
-  --lang <lang>          设置 new 命令执行语言(zh 或者 en)
-  -d, --debug            开启 Debug 模式，打印调试日志信息 (default: false)
-  -c, --config <config>  生成器运行默认配置(JSON 字符串)
-  --dist-tag <tag>       生成器使用特殊的 npm Tag 版本
-  --registry             生成器运行过程中定制 npm Registry
+  --endpoint <endpoint>  运行时状态端点 URL 或路径
+  --token <token>        运行时状态鉴权 Token
+  --token-env <name>     保存运行时状态鉴权 Token 的环境变量名称 (default: "MODERN_RUNTIME_SIGNAL_TOKEN")
+  --header-name <name>   鉴权请求头名称 (default: "x-modernjs-runtime-signal-token")
+  --timeout <ms>         请求超时时间，单位毫秒 (default: "5000")
+  --json                 以 JSON 格式输出，便于机器读取
   -h, --help             显示命令帮助
 ```
 
-### 添加入口
+如果 `--endpoint` 是路径，命令会基于 `http://127.0.0.1:8080` 解析该路径。如果省略 `--token`，命令会从 `--token-env` 指定的环境变量中读取 Token。
 
-在 Modern.js 工程中，执行 `new` 命令添加入口的步骤如下：
+默认情况下，命令会将响应格式化为可读的键值行。添加 `--json` 后会打印原始 JSON 载荷。
 
 ```bash
-$ npx ultramodern new
-? 请选择你想要的操作 创建工程元素
-? 请选择创建元素类型 新建「应用入口」
-? 请填写入口名称 entry
+modern runtime status --json
 ```
 
-### 启用可选功能
+## modern runtime fallback-signal
 
-在 Modern.js 工程中，执行 `new` 命令启用可选能力的步骤如下：
+`modern runtime fallback-signal` 命令用于向金丝雀 contract-gate 端点发送运行时 fallback 信号。默认请求 `http://127.0.0.1:8080/_modern/contract-gates/runtime-fallback`。
 
 ```bash
-$ npx ultramodern new
-? 请选择你想要的操作 启用可选功能
-? 请选择功能名称 (Use arrow keys)
-❯ 启用「BFF」功能
-  启用「微前端」模式
-```
+Usage: modern runtime fallback-signal [options]
 
-:::tip
-`--config` 参数对应参数值需要使用 JSON 字符串。
+Options:
+  --app <appName>          远程应用名称
+  --endpoint <endpoint>    运行时 fallback 信号端点 URL 或路径
+  --reason <reason>        fallback 原因 (default: "runtime_fallback")
+  --phase <phase>          fallback 阶段 (default: "load")
+  --entry <entry>          远程入口 URL
+  --runtime-digest <digest>  运行时 digest 值
+  --metadata <json>        metadata JSON 对象字符串
+  --token <token>          运行时信号鉴权 Token
+  --token-env <name>       保存运行时信号鉴权 Token 的环境变量名称 (default: "MODERN_RUNTIME_SIGNAL_TOKEN")
+  --header-name <name>     鉴权请求头名称 (default: "x-modernjs-runtime-signal-token")
+  --timeout <ms>           请求超时时间，单位毫秒 (default: "5000")
+  --json                   以 JSON 格式输出，便于机器读取
+  -h, --help               显示命令帮助
+```
 
-pnpm 暂不支持使用 JSON 字符串作为参数值，可使用 `npm new` 开启相关功能。【[相关 Issue](https://github.com/pnpm/pnpm/issues/3876)】
+请求体始终包含 `appName`、`reason` 和 `phase`。只有在提供对应选项时，才会包含 `entry`、`runtimeDigest` 和 `metadata`。`--metadata` 必须是 JSON 对象字符串。
 
-:::
+```bash
+modern runtime fallback-signal --app crm-shell --reason remote_load_failed --phase load --json
+```
 
 import ServeCommand from '@site-docs/components/serve-command';
 
 <ServeCommand />
 
-## ultramodern upgrade
-
-在项目根目录下执行命令 `npx ultramodern upgrade`，会默认将当前执行命令项目的 `package.json` 中的 UltraModern.js 相关依赖更新至最新版本。
-
-```bash
-Usage: ultramodern upgrade [options]
-
-Options:
-  -c --config <config>  指定配置文件路径，可以为相对路径或绝对路径
-  --registry <registry>  定制 npm registry (default: "")
-  -d,--debug             开启 Debug 模式，打印调试日志信息 (default: false)
-  --cwd <cwd>            项目路径 (default: "")
-  -h, --help             display help for command
-```
-
-## ultramodern inspect
+## modern inspect
 
-`ultramodern inspect` 命令用于查看项目的 UltraModern.js 配置、[Rsbuild 配置](https://v2.rsbuild.rs/zh/config/index) 以及 Rspack 配置。
+`modern inspect` 命令用于查看项目的 UltraModern.js 配置、[Rsbuild 配置](https://v2.rsbuild.rs/zh/config/index) 以及 Rspack 配置。
 
 ```bash
-Usage: ultramodern inspect [options]
+Usage: modern inspect [options]
 
 Options:
   --env <env>           查看指定环境下的配置 (default: "development")
@@ -163,14 +153,14 @@ Options:
   -h, --help            显示命令帮助
 ```
 
-在项目根目录下执行命令 `npx ultramodern inspect` 后，会在项目的 `dist` 目录生成以下文件：
+在项目根目录下执行命令 `npx modern inspect` 后，会在项目的 `dist` 目录生成以下文件：
 
 - `modern.js.config.mjs`: 表示当前使用的 Modern.js 配置。
 - `rsbuild.config.mjs`: 表示在构建时使用的 Rsbuild 配置。
 - `rspack.config.web.mjs`: 表示在构建时使用的 Rspack 配置。
 
 ```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:
 默认情况下，inspect 命令会输出开发环境的配置，你可以添加 `--env production` 选项来输出生产环境的配置：
 
 ```bash
-ultramodern inspect --env production
+modern inspect --env production
 ```
 
 ### 完整内容
@@ -192,7 +182,7 @@ ultramodern inspect --env production
 默认情况下，inspect 命令会省略配置对象中的函数内容，你可以添加 `--verbose` 选项来输出函数的完整内容：
 
 ```bash
-ultramodern inspect --verbose
+modern inspect --verbose
 ```
 
 ### SSR 构建配置
@@ -200,7 +190,7 @@ ultramodern inspect --verbose
 如果项目开启了 SSR 能力，则在 `dist` 目录会另外生成一份 `rspack.config.node.mjs` 文件，对应 SSR 构建时的 Rspack 配置。
 
 ```bash
-➜ npx ultramodern inspect
+➜ npx modern inspect
 
 Inspect config succeed, open following files to view the content: