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

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

@@ -197,13 +197,13 @@ The generated `api.client.*` API only exists for loader-materialized `@api/index
 ## Effect cohort
 
 UltraModern-generated workspaces pin the framework-compatible Effect cohort
-through `pnpm-workspace.yaml` overrides. For `3.5.0-ultramodern.1`, generated
+through `pnpm-workspace.yaml` overrides. For `3.5.0-ultramodern.2`, generated
 apps use:
 
 ```yaml
 overrides:
-  '@effect/vitest': 4.0.0-beta.89
-  effect: 4.0.0-beta.89
+  '@effect/vitest': 4.0.0-beta.91
+  effect: 4.0.0-beta.91
 ```
 
 Do not add a different direct `effect` version in an app package. A mismatched

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

@@ -78,20 +78,20 @@ mise exec -- pnpm check
 mise exec -- pnpm build
 ```
 
-Strict generated API migration requires `3.5.0-ultramodern.1` or newer.
+Strict generated API migration requires `3.5.0-ultramodern.2` or newer.
 `3.4.0-ultramodern.20` and earlier cohorts do not include this full direct
 `api/index.ts` generator, generated `.mts` checks, strict Oxlint boundary rule
 set, Effect cohort overrides, and strict Effect migration command. Agents that
 cannot install that BleedingDev cohort yet should use the local Modern.js
-workspace for migration validation; otherwise pin `3.5.0-ultramodern.1` or
+workspace for migration validation; otherwise pin `3.5.0-ultramodern.2` or
 newer with `--ultramodern-package-version`.
 
 Before hand-editing package aliases or generated metadata, run the framework
 migration command from the target workspace:
 
 ```bash
-pnpm dlx @bleedingdev/modern-js-create@3.5.0-ultramodern.1 ultramodern \
-  migrate-strict-effect --version 3.5.0-ultramodern.1
+pnpm dlx @bleedingdev/modern-js-create@3.5.0-ultramodern.2 ultramodern \
+  migrate-strict-effect --version 3.5.0-ultramodern.2
 pnpm api:check
 pnpm contract:check
 ```
@@ -103,7 +103,7 @@ move code to `shared/api.ts`, `api/index.ts`, and `src/api/*-client.ts`, then
 delete `api/effect`, `api/lambda`, `shared/effect`, and `src/effect`.
 
 Generated strict Effect workspaces pin the compatible Effect cohort with pnpm
-overrides: `effect@4.0.0-beta.89` and `@effect/vitest@4.0.0-beta.89`. Do not
+overrides: `effect@4.0.0-beta.91` and `@effect/vitest@4.0.0-beta.91`. Do not
 add app-local direct Effect versions that disagree with those overrides.
 
 Gradual migration means old, unmigrated Modern.js apps can keep their existing

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

@@ -195,12 +195,12 @@ export default defineConfig({
 ## Effect 版本组
 
 UltraModern 生成的 workspace 会通过 `pnpm-workspace.yaml` overrides 锁定与框架兼容的
-Effect 版本组。`3.5.0-ultramodern.1` 使用：
+Effect 版本组。`3.5.0-ultramodern.2` 使用：
 
 ```yaml
 overrides:
-  '@effect/vitest': 4.0.0-beta.89
-  effect: 4.0.0-beta.89
+  '@effect/vitest': 4.0.0-beta.91
+  effect: 4.0.0-beta.91
 ```
 
 不要在应用包里添加不同版本的直接 `effect` 依赖。Effect beta 不一致时，Layer 或 HTTP

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

@@ -71,18 +71,18 @@ mise exec -- pnpm check
 mise exec -- pnpm build
 ```
 
-严格生成 API 迁移要求 `3.5.0-ultramodern.1` 或更新版本。
+严格生成 API 迁移要求 `3.5.0-ultramodern.2` 或更新版本。
 `3.4.0-ultramodern.20` 及更早 cohort 还没有这套完整的直接
 `api/index.ts` 生成器、生成的 `.mts` 检查、严格 Oxlint 边界规则、Effect 版本组
 overrides 和严格 Effect 迁移命令。还不能安装该 BleedingDev cohort 的 agent 应使用本地
 Modern.js workspace 做迁移校验；否则用 `--ultramodern-package-version` 固定
-`3.5.0-ultramodern.1` 或更新版本。
+`3.5.0-ultramodern.2` 或更新版本。
 
 手写 package alias 或生成 metadata 之前，先在目标 workspace 运行框架迁移命令：
 
 ```bash
-pnpm dlx @bleedingdev/modern-js-create@3.5.0-ultramodern.1 ultramodern \
-  migrate-strict-effect --version 3.5.0-ultramodern.1
+pnpm dlx @bleedingdev/modern-js-create@3.5.0-ultramodern.2 ultramodern \
+  migrate-strict-effect --version 3.5.0-ultramodern.2
 pnpm api:check
 pnpm contract:check
 ```
@@ -93,7 +93,7 @@ Modern package alias、直接 topology API metadata 和 pnpm lockfile。剩余
 `api/effect`、`api/lambda`、`shared/effect` 和 `src/effect`。
 
 严格 Effect 生成 workspace 会通过 pnpm overrides 固定兼容版本组：
-`effect@4.0.0-beta.89` 和 `@effect/vitest@4.0.0-beta.89`。不要添加与这些
+`effect@4.0.0-beta.91` 和 `@effect/vitest@4.0.0-beta.91`。不要添加与这些
 overrides 冲突的 app 本地直接 Effect 版本。
 
 渐进迁移意味着尚未迁移的旧 Modern.js app 可以保留现有 runtime，直到被转换为

package/package.json

@@ -19,24 +19,24 @@
     "modern.js",
     "ultramodern.js"
   ],
-  "version": "3.5.0-ultramodern.1",
+  "version": "3.5.0-ultramodern.2",
   "publishConfig": {
     "registry": "https://registry.npmjs.org/",
     "access": "public"
   },
   "dependencies": {
-    "mermaid": "^11.15.0",
-    "@modern-js/sandpack-react": "npm:@bleedingdev/modern-js-sandpack-react@3.5.0-ultramodern.1"
+    "mermaid": "^11.16.0",
+    "@modern-js/sandpack-react": "npm:@bleedingdev/modern-js-sandpack-react@3.5.0-ultramodern.2"
   },
   "devDependencies": {
     "@rsbuild/plugin-sass": "2.0.0",
-    "@rspress/core": "2.0.14",
-    "@rspress/plugin-llms": "2.0.14",
-    "@rspress/shared": "2.0.14",
+    "@rspress/core": "2.0.15",
+    "@rspress/plugin-llms": "2.0.15",
+    "@rspress/shared": "2.0.15",
     "@shikijs/transformers": "^4.3.0",
     "@types/fs-extra": "11.0.4",
     "@types/node": "^26.0.1",
-    "@typescript/native-preview": "7.0.0-dev.20260624.1",
+    "@typescript/native-preview": "7.0.0-dev.20260628.1",
     "classnames": "^2.5.1",
     "clsx": "^2.1.1",
     "fs-extra": "^11.3.5",