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

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

@@ -197,18 +197,30 @@ 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.10`, generated
 apps use:
 
 ```yaml
+minimumReleaseAgeExclude:
+  - 'effect@4.0.0-beta.91'
+  - '@effect/opentelemetry@4.0.0-beta.91'
+
+trustPolicyExclude:
+  - 'effect@4.0.0-beta.91'
+  - '@effect/opentelemetry@4.0.0-beta.91'
+
 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
 Effect beta can fail while building layers or HTTP middleware because runtime
-services come from different package instances.
+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.
 
 ## Contract tests
 

package/docs/en/configure/app/performance/build-cache.mdx

@@ -28,6 +28,11 @@ type BuildCacheConfig =
 
 Controls the caching behavior during the build process.
 
+When persistent Rspack cache is enabled, Modern.js treats `cacheDirectory` as a
+base directory and stores each Rsbuild/Rspack environment in its own child
+directory, such as `client`, `server`, or `workerSSR`. This avoids concurrent
+environment compilers writing to the same filesystem cache root.
+
 Modern.js will enable build cache by default to improve the compile speed. You can disable the build cache by setting it to `false`:
 
 ```js

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

@@ -78,33 +78,39 @@ 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.10` 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.10` 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.10 ultramodern \
+  migrate-strict-effect --version 3.5.0-ultramodern.10
 pnpm api:check
 pnpm contract:check
 ```
 
 The command updates `.modernjs/ultramodern.json`, root
-`modernjs.packageSource`, generated Modern package aliases, direct topology API
-metadata, and the pnpm lockfile. Remaining failures are source migration work:
-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`.
+`modernjs.packageSource`, generated Modern package aliases, framework-owned
+toolchain pins, direct topology API metadata, strict Effect pnpm
+overrides/trust policy, and the pnpm lockfile. Remaining failures are source
+migration work: 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
-add app-local direct Effect versions that disagree with those overrides.
+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. They
+also carry generated pnpm policy exclusions for `effect@4.0.0-beta.91` and
+`@effect/opentelemetry@4.0.0-beta.91` so the framework-selected Effect beta
+cohort is not blocked by the 24-hour age gate or trusted-publisher to
+provenance metadata transition.
 
 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
@@ -183,9 +189,9 @@ instead of patching generated output by hand.
 Cloudflare D1 bindings are first-class on `deploy.worker.d1Databases`; use that
 config instead of app-local postprocessing when a generated app owns D1
 migrations. Cloudflare public output excludes server-only `api` and `shared`
-directories by default, and generated Modern/Rspack caches are isolated per app
-and build target so local `build` and `cloudflare:build` runs do not share the
-same Rspack cache directory.
+directories by default, and generated Modern/Rspack caches are isolated per app,
+build target, and Rspack environment so local `build`, `cloudflare:build`, and
+multi-environment compilers do not share the same filesystem cache directory.
 
 ## Human Workflow
 

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

@@ -195,16 +195,27 @@ export default defineConfig({
 ## Effect 版本组
 
 UltraModern 生成的 workspace 会通过 `pnpm-workspace.yaml` overrides 锁定与框架兼容的
-Effect 版本组。`3.5.0-ultramodern.1` 使用：
+Effect 版本组。`3.5.0-ultramodern.10` 使用：
 
 ```yaml
+minimumReleaseAgeExclude:
+  - 'effect@4.0.0-beta.91'
+  - '@effect/opentelemetry@4.0.0-beta.91'
+
+trustPolicyExclude:
+  - 'effect@4.0.0-beta.91'
+  - '@effect/opentelemetry@4.0.0-beta.91'
+
 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
-middleware 构建可能因为运行时 service 来自不同包实例而失败。
+middleware 构建可能因为运行时 service 来自不同包实例而失败。保留生成的 policy
+exclusion 条目并让它跟随同一个 Effect 版本组；它用于处理框架选定 Effect beta 版本在
+24 小时成熟期内的安装，以及 `effect` 和 `@effect/opentelemetry` 从 trusted-publisher
+metadata 迁移到 provenance attestation 时的 pnpm no-downgrade 检查。
 
 ## 契约测试
 

