@bleedingdev/modern-js-main-doc 3.5.0-ultramodern.99 → 3.8.1-ultramodern.2

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.17.0
+mise use pnpm@11.21.0
 ```
 
 :::note

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

@@ -54,7 +54,7 @@ would give your app a second Effect identity. Before setting
 `/effect-server`, `/effect-edge` or `/effect-client`, install the exact cohort:
 
 ```bash
-pnpm add effect@4.0.0-beta.102 @effect/opentelemetry@4.0.0-beta.102
+pnpm add effect@4.0.0-beta.107 @effect/opentelemetry@4.0.0-beta.107
 ```
 
 The pin is exact because UltraModern ships Effect as one lockstep cohort. Apps
@@ -218,27 +218,25 @@ through `pnpm-workspace.yaml` overrides. For the current UltraModern cohort,
 generated apps use:
 
 ```yaml
-minimumReleaseAgeExclude:
-  - 'effect@4.0.0-beta.102'
-  - '@effect/opentelemetry@4.0.0-beta.102'
-
 trustPolicyExclude:
-  - 'effect@4.0.0-beta.102'
-  - '@effect/opentelemetry@4.0.0-beta.102'
+  - 'effect@4.0.0-beta.107'
+  - '@effect/opentelemetry@4.0.0-beta.107'
 
 overrides:
