website: fix nine review findings (generator coverage, loader facts, mode semantics)

Generator (all four structural gaps):
- harness service pages now render public properties/accessors, not just
  methods (ctx.codeRuntime.language/isolation were missing);
- the class page merges the same-named interface half, so ctx.root/baseUrl/
  events/logger/reflect/registry appear on Context (vendor root JSDoc gains
  prose alongside @experimental);
- Pick<…> heritage on a Context merge resolves to the picked class members,
  giving ctx.effect a documented signature on the Fiber page;
- {@link} tags normalize to code spans; merge sections get their own h2 so
  reflect members no longer nest under 'Static members'.

verify-website-yaml: reject the unloadable 'group:' pseudo-name (tree.import
only special-cases 'cordis:'; no builtin is registered here) and recurse into
@cordisjs/plugin-group nested entry lists instead.

Prose corrected against loader/cordis source: service.md isolation example
uses the real group plugin + group: true + the required isolate map;
config.md documents concurrent entry startup (Promise.all; order via inject)
and the real hmr defaults (root ['.'], base/ignored/debounce); events.md
fixes emit (synchronous, not parallel), bail (null/false also delegate), and
serial (stops at the first bail value).

website/zh-CN/guide/config.md

@@ -332,7 +332,12 @@ config:
 
 | 字段 | 类型 | 默认值 | 说明 |
 |------|------|--------|------|
-| `root` | string[] | **必填** | 监听文件变更的目录列表 |
+| `root` | string[] | `['.']` | 监听文件变更的目录列表 |
+| `base` | string | — | 解析 `root` 的基准目录（默认取配置文件所在目录） |
+| `ignored` | string[] | `['**/node_modules', '**/.*', 'cache', 'data']` | 忽略的 glob 列表 |
+| `debounce` | number | `100` | 变更合并窗口（毫秒） |
+
+其余字段透传给 chokidar（`Config` 继承 `ChokidarOptions`）。
 
 ::: tip
 hmr 仅用于开发环境。它需要 `node --expose-internals` 启动参数，`demo:*` 脚本已自动添加。
@@ -342,7 +347,9 @@ hmr 仅用于开发环境。它需要 `node --expose-internals` 启动参数，`
 
 ## 加载顺序
 
-`cordis.yml` 的顺序就是加载顺序。推荐：
+`cordis.yml` 的条目是**并发启动**的（loader 对全部条目 `Promise.all`），文件顺序不决定加载顺序。真正的先后关系由依赖协调：插件声明的 `inject` 服务就绪之前，插件不会启动；服务出现后自动继续。所以**不要依赖书写顺序传递时序**——需要"先有 A 再有 B"就让 B `inject` A 提供的服务。
+
+文件顺序只是给人读的。推荐按角色分组书写：
 
 1. **hmr** — 热替换（仅开发时需要）
 2. **LLM 适配器** — 模型后端