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/api/harness/agents.md

@@ -16,7 +16,7 @@ setFactory(factory: AgentFactory): () => void
 
 Register the agent-creation factory (the loop calls this on construction, effect-scoped). Throws if a factory is already registered. Returns the disposer; on dispose the factory slot is cleared.
 
-- `factory` — the loop-owned factory {@link create}/{@link resume} delegate to.
+- `factory` — the loop-owned factory `create`/`resume` delegate to.
 
 **Returns** the disposer that clears the factory slot.
 

website/zh-CN/api/harness/bash.md

@@ -23,7 +23,7 @@ Resolve a caller's BashExecRequest into a fully-specified BashExecSpec, applying
 
 - `request` — the caller's request; omitted fields get this implementation's defaults, capped fields are clamped.
 
-**Returns** the fully-specified spec to hand to {@link run}/{@link start}.
+**Returns** the fully-specified spec to hand to `run`/`start`.
 
 [Source](https://github.com/deepseek-harness/deepseek-harness/blob/master/packages/bash/bash/src/index.ts#L84)
 
@@ -35,7 +35,7 @@ abstract run(spec: BashExecSpec): Promise<BashRunResult>
 
 Run a command in the foreground; resolves when it finishes.
 
-- `spec` — a resolved spec from {@link resolve}, never a raw request.
+- `spec` — a resolved spec from `resolve`, never a raw request.
 
 **Returns** the outcome; nonzero exits, timeout kills, and abort kills resolve with a descriptive result rather than reject.
 
@@ -49,9 +49,9 @@ abstract start(spec: BashExecSpec): BashTask
 
 Start a background task and return its handle immediately.
 
-- `spec` — a resolved spec from {@link resolve}, never a raw request.
+- `spec` — a resolved spec from `resolve`, never a raw request.
 
-**Returns** the live task handle; completion fires {@link onTaskDone}.
+**Returns** the live task handle; completion fires `onTaskDone`.
 
 [Source](https://github.com/deepseek-harness/deepseek-harness/blob/master/packages/bash/bash/src/index.ts#L99)
 

website/zh-CN/api/harness/code-runtime.md

@@ -13,6 +13,26 @@ Semantics every implementation must honor:
 
 [Source](https://github.com/deepseek-harness/deepseek-harness/blob/master/packages/code-runtime/code-runtime/src/index.ts#L59)
 
+### ctx.codeRuntime.language
+
+```ts website-api
+abstract readonly language: string
+```
+
+The source language run expects `program` to be written in, as a lowercase identifier. Informational, not gating — a consumer that generates language-specific presentation (typed SDK stubs, usage instructions) switches on it and fails loud on a language it cannot present. Well-known value: `'typescript'`.
+
+[Source](https://github.com/deepseek-harness/deepseek-harness/blob/master/packages/code-runtime/code-runtime/src/index.ts#L67)
+
+### ctx.codeRuntime.isolation
+
+```ts website-api
+abstract readonly isolation: string
+```
+
+The execution substrate, as a lowercase identifier. Informational, not gating — a descriptor so deployments and diagnostics can tell backends apart, not a security claim. Well-known values: `'worker-thread'`, `'process'`, `'container'`.
+
+[Source](https://github.com/deepseek-harness/deepseek-harness/blob/master/packages/code-runtime/code-runtime/src/index.ts#L75)
+
 ### ctx.codeRuntime.run(request)
 
 ```ts website-api

website/zh-CN/api/harness/events.md

@@ -381,7 +381,7 @@ A subagent run started — emitted after the provider is resolved and its capabi
 Waterfall around prompt assembly — mutate or extend the PromptAssembly (sections + tools + variables) before it is rendered. Bound to the SystemPrompt service; call `next()` to delegate.
 
 - `assembly` — the assembly built from the registered sections, tool providers, and variable providers; listeners may mutate it or return a replacement.
-- `context` — the per-assembly {@link AssembleContext} the caller passed to {@link SystemPrompt.assemble} (e.g. which agent the prompt is for), so a listener can filter or extend per agent.
+- `context` — the per-assembly `AssembleContext` the caller passed to `SystemPrompt.assemble` (e.g. which agent the prompt is for), so a listener can filter or extend per agent.
 
 [Source](https://github.com/deepseek-harness/deepseek-harness/blob/master/packages/core/system-prompt/src/index.ts#L38)
 
@@ -497,7 +497,7 @@ One `agent()` call started a child run. Paired with Events['workflow/agent-end']
 A workflow run settled (any stop reason). Fired when WorkflowRun.result resolves. Paired with Events['workflow/start'].
 
 - `info` — the run's identity snapshot.
-- `result` — the outcome data (stop reason, error, agent count) — deliberately WITHOUT the result value (see {@link WorkflowResultInfo}).
+- `result` — the outcome data (stop reason, error, agent count) — deliberately WITHOUT the result value (see `WorkflowResultInfo`).
 
 [Source](https://github.com/deepseek-harness/deepseek-harness/blob/master/packages/workflow/workflow/src/index.ts#L106)
 

website/zh-CN/api/harness/fs.md

@@ -72,7 +72,7 @@ Stream the whole regular text file as decoded text chunks (same text semantics a
 - `target` — the resolved target to read.
 - `signal` — aborts the stream, including between chunks.
 
-**Returns** the chunk iterable, decoded and validated like {@link readText}.
+**Returns** the chunk iterable, decoded and validated like `readText`.
 
 [Source](https://github.com/deepseek-harness/deepseek-harness/blob/master/packages/fs/fs/src/index.ts#L221)
 

website/zh-CN/api/harness/sessions.md

@@ -49,7 +49,7 @@ enter(session: Session): () => void
 Enter a prepared session into the store: wire `onAppend` → `session/event` and add it to the store. Returns the DETACH disposer (`onAppend = undefined` + store removal). Does NOT emit `session/created` — the caller yields this disposer inside its effect and THEN calls announce, so a throwing `session/created` listener rolls the attach back instead of leaking it.
 Re-checks the id for a duplicate: `prepare` and `enter` are public cross-package primitives and a caller may interleave arbitrary work (or another create) between them, so a stale prepared session must NOT overwrite a live store entry of the same id — its detach disposer would later delete the REAL session. The create convenience and the agent factory call the two back-to-back so they never trip this, but the public seam cannot assume that.
 
-- `session` — a {@link prepare}d session not yet in the store.
+- `session` — a `prepare`d session not yet in the store.
 
 **Returns** the detach disposer (`onAppend = undefined` + store removal).
 

website/zh-CN/api/harness/system-prompt.md

@@ -30,7 +30,7 @@ tools(provider: () => ToolSchema[]): () => void
 
 Contribute a tool-schema provider that is evaluated at each assembly call (so it can reflect the live registry state). The provider is removed when the calling fiber is disposed. A provider must not return a schema named TOOL_ORDER_REST; that name is reserved for Config.toolOrder's rest entry and rejects the assembly. Emits `system-prompt/change`.
 
-- `provider` — evaluated at every {@link assemble} for fresh schemas.
+- `provider` — evaluated at every `assemble` for fresh schemas.
 
 **Returns** the disposer that removes the provider.
 
@@ -45,7 +45,7 @@ variable(name: string, provider: (context: AssembleContext) => string | undefine
 Contribute a named prompt variable, referenced from section text as `{{name}}`. The provider is evaluated at each assembly with that assembly's AssembleContext; returning `undefined` means "no value for this assembly" (a section referencing it then fails to render — a deployment must not claim facts it does not have). Throws on a name that does not match `[a-z][a-z0-9_]*` (it could never be referenced) or is already registered. Removed when the calling fiber is disposed; emits `system-prompt/change` on register/unregister.
 
 - `name` — the reference name (matches `[a-z][a-z0-9_]*`).
-- `provider` — evaluated at every {@link assemble} for the value.
+- `provider` — evaluated at every `assemble` for the value.
 
 **Returns** the disposer that removes the variable.
 
@@ -59,7 +59,7 @@ async assemble(context: AssembleContext = {}): Promise<PromptAssembly>
 
 Assemble the current prompt for one caller: section texts are resolved against `context` and sorted by order, tools collected from all providers and put in the canonical model-facing order (Config.toolOrder, or lexicographic name order when unconfigured — provider registration order is a plugin-load artifact and never reaches the assembly; a configured order naming a tool no provider contributed rejects the assembly), and every registered variable resolved against `context` into `assembly.variables`. Tool schemas are deep-cloned because adapters and request waterfalls may mutate schema objects. Runs through the `system-prompt/assemble` waterfall, giving listeners the opportunity to mutate or replace the assembly before it reaches the model — like the sections' `order` sort, tool canonicalization happens on the initial assembly, and a listener owns the determinism of whatever it emits. Await the result before reading the assembly values — waterfall listeners may be async. Interpolation happens later, in renderPrompt.
 
-- `context` — what this assembly is for (defaults to an empty context; see {@link AssembleContext}).
+- `context` — what this assembly is for (defaults to an empty context; see `AssembleContext`).
 
 **Returns** the assembly after the waterfall has run.