-  '@effect/opentelemetry': 4.0.0-beta.102
-  '@effect/vitest': 4.0.0-beta.102
-  effect: 4.0.0-beta.102
+  '@effect/opentelemetry': 4.0.0-beta.107
+  '@effect/vitest': 4.0.0-beta.107
+  effect: 4.0.0-beta.107
 ```
 
 Do not add a different direct `effect` version in an app package. A mismatched
 Effect beta can fail while building layers or HTTP middleware because runtime
-services come from different package instances. Keep the generated
-policy exclusion entries with the same Effect cohort; they handle the
-framework-selected Effect beta versions before the 24-hour maturity window and
-the `effect`/`@effect/opentelemetry` trusted-publisher to provenance metadata
-transition without weakening UltraModern API architecture checks.
+services come from different package instances. The strict 24-hour release-age
+gate applies to installed packages; the current cohort has no Effect age
+exemption, and override-only `@effect/vitest` is not an installed approval
+target. `trustPolicyExclude` is a separate policy:
+its exact `effect` and `@effect/opentelemetry` exceptions cover their
+trusted-publisher to provenance metadata transition and are not release-age
+approvals.
 
 ## Contract tests
 

package/docs/en/configure/app/server/rsc.mdx

@@ -7,24 +7,20 @@ title: rsc
 - **Type:** `boolean`
 - **Default:** `false`
 
-Enable React Server Components (RSC) configuration.
+Configure React Server Components (RSC).
 
-When set to `true`, enables React Server Components support in Modern.js. This allows components to be rendered on the server, providing better performance and developer experience.
+:::warning UltraModern availability
+RSC is not shipped or supported in the current UltraModern company distribution. Keep this option `false`. The Rspack Flight runtime remains under upstream review, and enabling RSC intentionally fails unless an application supplies the complete optional toolchain.
+
+Do not install `react-server-dom-rspack` or add an application-level pnpm patch to bypass this boundary.
+:::
 
 ```ts title="modern.config.ts"
 export default defineConfig({
   server: {
-    rsc: true,
+    rsc: false,
   },
 });
 ```
 
-:::tip Prerequisites
-Before enabling RSC, ensure:
-1. React and React DOM are upgraded to version 19 (recommended 19.2.4 or above)
-2. Install the `react-server-dom-rspack@0.0.2` dependency
-
-:::
-
-For more information about using RSC, see the [React Server Components guide](/guides/basic-features/render/rsc).
-
+The [React Server Components guide](/guides/basic-features/render/rsc) is retained as reference material for future upstream adoption.

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

@@ -21,29 +21,20 @@ Before starting, we recommend reading React's official [Server Components docume
 
 ## Quick Start
 
-1. **Ensure React and React DOM are upgraded to version 19** (recommended version 19.2.4 or above)
-
-2. **Install the `react-server-dom-rspack@0.0.2` dependency**
-
-```bash
-npm install react-server-dom-rspack@0.0.2
-```
-
-:::warning Notes
-
-1. Currently, [Server Functions](https://react.dev/reference/rsc/server-functions) are not supported in SPA projects
-2. Currently, when building with Rspack, the output chunks and bundle size are not yet optimal. We will further optimize this in the near future
+:::warning UltraModern availability
+RSC is not shipped or supported in the current UltraModern company distribution. The framework keeps [`server.rsc`](/configure/app/server/rsc) disabled while the Rspack Flight runtime is completed upstream. Do not install `react-server-dom-rspack` or carry an application-level pnpm patch to enable it early.
 
+The remainder of this page is retained as reference material for future upstream adoption.
 :::
 
-3. Set [`server.rsc`](/configure/app/server/rsc) to `true`:
+Keep [`server.rsc`](/configure/app/server/rsc) set to `false`:
 
 ```ts title="modern.config.ts"
 import { defineConfig } from '@modern-js/app-tools';
 
 export default defineConfig({
   server: {
-    rsc: true,
+    rsc: false,
   },
 });
 ```

package/docs/en/guides/get-started/ai-coding-agents.mdx

@@ -18,7 +18,7 @@ AI agents use them to get APIs, config, and conventions that exactly match your
 `AGENTS.md` gives AI coding agents project-level guidance — telling them to read the bundled docs before making changes and to follow Modern.js conventions. A `CLAUDE.md` is generated alongside it, reusing the same guidance for Claude Code via the `@AGENTS.md` import.
 
 - **New projects**: `npx @modern-js/create` generates both files by default; pass `--no-agents-md` to skip them.
-- **Existing projects**: run `npx @modern-js/create agents-md` at the project root to create or update them. Re-run it any time; your own additions are preserved.
+- **Existing projects**: run `npx @modern-js/create --agents-md-only` at the project root to create or update them. Re-run it any time; your own additions are preserved.
 
 Modern.js only maintains the content inside the `<!-- BEGIN:modernjs-agent-rules -->` markers in `AGENTS.md`; anything you write outside them is left untouched.
 

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

@@ -143,13 +143,25 @@ migration work: move code to `shared/api.ts`, `api/index.ts`, and
 and `src/effect`.
 
 Generated strict Effect workspaces pin the compatible Effect cohort with pnpm
-overrides: `effect@4.0.0-beta.102`, `@effect/opentelemetry@4.0.0-beta.102`,
-and `@effect/vitest@4.0.0-beta.102`. Do not add app-local direct Effect
-versions that disagree with those overrides. They also carry generated pnpm
-policy exclusions for `effect@4.0.0-beta.102` and
-`@effect/opentelemetry@4.0.0-beta.102` so the framework-selected Effect beta
-cohort is not blocked by the 24-hour age gate or trusted-publisher to
-provenance metadata transition.
+overrides: `effect@4.0.0-beta.107`, `@effect/opentelemetry@4.0.0-beta.107`,
+and `@effect/vitest@4.0.0-beta.107`. Do not add app-local direct Effect
+versions that disagree with those overrides. The strict 24-hour release-age
+gate applies to installed packages; this cohort carries no Effect age
+exemption, and override-only `@effect/vitest` is not an installed approval
+target. Independently, exact `trustPolicyExclude` entries for `effect`
+and `@effect/opentelemetry` cover their trusted-publisher to provenance
+metadata transition; they are not release-age approvals.
+
+### Current generated dependency baseline
+
+| Surface | Pin |
+| --- | --- |
+| Effect runtime and test cohort | `effect`, `@effect/opentelemetry`, and `@effect/vitest`: `4.0.0-beta.107` |
+| Effect compiler | `@effect/tsgo@0.36.2` |
+| TanStack Router | `@tanstack/react-router@1.170.25`, `@tanstack/router-core@1.171.21`, `@tanstack/history@1.162.1` |
+| Module Federation | `bridge-react`, `manifest`, `modern-js-v3`, and `rspack`: `2.8.2`; `@module-federation/node@2.7.49` |
+| React Router | `react-router@7.18.2` |
+| Node and package tooling | Node `26.7.0`, `@types/node@^26.2.0`, pnpm `11.21.0` |
 
 Gradual migration means old, unmigrated Modern.js apps can keep their existing
 runtime until they are converted. Once a surface is generated or migrated as

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

@@ -24,7 +24,7 @@ All Modern.js official packages are released with a **uniform version number**,
    - Visit [npm](https://www.npmjs.com/package/@modern-js/app-tools) to check the latest version of `@modern-js/app-tools`
    - Check [GitHub Releases](https://github.com/web-infra-dev/modern.js/releases)
 
-   <ReleaseNote />
+<ReleaseNote />
 
 2. **Update package.json**
 
@@ -46,7 +46,7 @@ All Modern.js official packages are released with a **uniform version number**,
 
    After updating `package.json`, reinstall dependencies:
 
-   <PackageManagerTabs command="install" />
+<PackageManagerTabs command="install" />
 
 :::tip
 When upgrading, you need to upgrade all packages provided by Modern.js uniformly, rather than upgrading individual dependencies. Ensure that all `@modern-js/**` packages have the same version number.
@@ -72,16 +72,11 @@ When a nested dependency of the project has a problem and Modern.js cannot be up
 
 ### pnpm
 
-For projects using pnpm, add the following configuration to the `package.json` in the **root directory** of the project, and then run `pnpm install` again:
+For projects using pnpm, add the following configuration to `pnpm-workspace.yaml` in the **root directory** of the project, and then run `pnpm install` again:
 
-```json title="package.json"
-{
-  "pnpm": {
-    "overrides": {
-      "package-name": "^1.0.0"
-    }
-  }
-}
+```yaml title="pnpm-workspace.yaml"
+overrides:
+  package-name: ^1.0.0
 ```
 
 ### Yarn
@@ -109,6 +104,6 @@ For projects using Npm, add the following configuration to the `package.json` in
 ```
 
 :::info
-For Monorepo repositories, you can only lock dependency versions in the `package.json` in the root directory of the project, and it will affect all packages in the Monorepo.
+For Monorepo repositories, lock dependency versions in the package-manager configuration at the project root. The override affects every package in the Monorepo.
 
 :::

package/docs/zh/components/prerequisites.mdx

@@ -9,7 +9,7 @@ import NodeVersion from '@site-docs/components/nodeVersion.mdx';
 推荐使用 [pnpm](https://pnpm.io/installation) 来管理依赖：
 
 ```bash
-mise use pnpm@11.17.0
+mise use pnpm@11.21.0
 ```
 
 :::note

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

@@ -53,7 +53,7 @@ import EnableBFFCaution from "@site-docs/components/enable-bff-caution";
 `/effect-client` 之前，请安装精确版本的依赖组：
 
 ```bash
-pnpm add effect@4.0.0-beta.102 @effect/opentelemetry@4.0.0-beta.102
+pnpm add effect@4.0.0-beta.107 @effect/opentelemetry@4.0.0-beta.107
 ```
 
 采用精确版本是因为 UltraModern 以锁步依赖组的方式发布 Effect。只使用
@@ -213,25 +213,23 @@ UltraModern 生成的 workspace 会通过 `pnpm-workspace.yaml` overrides 锁定
 Effect 版本组。当前 UltraModern 版本组使用：
 
 ```yaml
-minimumReleaseAgeExclude:
-  - 'effect@4.0.0-beta.102'
-  - '@effect/opentelemetry@4.0.0-beta.102'
-
 trustPolicyExclude:
-  - 'effect@4.0.0-beta.102'
-  - '@effect/opentelemetry@4.0.0-beta.102'
+  - 'effect@4.0.0-beta.107'
+  - '@effect/opentelemetry@4.0.0-beta.107'
 
 overrides:
-  '@effect/opentelemetry': 4.0.0-beta.102
-  '@effect/vitest': 4.0.0-beta.102
-  effect: 4.0.0-beta.102
+  '@effect/opentelemetry': 4.0.0-beta.107
+  '@effect/vitest': 4.0.0-beta.107
+  effect: 4.0.0-beta.107
 ```
 
 不要在应用包里添加不同版本的直接 `effect` 依赖。Effect beta 不一致时，Layer 或 HTTP
-middleware 构建可能因为运行时 service 来自不同包实例而失败。保留生成的 policy
-exclusion 条目并让它跟随同一个 Effect 版本组；它用于处理框架选定 Effect beta 版本在
-24 小时成熟期内的安装，以及 `effect` 和 `@effect/opentelemetry` 从 trusted-publisher
-metadata 迁移到 provenance attestation 时的 pnpm no-downgrade 检查。
+middleware 构建可能因为运行时 service 来自不同包实例而失败。严格的 24 小时发布年龄
+门禁适用于实际安装的包；当前版本组没有 Effect 年龄豁免，且仅用于 override 的
+`@effect/vitest` 不是已安装的审批目标。
+`trustPolicyExclude` 是另一项独立策略：其中精确的 `effect` 与
+`@effect/opentelemetry` 例外用于处理 trusted-publisher metadata 向 provenance
+attestation 的迁移，并不等同于 release-age 审批。
 
 ## 契约测试
 

package/docs/zh/configure/app/server/rsc.mdx

@@ -7,24 +7,20 @@ title: rsc
 - **类型：** `boolean`
 - **默认值：** `false`
 
-启用 React Server Components (RSC) 配置。
+配置 React Server Components (RSC)。
 
-当设置为 `true` 时，启用 Modern.js 的 React Server Components 支持。这允许组件在服务端渲染，提供更好的性能和开发体验。
+:::warning UltraModern 可用性
+当前 UltraModern 公司发行版不提供也不支持 RSC。请保持该选项为 `false`。Rspack Flight 运行时仍在上游审查中；除非应用显式提供完整的可选工具链，否则启用 RSC 会按设计失败。
+
+请勿安装 `react-server-dom-rspack`，也不要添加应用级 pnpm 补丁来绕过此边界。
+:::
 
 ```ts title="modern.config.ts"
 export default defineConfig({
   server: {
-    rsc: true,
+    rsc: false,
   },
 });
 ```
 
-:::tip 前置条件
-在启用 RSC 之前，请确保：
-1. React 和 React DOM 已升级到 19 版本（建议 19.2.4 以上版本）
-2. 已安装 `react-server-dom-rspack@0.0.2` 依赖
-
-:::
-
-有关使用 RSC 的更多信息，请参阅 [React Server Components 指南](/guides/basic-features/render/rsc)。
-
+[React Server Components 指南](/guides/basic-features/render/rsc) 仅作为未来采用上游实现时的参考资料保留。

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

@@ -21,29 +21,20 @@ React Server Components (RSC) 是一种新的组件类型，允许在服务端
 
 ## 快速开始
 
-1. **确保 React 和 React DOM 升级到 19 版本**（建议 19.2.4 以上版本）
-
-2. **安装 `react-server-dom-rspack@0.0.2` 依赖**
-
-```bash
-npm install react-server-dom-rspack@0.0.2
-```
-
-:::warning 注意事项
-
-1. 目前暂不支持在 SPA 项目中使用 [Server Functions](https://react.dev/reference/rsc/server-functions)
-2. 目前在 Rspack 构建时，产物分片和体积还未达到最优状态，我们将在近期进一步优化
+:::warning UltraModern 可用性
+当前 UltraModern 公司发行版不提供也不支持 RSC。在 Rspack Flight 运行时完成上游工作之前，框架会保持 [`server.rsc`](/configure/app/server/rsc) 关闭。请勿安装 `react-server-dom-rspack`，也不要携带应用级 pnpm 补丁来提前启用它。
 
+本页其余内容仅作为未来采用上游实现时的参考资料保留。
 :::
 
-3. 设置 [`server.rsc`](/configure/app/server/rsc) 为 `true`：
+请保持 [`server.rsc`](/configure/app/server/rsc) 为 `false`：
 
 ```ts title="modern.config.ts"
 import { defineConfig } from '@modern-js/app-tools';
 
 export default defineConfig({
   server: {
-    rsc: true,
+    rsc: false,
   },
 });
 ```

package/docs/zh/guides/get-started/ai-coding-agents.mdx

@@ -18,7 +18,7 @@ AI Agent 由此获取与当前框架版本严格匹配的 API、配置与约定
 `AGENTS.md` 是给 AI 编码助手的项目指引，告诉它在动手前先阅读随包文档、并遵循 Modern.js 的约定；同时会生成 `CLAUDE.md`，通过 `@AGENTS.md` 让 Claude Code 复用同一份指引。
 
 - **新建项目**：`npx @modern-js/create` 默认生成这两个文件，加 `--no-agents-md` 可跳过。
-- **已有项目**：在项目根运行 `npx @modern-js/create agents-md` 生成或更新，可随时重复运行，你添加的自定义内容会被保留。
+- **已有项目**：在项目根运行 `npx @modern-js/create --agents-md-only` 生成或更新，可随时重复运行，你添加的自定义内容会被保留。
 
 Modern.js 只维护 `AGENTS.md` 中 `<!-- BEGIN:modernjs-agent-rules -->` 标记内的内容，标记之外你写的内容不会被改动。
 

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

@@ -128,12 +128,24 @@ pnpm overrides/trust policy 和 pnpm lockfile。剩余失败就是源码迁移
 `api/lambda`、`shared/effect` 和 `src/effect`。
 
 严格 Effect 生成 workspace 会通过 pnpm overrides 固定兼容版本组：
-`effect@4.0.0-beta.102`、`@effect/opentelemetry@4.0.0-beta.102` 和
-`@effect/vitest@4.0.0-beta.102`。不要添加与这些 overrides 冲突的 app 本地直接
-Effect 版本。生成的 pnpm policy 还会为 `effect@4.0.0-beta.102` 和
-`@effect/opentelemetry@4.0.0-beta.102` 添加例外，避免框架选定的 Effect beta
-版本组被 24 小时成熟期检查，或从 trusted-publisher metadata 迁移到 provenance
-attestation 时被 no-downgrade 检查误拦截。
+`effect@4.0.0-beta.107`、`@effect/opentelemetry@4.0.0-beta.107` 和
+`@effect/vitest@4.0.0-beta.107`。不要添加与这些 overrides 冲突的 app 本地直接
+Effect 版本。严格的 24 小时发布年龄门禁适用于实际安装的包；当前版本组不包含 Effect
+年龄豁免，仅用于 override 的 `@effect/vitest` 也不是已安装的审批目标。
+`trustPolicyExclude` 是独立策略，仅为 `effect` 和
+`@effect/opentelemetry` 保留精确例外，以处理 trusted-publisher metadata 向
+provenance attestation 的迁移；它不属于 release-age 审批。
+
+### 当前生成依赖基线
+
+| 范围 | 固定版本 |
+| --- | --- |
+| Effect runtime 与测试版本组 | `effect`、`@effect/opentelemetry`、`@effect/vitest`：`4.0.0-beta.107` |
+| Effect compiler | `@effect/tsgo@0.36.2` |
+| TanStack Router | `@tanstack/react-router@1.170.25`、`@tanstack/router-core@1.171.21`、`@tanstack/history@1.162.1` |
+| Module Federation | `bridge-react`、`manifest`、`modern-js-v3`、`rspack`：`2.8.2`；`@module-federation/node@2.7.49` |
+| React Router | `react-router@7.18.2` |
+| Node 与包管理工具 | Node `26.7.0`、`@types/node@^26.2.0`、pnpm `11.21.0` |
 
 渐进迁移意味着尚未迁移的旧 Modern.js app 可以保留现有 runtime，直到被转换为
 UltraModern。一个 surface 一旦生成为或迁移为 UltraModern HTTP API，就只能使用

package/docs/zh/guides/get-started/upgrade.mdx

@@ -24,7 +24,7 @@ Modern.js 所有的官方包使用**统一版本号**进行发布，因此升级
    - 访问 [npm](https://www.npmjs.com/package/@modern-js/app-tools) 查看 `@modern-js/app-tools` 的最新版本
    - 查看 [GitHub Releases](https://github.com/web-infra-dev/modern.js/releases)
 
-   <ReleaseNote />
+<ReleaseNote />
 
 2. **更新 package.json**
 
@@ -46,7 +46,7 @@ Modern.js 所有的官方包使用**统一版本号**进行发布，因此升级
 
    更新完 `package.json` 后，重新安装依赖：
 
-   <PackageManagerTabs command="install" />
+<PackageManagerTabs command="install" />
 
 :::tip
 当升级时，需要对 Modern.js 官方提供的所有包做统一升级，而不是升级单个依赖。确保所有 `@modern-js/**` 包的版本号保持一致。
@@ -72,16 +72,11 @@ Modern.js 所有的官方包使用**统一版本号**进行发布，因此升级
 
 ### pnpm
 
-对于使用 pnpm 的项目，请在**项目根目录**的 `package.json` 中添加以下配置，然后重新执行 `pnpm install`：
+对于使用 pnpm 的项目，请在**项目根目录**的 `pnpm-workspace.yaml` 中添加以下配置，然后重新执行 `pnpm install`：
 
-```json title="package.json"
-{
-  "pnpm": {
-    "overrides": {
-      "package-name": "^1.0.0"
-    }
-  }
-}
+```yaml title="pnpm-workspace.yaml"
+overrides:
+  package-name: ^1.0.0
 ```
 
 ### Yarn
@@ -109,6 +104,6 @@ Modern.js 所有的官方包使用**统一版本号**进行发布，因此升级
 ```
 
 :::info
-对于 Monorepo 仓库，只能在项目根目录的 `package.json` 中锁定依赖版本，并且会影响 Monorepo 中的所有 package。
+对于 Monorepo 仓库，请在项目根目录的包管理器配置中锁定依赖版本；该 override 会影响 Monorepo 中的所有 package。
 
 :::

package/package.json

@@ -19,12 +19,12 @@
     "modern.js",
     "ultramodern.js"
   ],
-  "version": "3.5.0-ultramodern.99",
+  "version": "3.8.1-ultramodern.2",
   "publishConfig": {
     "access": "public"
   },
   "dependencies": {
-    "@modern-js/sandpack-react": "npm:@bleedingdev/modern-js-sandpack-react@3.5.0-ultramodern.99",
+    "@modern-js/sandpack-react": "npm:@bleedingdev/modern-js-sandpack-react@3.8.1-ultramodern.2",
     "mermaid": "^11.16.0"
   },
   "devDependencies": {
@@ -34,17 +34,32 @@
     "@rspress/shared": "2.0.17",
     "@shikijs/transformers": "^4.3.1",
     "@types/fs-extra": "11.0.4",
-    "@types/node": "^26.1.1",
+    "@types/node": "^26.2.0",
     "@typescript/native-preview": "7.0.0-dev.20260707.2",
     "classnames": "^2.5.1",
     "clsx": "^2.1.1",
     "fs-extra": "^11.3.6",
-    "react": "^19.2.7",
-    "react-dom": "^19.2.7",
+    "react": "^19.2.8",
+    "react-dom": "^19.2.8",
     "rsbuild-plugin-open-graph": "1.1.3",
     "ts-node": "^10.9.2",
     "typescript": "^7.0.2"
   },
+  "nx": {
+    "targets": {
+      "build": {
+        "inputs": [
+          "build",
+          "^build",
+          "{projectRoot}/docs/**/*",
+          "{projectRoot}/rspress.config.ts"
+        ],
+        "outputs": [
+          "{projectRoot}/doc_build"
+        ]
+      }
+    }
+  },
   "scripts": {
     "dev": "rspress dev",
     "dev:no_lazy": "LAZY=false rspress dev",