@c4a/context-cli 0.6.0-alpha.1 → 0.6.0-alpha.6

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@c4a/context-cli",
-  "version": "0.6.0-alpha.1",
+  "version": "0.6.0-alpha.6",
   "type": "module",
   "bin": {
     "context": "./cli.js"

package/plugin/skills/skill-source-scope/SKILL.md

@@ -210,15 +210,19 @@ For local Markdown/MDX document sources, after the user confirms the boundary, r
 context source add file <name> --local <file-or-folder>
 ```
 
-Default file capture handles Markdown. For MDX documentation sites that use
-`_meta.json` route metadata, declare
+Default file capture handles Markdown. If `context source add file`,
+`context source inspect`, `context status`, or capture output reports that the
+source looks like an MDX documentation site, stop at the source boundary gate
+and ask the user to confirm that interpretation before changing `src/index.ts`.
+For MDX documentation sites that use `_meta.json` route metadata, declare
 `captureFile({ source: source("<name>"), processor: mdxJsonDocs() })` in
-`src/index.ts`; included `_meta.json` files are route metadata, not body
-evidence. Use `--include` only when the approved boundary is narrower than the
-folder. Then explain that the next operation reads the approved document files
-and writes a committed snapshot under `sources/file/<name>/`. After the user
-confirms read permission, summarize the `src/index.ts` change or show an
-equivalent diff summary, and run the capture phase.
+`src/index.ts`; included `_meta.json` files are route metadata, and the CLI
+generates `__context_route_metadata.md` as mechanical route evidence. Use
+`--include` only when the approved boundary is narrower than the folder. Then
+explain that the next operation reads the approved document files and writes a
+committed snapshot under `sources/file/<name>/`. After the user confirms read
+permission, summarize the `src/index.ts` change or show an equivalent diff
+summary, and run the capture phase.
 Apply [references/capture-source.md](references/capture-source.md) for route
 selection, dependency recovery, output handling, and final reporting, using the
 current capture phase command returned by `context status`.

package/plugin/skills/skill-source-scope/references/capture-source.md

@@ -55,12 +55,21 @@ Before choosing a local Markdown capture route, honor the surrounding task conte
   register one file source with the user-confirmed source name and boundary:
   `context source add file <name> --local <file-or-folder>`. For an explicit
   batch inside a broader folder, preserve the user's include list on source
-  registration. Default file capture handles `.md`. For MDX documentation sites
-  that use `_meta.json`, declare `mdxJsonDocs()` on `captureFile` in
-  `src/index.ts`; keep `_meta.json` only when it is route metadata for the
-  selected document folder. It is captured as metadata, not body evidence.
-  Declare `captureFile({ source: source("<name>") })`, then run
-  `context run capture:file:<name> --format json`.
+  registration. Default file capture handles `.md`. If the CLI reports
+  document-site files such as `.mdx`, `_meta.json`, sidebars, or docs config,
+  stop and confirm whether the selected boundary is a documentation site before
+  changing capture configuration. For MDX documentation sites that use
+  `_meta.json`, declare `mdxJsonDocs()` on `captureFile` in `src/index.ts`;
+  keep `_meta.json` only when it is route metadata for the selected document
+  folder. The CLI captures it as metadata and generates
+  `__context_route_metadata.md` as mechanical route evidence; it also extracts
+  static MDX component props/children into `__context_mdx_component_text.md`
+  when components carry user-facing text. Declare
+  `captureFile({ source: source("<name>"), processor: mdxJsonDocs() })`, then
+  run `context run capture:file:<name> --format json`. If the selected MDX page
+  is empty or only mounts runtime-rendered content, tell the user that capture
+  found a document-site shell and ask for the rendered-site or data-source
+  boundary instead of inventing body text.
 - A Lark/Feishu URL, doc token, or wiki token → register one Lark source:
   `context source add lark <name> --url <url>` or the matching token flag.
   Declare `captureLark({ source: source("<name>") })`, then run

package/plugins/VERSION

@@ -1 +1 @@
-0.6.0-alpha.1
+0.6.0-alpha.6

package/plugins/claude/.claude-plugin/plugin.json

@@ -1,7 +1,7 @@
 {
   "name": "context",
   "description": "Maintain a project-local knowledge workspace through init and next-step agent guidance.",
-  "version": "0.6.0-alpha.1",
+  "version": "0.6.0-alpha.6",
   "author": {
     "name": "c4a"
   },

package/plugins/claude/skills/skill-source-scope/SKILL.md

@@ -210,15 +210,19 @@ For local Markdown/MDX document sources, after the user confirms the boundary, r
 context source add file <name> --local <file-or-folder>
 ```
 
-Default file capture handles Markdown. For MDX documentation sites that use
-`_meta.json` route metadata, declare
+Default file capture handles Markdown. If `context source add file`,
+`context source inspect`, `context status`, or capture output reports that the
+source looks like an MDX documentation site, stop at the source boundary gate
+and ask the user to confirm that interpretation before changing `src/index.ts`.
+For MDX documentation sites that use `_meta.json` route metadata, declare
 `captureFile({ source: source("<name>"), processor: mdxJsonDocs() })` in
-`src/index.ts`; included `_meta.json` files are route metadata, not body
-evidence. Use `--include` only when the approved boundary is narrower than the
-folder. Then explain that the next operation reads the approved document files
-and writes a committed snapshot under `sources/file/<name>/`. After the user
-confirms read permission, summarize the `src/index.ts` change or show an
-equivalent diff summary, and run the capture phase.
+`src/index.ts`; included `_meta.json` files are route metadata, and the CLI
+generates `__context_route_metadata.md` as mechanical route evidence. Use
+`--include` only when the approved boundary is narrower than the folder. Then
+explain that the next operation reads the approved document files and writes a
+committed snapshot under `sources/file/<name>/`. After the user confirms read
+permission, summarize the `src/index.ts` change or show an equivalent diff
+summary, and run the capture phase.
 Apply [references/capture-source.md](references/capture-source.md) for route
 selection, dependency recovery, output handling, and final reporting, using the
 current capture phase command returned by `context status`.

package/plugins/claude/skills/skill-source-scope/references/capture-source.md

@@ -55,12 +55,21 @@ Before choosing a local Markdown capture route, honor the surrounding task conte
   register one file source with the user-confirmed source name and boundary:
   `context source add file <name> --local <file-or-folder>`. For an explicit
   batch inside a broader folder, preserve the user's include list on source
-  registration. Default file capture handles `.md`. For MDX documentation sites
-  that use `_meta.json`, declare `mdxJsonDocs()` on `captureFile` in
-  `src/index.ts`; keep `_meta.json` only when it is route metadata for the
-  selected document folder. It is captured as metadata, not body evidence.
-  Declare `captureFile({ source: source("<name>") })`, then run
-  `context run capture:file:<name> --format json`.
+  registration. Default file capture handles `.md`. If the CLI reports
+  document-site files such as `.mdx`, `_meta.json`, sidebars, or docs config,
+  stop and confirm whether the selected boundary is a documentation site before
+  changing capture configuration. For MDX documentation sites that use
+  `_meta.json`, declare `mdxJsonDocs()` on `captureFile` in `src/index.ts`;
+  keep `_meta.json` only when it is route metadata for the selected document
+  folder. The CLI captures it as metadata and generates
+  `__context_route_metadata.md` as mechanical route evidence; it also extracts
+  static MDX component props/children into `__context_mdx_component_text.md`
+  when components carry user-facing text. Declare
+  `captureFile({ source: source("<name>"), processor: mdxJsonDocs() })`, then
+  run `context run capture:file:<name> --format json`. If the selected MDX page
+  is empty or only mounts runtime-rendered content, tell the user that capture
+  found a document-site shell and ask for the rendered-site or data-source
+  boundary instead of inventing body text.
 - A Lark/Feishu URL, doc token, or wiki token → register one Lark source:
   `context source add lark <name> --url <url>` or the matching token flag.
   Declare `captureLark({ source: source("<name>") })`, then run

package/plugins/codex/.codex-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "context",
-  "version": "0.6.0-alpha.1",
+  "version": "0.6.0-alpha.6",
   "description": "Maintain a project-local knowledge workspace through init and next-step agent guidance.",
   "author": {
     "name": "c4a"
@@ -18,7 +18,7 @@
   "skills": "./skills/",
   "interface": {
     "displayName": "C4A Context",
-    "shortDescription": "Initialize and advance a local, source-linked project knowledge workspace.\nv0.6.0-alpha.1",
+    "shortDescription": "Initialize and advance a local, source-linked project knowledge workspace.\nv0.6.0-alpha.6",
     "longDescription": "Create a Context workspace and use agent-guided next steps to register sources, run extraction, review candidates, build package outputs, and verify health without silently mutating source repositories.",
     "developerName": "c4a",
     "category": "Productivity",

package/plugins/codex/skills/continue/references/internal-procedures/skill-source-scope/references/capture-source.md

@@ -55,12 +55,21 @@ Before choosing a local Markdown capture route, honor the surrounding task conte
   register one file source with the user-confirmed source name and boundary:
   `context source add file <name> --local <file-or-folder>`. For an explicit
   batch inside a broader folder, preserve the user's include list on source
-  registration. Default file capture handles `.md`. For MDX documentation sites
-  that use `_meta.json`, declare `mdxJsonDocs()` on `captureFile` in
-  `src/index.ts`; keep `_meta.json` only when it is route metadata for the
-  selected document folder. It is captured as metadata, not body evidence.
-  Declare `captureFile({ source: source("<name>") })`, then run
-  `context run capture:file:<name> --format json`.
+  registration. Default file capture handles `.md`. If the CLI reports
+  document-site files such as `.mdx`, `_meta.json`, sidebars, or docs config,
+  stop and confirm whether the selected boundary is a documentation site before
+  changing capture configuration. For MDX documentation sites that use
+  `_meta.json`, declare `mdxJsonDocs()` on `captureFile` in `src/index.ts`;
+  keep `_meta.json` only when it is route metadata for the selected document
+  folder. The CLI captures it as metadata and generates
+  `__context_route_metadata.md` as mechanical route evidence; it also extracts
+  static MDX component props/children into `__context_mdx_component_text.md`
+  when components carry user-facing text. Declare
+  `captureFile({ source: source("<name>"), processor: mdxJsonDocs() })`, then
+  run `context run capture:file:<name> --format json`. If the selected MDX page
+  is empty or only mounts runtime-rendered content, tell the user that capture
+  found a document-site shell and ask for the rendered-site or data-source
+  boundary instead of inventing body text.
 - A Lark/Feishu URL, doc token, or wiki token → register one Lark source:
   `context source add lark <name> --url <url>` or the matching token flag.
   Declare `captureLark({ source: source("<name>") })`, then run

package/plugins/codex/skills/continue/references/internal-procedures/skill-source-scope.md

@@ -210,15 +210,19 @@ For local Markdown/MDX document sources, after the user confirms the boundary, r
 context source add file <name> --local <file-or-folder>
 ```
 
-Default file capture handles Markdown. For MDX documentation sites that use
-`_meta.json` route metadata, declare
+Default file capture handles Markdown. If `context source add file`,
+`context source inspect`, `context status`, or capture output reports that the
+source looks like an MDX documentation site, stop at the source boundary gate
+and ask the user to confirm that interpretation before changing `src/index.ts`.
+For MDX documentation sites that use `_meta.json` route metadata, declare
 `captureFile({ source: source("<name>"), processor: mdxJsonDocs() })` in
-`src/index.ts`; included `_meta.json` files are route metadata, not body
-evidence. Use `--include` only when the approved boundary is narrower than the
-folder. Then explain that the next operation reads the approved document files
-and writes a committed snapshot under `sources/file/<name>/`. After the user
-confirms read permission, summarize the `src/index.ts` change or show an
-equivalent diff summary, and run the capture phase.
+`src/index.ts`; included `_meta.json` files are route metadata, and the CLI
+generates `__context_route_metadata.md` as mechanical route evidence. Use
+`--include` only when the approved boundary is narrower than the folder. Then
+explain that the next operation reads the approved document files and writes a
+committed snapshot under `sources/file/<name>/`. After the user confirms read
+permission, summarize the `src/index.ts` change or show an equivalent diff
+summary, and run the capture phase.
 Apply [skill-source-scope/references/capture-source.md](skill-source-scope/references/capture-source.md) for route
 selection, dependency recovery, output handling, and final reporting, using the
 current capture phase command returned by `context status`.

package/plugins/codex/skills/init/references/internal-procedures/skill-source-scope/references/capture-source.md

@@ -55,12 +55,21 @@ Before choosing a local Markdown capture route, honor the surrounding task conte
   register one file source with the user-confirmed source name and boundary:
   `context source add file <name> --local <file-or-folder>`. For an explicit
   batch inside a broader folder, preserve the user's include list on source
-  registration. Default file capture handles `.md`. For MDX documentation sites
-  that use `_meta.json`, declare `mdxJsonDocs()` on `captureFile` in
-  `src/index.ts`; keep `_meta.json` only when it is route metadata for the
-  selected document folder. It is captured as metadata, not body evidence.
-  Declare `captureFile({ source: source("<name>") })`, then run
-  `context run capture:file:<name> --format json`.
+  registration. Default file capture handles `.md`. If the CLI reports
+  document-site files such as `.mdx`, `_meta.json`, sidebars, or docs config,
+  stop and confirm whether the selected boundary is a documentation site before
+  changing capture configuration. For MDX documentation sites that use
+  `_meta.json`, declare `mdxJsonDocs()` on `captureFile` in `src/index.ts`;
+  keep `_meta.json` only when it is route metadata for the selected document
+  folder. The CLI captures it as metadata and generates
+  `__context_route_metadata.md` as mechanical route evidence; it also extracts
+  static MDX component props/children into `__context_mdx_component_text.md`
+  when components carry user-facing text. Declare
+  `captureFile({ source: source("<name>"), processor: mdxJsonDocs() })`, then
+  run `context run capture:file:<name> --format json`. If the selected MDX page
+  is empty or only mounts runtime-rendered content, tell the user that capture
+  found a document-site shell and ask for the rendered-site or data-source
+  boundary instead of inventing body text.
 - A Lark/Feishu URL, doc token, or wiki token → register one Lark source:
   `context source add lark <name> --url <url>` or the matching token flag.
   Declare `captureLark({ source: source("<name>") })`, then run

package/plugins/codex/skills/init/references/internal-procedures/skill-source-scope.md

@@ -210,15 +210,19 @@ For local Markdown/MDX document sources, after the user confirms the boundary, r
 context source add file <name> --local <file-or-folder>
 ```
 
-Default file capture handles Markdown. For MDX documentation sites that use
-`_meta.json` route metadata, declare
+Default file capture handles Markdown. If `context source add file`,
+`context source inspect`, `context status`, or capture output reports that the
+source looks like an MDX documentation site, stop at the source boundary gate
+and ask the user to confirm that interpretation before changing `src/index.ts`.
+For MDX documentation sites that use `_meta.json` route metadata, declare
 `captureFile({ source: source("<name>"), processor: mdxJsonDocs() })` in
-`src/index.ts`; included `_meta.json` files are route metadata, not body
-evidence. Use `--include` only when the approved boundary is narrower than the
-folder. Then explain that the next operation reads the approved document files
-and writes a committed snapshot under `sources/file/<name>/`. After the user
-confirms read permission, summarize the `src/index.ts` change or show an
-equivalent diff summary, and run the capture phase.
+`src/index.ts`; included `_meta.json` files are route metadata, and the CLI
+generates `__context_route_metadata.md` as mechanical route evidence. Use
+`--include` only when the approved boundary is narrower than the folder. Then
+explain that the next operation reads the approved document files and writes a
+committed snapshot under `sources/file/<name>/`. After the user confirms read
+permission, summarize the `src/index.ts` change or show an equivalent diff
+summary, and run the capture phase.
 Apply [skill-source-scope/references/capture-source.md](skill-source-scope/references/capture-source.md) for route
 selection, dependency recovery, output handling, and final reporting, using the
 current capture phase command returned by `context status`.

package/plugins/cursor/.cursor-plugin/plugin.json

@@ -1,7 +1,7 @@
 {
   "name": "context",
   "displayName": "C4A Context",
-  "version": "0.6.0-alpha.1",
+  "version": "0.6.0-alpha.6",
   "description": "Maintain a project-local knowledge workspace through init and next-step agent guidance.",
   "author": {
     "name": "Context4AI",

package/plugins/cursor/skills/skill-source-scope/SKILL.md

@@ -210,15 +210,19 @@ For local Markdown/MDX document sources, after the user confirms the boundary, r
 context source add file <name> --local <file-or-folder>
 ```
 
-Default file capture handles Markdown. For MDX documentation sites that use
-`_meta.json` route metadata, declare
+Default file capture handles Markdown. If `context source add file`,
+`context source inspect`, `context status`, or capture output reports that the
+source looks like an MDX documentation site, stop at the source boundary gate
+and ask the user to confirm that interpretation before changing `src/index.ts`.
+For MDX documentation sites that use `_meta.json` route metadata, declare
 `captureFile({ source: source("<name>"), processor: mdxJsonDocs() })` in
-`src/index.ts`; included `_meta.json` files are route metadata, not body
-evidence. Use `--include` only when the approved boundary is narrower than the
-folder. Then explain that the next operation reads the approved document files
-and writes a committed snapshot under `sources/file/<name>/`. After the user
-confirms read permission, summarize the `src/index.ts` change or show an
-equivalent diff summary, and run the capture phase.
+`src/index.ts`; included `_meta.json` files are route metadata, and the CLI
+generates `__context_route_metadata.md` as mechanical route evidence. Use
+`--include` only when the approved boundary is narrower than the folder. Then
+explain that the next operation reads the approved document files and writes a
+committed snapshot under `sources/file/<name>/`. After the user confirms read
+permission, summarize the `src/index.ts` change or show an equivalent diff
+summary, and run the capture phase.
 Apply [references/capture-source.md](references/capture-source.md) for route
 selection, dependency recovery, output handling, and final reporting, using the
 current capture phase command returned by `context status`.

package/plugins/cursor/skills/skill-source-scope/references/capture-source.md

@@ -55,12 +55,21 @@ Before choosing a local Markdown capture route, honor the surrounding task conte
   register one file source with the user-confirmed source name and boundary:
   `context source add file <name> --local <file-or-folder>`. For an explicit
   batch inside a broader folder, preserve the user's include list on source
-  registration. Default file capture handles `.md`. For MDX documentation sites
-  that use `_meta.json`, declare `mdxJsonDocs()` on `captureFile` in
-  `src/index.ts`; keep `_meta.json` only when it is route metadata for the
-  selected document folder. It is captured as metadata, not body evidence.
-  Declare `captureFile({ source: source("<name>") })`, then run
-  `context run capture:file:<name> --format json`.
+  registration. Default file capture handles `.md`. If the CLI reports
+  document-site files such as `.mdx`, `_meta.json`, sidebars, or docs config,
+  stop and confirm whether the selected boundary is a documentation site before
+  changing capture configuration. For MDX documentation sites that use
+  `_meta.json`, declare `mdxJsonDocs()` on `captureFile` in `src/index.ts`;
+  keep `_meta.json` only when it is route metadata for the selected document
+  folder. The CLI captures it as metadata and generates
+  `__context_route_metadata.md` as mechanical route evidence; it also extracts
+  static MDX component props/children into `__context_mdx_component_text.md`
+  when components carry user-facing text. Declare
+  `captureFile({ source: source("<name>"), processor: mdxJsonDocs() })`, then
+  run `context run capture:file:<name> --format json`. If the selected MDX page
+  is empty or only mounts runtime-rendered content, tell the user that capture
+  found a document-site shell and ask for the rendered-site or data-source
+  boundary instead of inventing body text.
 - A Lark/Feishu URL, doc token, or wiki token → register one Lark source:
   `context source add lark <name> --url <url>` or the matching token flag.
   Declare `captureLark({ source: source("<name>") })`, then run

package/plugins/skills/context-continue/references/internal-procedures/skill-source-scope/references/capture-source.md

@@ -55,12 +55,21 @@ Before choosing a local Markdown capture route, honor the surrounding task conte
   register one file source with the user-confirmed source name and boundary:
   `context source add file <name> --local <file-or-folder>`. For an explicit
   batch inside a broader folder, preserve the user's include list on source
-  registration. Default file capture handles `.md`. For MDX documentation sites
-  that use `_meta.json`, declare `mdxJsonDocs()` on `captureFile` in
-  `src/index.ts`; keep `_meta.json` only when it is route metadata for the
-  selected document folder. It is captured as metadata, not body evidence.
-  Declare `captureFile({ source: source("<name>") })`, then run
-  `context run capture:file:<name> --format json`.
+  registration. Default file capture handles `.md`. If the CLI reports
+  document-site files such as `.mdx`, `_meta.json`, sidebars, or docs config,
+  stop and confirm whether the selected boundary is a documentation site before
+  changing capture configuration. For MDX documentation sites that use
+  `_meta.json`, declare `mdxJsonDocs()` on `captureFile` in `src/index.ts`;
+  keep `_meta.json` only when it is route metadata for the selected document
+  folder. The CLI captures it as metadata and generates
+  `__context_route_metadata.md` as mechanical route evidence; it also extracts
+  static MDX component props/children into `__context_mdx_component_text.md`
+  when components carry user-facing text. Declare
+  `captureFile({ source: source("<name>"), processor: mdxJsonDocs() })`, then
+  run `context run capture:file:<name> --format json`. If the selected MDX page
+  is empty or only mounts runtime-rendered content, tell the user that capture
+  found a document-site shell and ask for the rendered-site or data-source
+  boundary instead of inventing body text.
 - A Lark/Feishu URL, doc token, or wiki token → register one Lark source:
   `context source add lark <name> --url <url>` or the matching token flag.
   Declare `captureLark({ source: source("<name>") })`, then run

package/plugins/skills/context-continue/references/internal-procedures/skill-source-scope.md

@@ -210,15 +210,19 @@ For local Markdown/MDX document sources, after the user confirms the boundary, r
 context source add file <name> --local <file-or-folder>
 ```
 
-Default file capture handles Markdown. For MDX documentation sites that use
-`_meta.json` route metadata, declare
+Default file capture handles Markdown. If `context source add file`,
+`context source inspect`, `context status`, or capture output reports that the
+source looks like an MDX documentation site, stop at the source boundary gate
+and ask the user to confirm that interpretation before changing `src/index.ts`.
+For MDX documentation sites that use `_meta.json` route metadata, declare
 `captureFile({ source: source("<name>"), processor: mdxJsonDocs() })` in
-`src/index.ts`; included `_meta.json` files are route metadata, not body
-evidence. Use `--include` only when the approved boundary is narrower than the
-folder. Then explain that the next operation reads the approved document files
-and writes a committed snapshot under `sources/file/<name>/`. After the user
-confirms read permission, summarize the `src/index.ts` change or show an
-equivalent diff summary, and run the capture phase.
+`src/index.ts`; included `_meta.json` files are route metadata, and the CLI
+generates `__context_route_metadata.md` as mechanical route evidence. Use
+`--include` only when the approved boundary is narrower than the folder. Then
+explain that the next operation reads the approved document files and writes a
+committed snapshot under `sources/file/<name>/`. After the user confirms read
+permission, summarize the `src/index.ts` change or show an equivalent diff
+summary, and run the capture phase.
 Apply [skill-source-scope/references/capture-source.md](skill-source-scope/references/capture-source.md) for route
 selection, dependency recovery, output handling, and final reporting, using the
 current capture phase command returned by `context status`.

package/plugins/skills/context-init/references/internal-procedures/skill-source-scope/references/capture-source.md

@@ -55,12 +55,21 @@ Before choosing a local Markdown capture route, honor the surrounding task conte
   register one file source with the user-confirmed source name and boundary:
   `context source add file <name> --local <file-or-folder>`. For an explicit
   batch inside a broader folder, preserve the user's include list on source
-  registration. Default file capture handles `.md`. For MDX documentation sites
-  that use `_meta.json`, declare `mdxJsonDocs()` on `captureFile` in
-  `src/index.ts`; keep `_meta.json` only when it is route metadata for the
-  selected document folder. It is captured as metadata, not body evidence.
-  Declare `captureFile({ source: source("<name>") })`, then run
-  `context run capture:file:<name> --format json`.
+  registration. Default file capture handles `.md`. If the CLI reports
+  document-site files such as `.mdx`, `_meta.json`, sidebars, or docs config,
+  stop and confirm whether the selected boundary is a documentation site before
+  changing capture configuration. For MDX documentation sites that use
+  `_meta.json`, declare `mdxJsonDocs()` on `captureFile` in `src/index.ts`;
+  keep `_meta.json` only when it is route metadata for the selected document
+  folder. The CLI captures it as metadata and generates
+  `__context_route_metadata.md` as mechanical route evidence; it also extracts
+  static MDX component props/children into `__context_mdx_component_text.md`
+  when components carry user-facing text. Declare
+  `captureFile({ source: source("<name>"), processor: mdxJsonDocs() })`, then
+  run `context run capture:file:<name> --format json`. If the selected MDX page
+  is empty or only mounts runtime-rendered content, tell the user that capture
+  found a document-site shell and ask for the rendered-site or data-source
+  boundary instead of inventing body text.
 - A Lark/Feishu URL, doc token, or wiki token → register one Lark source:
   `context source add lark <name> --url <url>` or the matching token flag.
   Declare `captureLark({ source: source("<name>") })`, then run

package/plugins/skills/context-init/references/internal-procedures/skill-source-scope.md

@@ -210,15 +210,19 @@ For local Markdown/MDX document sources, after the user confirms the boundary, r
 context source add file <name> --local <file-or-folder>
 ```
 
-Default file capture handles Markdown. For MDX documentation sites that use
-`_meta.json` route metadata, declare
+Default file capture handles Markdown. If `context source add file`,
+`context source inspect`, `context status`, or capture output reports that the
+source looks like an MDX documentation site, stop at the source boundary gate
+and ask the user to confirm that interpretation before changing `src/index.ts`.
+For MDX documentation sites that use `_meta.json` route metadata, declare
 `captureFile({ source: source("<name>"), processor: mdxJsonDocs() })` in
-`src/index.ts`; included `_meta.json` files are route metadata, not body
-evidence. Use `--include` only when the approved boundary is narrower than the
-folder. Then explain that the next operation reads the approved document files
-and writes a committed snapshot under `sources/file/<name>/`. After the user
-confirms read permission, summarize the `src/index.ts` change or show an
-equivalent diff summary, and run the capture phase.
+`src/index.ts`; included `_meta.json` files are route metadata, and the CLI
+generates `__context_route_metadata.md` as mechanical route evidence. Use
+`--include` only when the approved boundary is narrower than the folder. Then
+explain that the next operation reads the approved document files and writes a
+committed snapshot under `sources/file/<name>/`. After the user confirms read
+permission, summarize the `src/index.ts` change or show an equivalent diff
+summary, and run the capture phase.
 Apply [skill-source-scope/references/capture-source.md](skill-source-scope/references/capture-source.md) for route
 selection, dependency recovery, output handling, and final reporting, using the
 current capture phase command returned by `context status`.