package/docs/zh/configure/app/performance/build-cache.mdx

@@ -28,6 +28,10 @@ type BuildCacheConfig =
 
 控制 Modern.js 在构建过程中的缓存行为。
 
+启用 Rspack 持久化缓存时，Modern.js 会把 `cacheDirectory` 视为基础目录，并为每个
+Rsbuild/Rspack environment 写入独立子目录，例如 `client`、`server` 或
+`workerSSR`。这样可以避免并发 environment compiler 写入同一个文件系统 cache 根目录。
+
 在构建时，Modern.js 默认会开启构建缓存来提升二次构建的速度。如果不希望缓存，你可以将 `buildCache` 置为 `false` 将其禁用掉：
 
 ```js

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

@@ -71,30 +71,34 @@ mise exec -- pnpm check
 mise exec -- pnpm build
 ```
 
-严格生成 API 迁移要求 `3.5.0-ultramodern.1` 或更新版本。
+严格生成 API 迁移要求 `3.5.0-ultramodern.10` 或更新版本。
 `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.10` 或更新版本。
 
 手写 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.10 ultramodern \
+  migrate-strict-effect --version 3.5.0-ultramodern.10
 pnpm api:check
 pnpm contract:check
 ```
 
 该命令会更新 `.modernjs/ultramodern.json`、根 `modernjs.packageSource`、生成的
-Modern package alias、直接 topology API metadata 和 pnpm lockfile。剩余失败就是源码迁移：
-把代码移到 `shared/api.ts`、`api/index.ts` 和 `src/api/*-client.ts`，再删除
-`api/effect`、`api/lambda`、`shared/effect` 和 `src/effect`。
+Modern package alias、框架拥有的 toolchain pin、直接 topology API metadata、严格 Effect
+pnpm overrides/trust policy 和 pnpm lockfile。剩余失败就是源码迁移：把代码移到
+`shared/api.ts`、`api/index.ts` 和 `src/api/*-client.ts`，再删除 `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`。不要添加与这些
-overrides 冲突的 app 本地直接 Effect 版本。
+`effect@4.0.0-beta.91` 和 `@effect/vitest@4.0.0-beta.91`。不要添加与这些
+overrides 冲突的 app 本地直接 Effect 版本。生成的 pnpm policy 还会为
+`effect@4.0.0-beta.91` 和 `@effect/opentelemetry@4.0.0-beta.91` 添加例外，避免框架选定的
+Effect beta 版本组被 24 小时成熟期检查，或从 trusted-publisher metadata 迁移到
+provenance attestation 时被 no-downgrade 检查误拦截。
 
 渐进迁移意味着尚未迁移的旧 Modern.js app 可以保留现有 runtime，直到被转换为
 UltraModern。一个 surface 一旦生成为或迁移为 UltraModern HTTP API，就只能使用
@@ -157,8 +161,9 @@ Federation 冲突，都应在对应归属文件中修复，不要手写补丁覆
 
 Cloudflare D1 绑定使用一等配置 `deploy.worker.d1Databases`；生成 app 拥有 D1
 migration 时不要再用 app 本地 postprocess。Cloudflare public output 默认排除服务端
-`api` 和 `shared` 目录，并且生成的 Modern/Rspack cache 会按 app 与构建目标隔离，避免
-本地 `build` 与 `cloudflare:build` 共享同一个 Rspack cache 目录。
+`api` 和 `shared` 目录，并且生成的 Modern/Rspack cache 会按 app、构建目标和 Rspack
+environment 隔离，避免本地 `build`、`cloudflare:build` 以及多 environment compiler
+共享同一个文件系统 cache 目录。
 
 ## 人类工作流
 

package/package.json

@@ -19,24 +19,24 @@
     "modern.js",
     "ultramodern.js"
   ],
-  "version": "3.5.0-ultramodern.1",
+  "version": "3.5.0-ultramodern.11",
   "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.11"
   },
   "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",