docs: document Application / Projection / Artifact IR boundaries (#592 step 2)

website/docs/en/guide/_meta.json

@@ -4,6 +4,11 @@
     "name": "start",
     "label": "Start"
   },
+  {
+    "type": "dir-section-header",
+    "name": "concepts",
+    "label": "Concepts"
+  },
   {
     "type": "dir-section-header",
     "name": "authoring",

website/docs/en/guide/authoring/hooks.mdx

@@ -415,3 +415,5 @@ playground with the raw stdout, stderr, and outcome for each run.
 
 - [MCP servers and Apps](./mcp.mdx) — the other executable surface.
 - [Scripts and assets](./scripts-assets.mdx) — code a hook or Skill can call.
+- [Compiler architecture](../concepts/architecture.mdx) — how event routes,
+  config hooks, and host wrappers sit in the compiler pipeline.

website/docs/en/guide/authoring/index.mdx

@@ -188,3 +188,7 @@ and the runtime validates with the real zod object. How a reference is resolved,
 - [MCP servers and Apps](./mcp.mdx) — generated route servers, handwritten stdio entries, and browser Apps.
 - [Scripts and assets](./scripts-assets.mdx) — artifact scripts and static files.
 - [Package entries](./package-entries.mdx) — `bin`, `lib`, the routed CLI, and the bundler escape hatch.
+
+How one route becomes MCP, CLI, and hooks — and what the compiler still
+duplicates today — is in
+[Compiler architecture](../concepts/architecture.mdx).

website/docs/en/guide/authoring/mcp.mdx

@@ -1035,3 +1035,5 @@ loopback and is never exposed beyond the local machine.
 
 - [Scripts and assets](./scripts-assets.mdx) — the non-protocol executables in an artifact.
 - [Package entries](./package-entries.mdx) — `bin`, `lib`, and the routed CLI.
+- [Compiler architecture](../concepts/architecture.mdx) — how a generated
+  route sits in the application graph, a host projection, and the artifact.

website/docs/en/guide/concepts/_meta.json

@@ -0,0 +1 @@
+["architecture"]

website/docs/en/guide/start/index.mdx

@@ -85,6 +85,7 @@ than the harness produced is `inconclusive` rather than silently passing.
 - [Installation](./installation.mdx) — install the preview tarballs that CI publishes today.
 - [Quick start](./quick-start.mdx) — scaffold a project, or write the config by hand.
 - [Project structure](./project-structure.mdx) — the conventional `src/` roots and the output layout.
+- [Compiler architecture](../concepts/architecture.mdx) — how one route becomes MCP, CLI, and hooks.
 - [Authoring](../authoring/index.mdx) — the configuration model and every authorable surface.
 
 The repository documents the same contracts in more depth:

website/docs/en/guide/start/project-structure.mdx

@@ -182,6 +182,8 @@ export default defineConfig({
 
 ## Next steps
 
+- [Compiler architecture](../concepts/architecture.mdx) — how these roots
+  become a route graph, host projections, and one composite artifact.
 - [Configuration model](../authoring/index.mdx) — the full config surface.
 - [Skills](../authoring/skills.mdx), [Hooks](../authoring/hooks.mdx),
   [MCP servers and Apps](../authoring/mcp.mdx) — one page per surface.

website/docs/en/reference/targets-artifacts.mdx

@@ -134,8 +134,10 @@ inventory checks the same paths (`AB7010`).
 
 ## agent-bundle.manifest.json
 
-One manifest is emitted per root and is the input to every later integrity check —
-`validate --artifact`, `prepack`, `doctor --from`, and the packed and installed-host proof levels.
+One manifest is emitted per root and is the input to later integrity checks —
+`validate --artifact`, `prepack`, and the packed and installed-host proof
+levels. `doctor --from` and `install --from` identify the root from the
+host `plugin.json` under `--from`; they do not parse this file.
 
 | Field | Contents |
 | --- | --- |
@@ -182,6 +184,8 @@ schema pin, and emitted files and source inputs.
 
 ## Next
 
+- [Compiler architecture](../guide/concepts/architecture.mdx) — the three
+  compiler layers and which production readers consume each manifest field.
 - [Artifact validation](../guide/distribution/validation.mdx) — the checks that read this manifest.
 - [Host installation](../guide/distribution/installation.mdx) — installing the root into each host.
 - [Runtime environment](./runtime-environment.mdx) — what the emitted executables assume at run time.

website/docs/zh/guide/_meta.json

@@ -4,6 +4,11 @@
     "name": "start",
     "label": "开始"
   },
+  {
+    "type": "dir-section-header",
+    "name": "concepts",
+    "label": "概念"
+  },
   {
     "type": "dir-section-header",
     "name": "authoring",

website/docs/zh/guide/authoring/hooks.mdx

@@ -357,3 +357,5 @@ targets、tools、timeout 与 args，因此声明的任何改动都会得到新
 
 - [MCP 服务器与 MCP App](./mcp.mdx) —— 另一种可执行表面。
 - [脚本与资源](./scripts-assets.mdx) —— 钩子或 Skill 可以调用的代码。
+- [编译器架构](../concepts/architecture.mdx) —— 事件路由、配置钩子与宿主包装层
+  在编译管线中的位置。

website/docs/zh/guide/authoring/index.mdx

@@ -171,3 +171,6 @@ schema 全部内联的路由图保持其已有的 digest。
 - [MCP 服务器与 MCP App](./mcp.mdx) —— 生成式路由服务器、手写 stdio 入口与浏览器 App。
 - [脚本与资源](./scripts-assets.mdx) —— 产物脚本与静态文件。
 - [包入口](./package-entries.mdx) —— `bin`、`lib`、路由式 CLI 与打包器逃生舱。
+
+一条路由如何同时变成 MCP、CLI 与钩子——以及编译器今天仍在哪些地方重复——见
+[编译器架构](../concepts/architecture.mdx)。

website/docs/zh/guide/authoring/mcp.mdx

@@ -918,3 +918,5 @@ HTTP 端点。`--target` 默认为 `portable`，`--url` 可覆盖发现过程。
 
 - [脚本与资源](./scripts-assets.mdx) —— 产物中非协议类的可执行文件。
 - [包入口](./package-entries.mdx) —— `bin`、`lib` 与路由式 CLI。
+- [编译器架构](../concepts/architecture.mdx) —— 生成式路由如何进入应用图、
+  宿主投影与产物。

website/docs/zh/guide/concepts/_meta.json

@@ -0,0 +1 @@
+["architecture"]