For AI agents: the complete documentation index is available at https://scriptedalchemy.github.io/agent-bundle/zh/llms.txt, the full documentation bundle is available at https://scriptedalchemy.github.io/agent-bundle/zh/llms-full.txt, and this page is available as Markdown at https://scriptedalchemy.github.io/agent-bundle/zh/api/types/test.AgentTestProofLevel.md.
agent-bundle
  • 简体中文

      • Type Alias: AgentTestProofLevel

      AgentTestProofLevel = "route-unit" | "mcp-in-memory" | "dev-epoch" | "cli-dispatch" | "script-dispatch" | "workbench-surface" | "packed-stdio" | "packed-deleted-source" | "browser-app" | "simulated" | "host-install"

      The proof level one harness helper supplies. The levels are deliberately separate and separately named: a pass at one is never a receipt for another, and every helper stamps the level it actually carried into its provenance and its failure text.

      • route-unit renders a route module through the real Agent renderer. No transport, no browser surface, no host artifact.
      • mcp-in-memory runs the real generated MCP server against a real MCP client over the SDK's in-memory transport pair. It proves the protocol contract — registration, schemas, content projection — and proves nothing about a process, stdout framing, or a packed artifact.
      • dev-epoch opens an epoch-pinned generated stdio entry through the Workbench session service and drives its real process. It proves the generated development artifact, not packed or native-host provenance.
      • cli-dispatch runs an argv vector through the routed CLI's own shell over the compiled command graph, in this process. It proves command resolution, argv projection, and exit codes, not a spawned binary.
      • script-dispatch runs one conventional src/scripts/* module through the contract its generated scripts/<name>.mjs executable carries: a rendered .tsx script through the rendered-script shell and its four output modes in this process, a plain .ts script as a Node child process of its own over the source module with the main envelope. It proves the script's behavior and output contract — process exit, streams, and signals included for a plain script — not the bundled artifact.
      • workbench-surface projects the compiled route graph the way the dev server serves it to the Workbench — route catalog, state, lifecycle fixtures, page availability — without a browser or a dev server. It proves what the Workbench would be given, not that the Workbench rendered it.
      • packed-stdio installs the packed release tarball into a clean consumer, spawns the generated stdio entry as a real process, and drives it with a real MCP client. This is the packed process-and-protocol evidence level.
      • packed-deleted-source carries the packed-stdio proof after project source and configuration have been removed and verified absent. It proves that the generated entry is self-contained; it does not prove native-host install or dispatch, or an install mode that copies the artifact elsewhere.
      • browser-app compiles MCP App HTML through the production Rsbuild profile and mounts it over the product bridge in a real browser page. It does not prove host embedding, a packed artifact, or Workbench behavior.
      • simulated stages an emitted bundle directly into an isolated host-shaped root and spawns its MCP command. It does not prove a host-owned install.
      • host-install installs a built bundle into an isolated real host home through the public install path and observes registration through the host's own CLI. It does not prove session behavior or packed provenance.