@kryptosai/mcp-observatory 1.32.0 → 1.33.0

package/docs/safety-index/artifacts/ref-tools-server.json

@@ -2,9 +2,9 @@
   "artifactType": "run",
   "schemaVersion": "1.0.0",
   "gate": "pass",
-  "runId": "run_2026-07-06T194951606Z_e657d5a4",
-  "createdAt": "2026-07-06T19:49:51.606Z",
-  "toolVersion": "0.28.0",
+  "runId": "run_2026-07-15T223322301Z_3fb8821d",
+  "createdAt": "2026-07-15T22:33:22.302Z",
+  "toolVersion": "1.32.1",
   "target": {
     "targetId": "ref-tools-server",
     "adapter": "local-process",
@@ -29,10 +29,10 @@
     "nodeVersion": "v22.22.1"
   },
   "summary": {
-    "total": 8,
+    "total": 9,
     "pass": 7,
     "fail": 0,
-    "partial": 0,
+    "partial": 1,
     "unsupported": 1,
     "flaky": 0,
     "skipped": 0,
@@ -43,7 +43,7 @@
       "id": "tools",
       "capability": "tools",
       "status": "pass",
-      "durationMs": 0.8886670000001686,
+      "durationMs": 1.3943750000016735,
       "message": "Advertised capability responded with the minimal expected shape (2 items).",
       "evidence": [
         {
@@ -92,7 +92,7 @@
       "id": "prompts",
       "capability": "prompts",
       "status": "pass",
-      "durationMs": 0.19312499999978172,
+      "durationMs": 0.23954200000116543,
       "message": "Advertised capability responded with the minimal expected shape (2 items).",
       "evidence": [
         {
@@ -115,7 +115,7 @@
       "id": "resources",
       "capability": "resources",
       "status": "unsupported",
-      "durationMs": 0.0022499999995488906,
+      "durationMs": 0.002917000001616543,
       "message": "Resources are not advertised by the target.",
       "evidence": [
         {
@@ -131,7 +131,7 @@
       "id": "security-lite",
       "capability": "security-lite",
       "status": "pass",
-      "durationMs": 0.016125000000101863,
+      "durationMs": 0.01841700000113633,
       "message": "No security issues detected (lightweight scan).",
       "evidence": [
         {
@@ -143,11 +143,58 @@
         }
       ]
     },
+    {
+      "id": "runtime-profile",
+      "capability": "runtime-profile",
+      "status": "partial",
+      "durationMs": 0.11679199999889534,
+      "message": "Detected 4 potential egress target(s) and 0 potential state mutation(s) with high confidence.",
+      "evidence": [
+        {
+          "endpoint": "runtime-profile/analyze",
+          "advertised": true,
+          "responded": true,
+          "minimalShapePresent": true,
+          "itemCount": 4,
+          "diagnostics": [
+            "Egress entries: 4",
+            "State mutations: 0",
+            "Confidence: high"
+          ],
+          "findings": [
+            {
+              "target": "ref_search_documentation",
+              "protocol": "unknown",
+              "source": "description_analysis",
+              "confidence": "low"
+            },
+            {
+              "target": "url",
+              "protocol": "unknown",
+              "source": "tool_schema",
+              "confidence": "high"
+            },
+            {
+              "target": "The URL of the webpage to read.",
+              "protocol": "unknown",
+              "source": "description_analysis",
+              "confidence": "medium"
+            },
+            {
+              "target": "ref_read_url",
+              "protocol": "unknown",
+              "source": "description_analysis",
+              "confidence": "low"
+            }
+          ]
+        }
+      ]
+    },
     {
       "id": "conformance",
       "capability": "conformance",
       "status": "pass",
-      "durationMs": 0.5073750000001382,
+      "durationMs": 0.5142089999990276,
       "message": "All 7 conformance checks passed.",
       "evidence": [
         {
@@ -173,7 +220,7 @@
       "id": "schema-quality",
       "capability": "schema-quality",
       "status": "pass",
-      "durationMs": 0.4954999999999927,
+      "durationMs": 0.5241670000013983,
       "message": "All 4 item(s) have good schema quality.",
       "evidence": [
         {
@@ -190,7 +237,7 @@
       "id": "security",
       "capability": "security",
       "status": "pass",
-      "durationMs": 0.19070799999917654,
+      "durationMs": 0.19254199999886623,
       "message": "No security issues detected.",
       "evidence": [
         {
@@ -206,7 +253,7 @@
       "id": "attack-sim",
       "capability": "attack-sim",
       "status": "pass",
-      "durationMs": 0.24504199999955745,
+      "durationMs": 0.26929200000085984,
       "message": "Safe attack simulation found no high-risk MCP attack-readiness findings.",
       "evidence": [
         {
@@ -265,16 +312,46 @@
         "weight": 0.1,
         "score": 100,
         "details": [
-          "Connect: 579ms",
+          "Connect: 726ms",
           "p95 latency: 1ms (3 operations)"
         ]
       }
     ]
   },
   "performanceMetrics": {
-    "connectMs": 579.0028749999992,
-    "toolsListMs": 0.8886670000001686,
-    "promptsListMs": 0.19312499999978172,
-    "resourcesListMs": 0.0022499999995488906
+    "connectMs": 725.896999999999,
+    "toolsListMs": 1.3943750000016735,
+    "promptsListMs": 0.23954200000116543,
+    "resourcesListMs": 0.002917000001616543
+  },
+  "runtimeProfile": {
+    "egress": [
+      {
+        "target": "ref_search_documentation",
+        "protocol": "unknown",
+        "source": "description_analysis",
+        "confidence": "low"
+      },
+      {
+        "target": "url",
+        "protocol": "unknown",
+        "source": "tool_schema",
+        "confidence": "high"
+      },
+      {
+        "target": "The URL of the webpage to read.",
+        "protocol": "unknown",
+        "source": "description_analysis",
+        "confidence": "medium"
+      },
+      {
+        "target": "ref_read_url",
+        "protocol": "unknown",
+        "source": "description_analysis",
+        "confidence": "low"
+      }
+    ],
+    "analyzedAt": "2026-07-15T22:33:23.029Z",
+    "confidence": "high"
   }
 }

package/docs/safety-index/artifacts/ref-tools-server.md

@@ -1,6 +1,6 @@
 # MCP Observatory Run Report
 
-Generated at 2026-07-06T19:49:51.606Z
+Generated at 2026-07-15T22:33:22.302Z
 
 ## Target and Environment Metadata
 
@@ -25,20 +25,40 @@ Generated at 2026-07-06T19:49:51.606Z
 
 | Gate | Total | Pass | Fail | Partial | Unsupported | Flaky | Skipped |
 | --- | --- | --- | --- | --- | --- | --- | --- |
-| pass | 8 | 7 | 0 | 0 | 1 | 0 | 0 |
+| pass | 9 | 7 | 0 | 1 | 1 | 0 | 0 |
 
 ## At a Glance
 
 - Safety verdict: **Needs review** — The server is usable, but caveated checks should be reviewed before agents depend on it.
-- Top risks: No high-priority risks detected.
+- Top risks: runtime-profile: Detected 4 potential egress target(s) and 0 potential state mutation(s) with high confidence.
 - Regression/schema drift: Run `mcp-observatory diff <previous-run.json> <current-run.json>` to classify regressions and schema drift.
 - Failing checks: none
-- Partial or flaky checks: none
+- Partial or flaky checks: runtime-profile
 - Skipped checks: none
 - Unsupported checks: resources
-- Suggested next step: Confirm that unsupported capabilities are intentional for this target: resources.
+- Suggested next step: Review the caveated checks next: runtime-profile.
 - CI next step: `Add CI: npx @kryptosai/mcp-observatory setup-ci --all --command "npx -y <server-package>"`
 
+## What Was Not Tested
+
+- ℹ️ credential_access: Credential scanning was performed (see security findings)
+- ℹ️ destructive_payloads: Destructive payloads were not attempted (safe-mode only)
+
+## Runtime Profile
+
+### Egress Manifest
+
+The following targets were identified as potentially reachable by this server (confidence: **high**):
+
+| Target | Protocol | Source | Confidence |
+| --- | --- | --- | --- |
+| ref_search_documentation | unknown | description_analysis | low |
+| url | unknown | tool_schema | high |
+| The URL of the webpage to read. | unknown | description_analysis | medium |
+| ref_read_url | unknown | description_analysis | low |
+
+_Analyzed at 2026-07-15T22:33:23.029Z_
+
 ## Regressions and Recoveries
 
 _Use the `diff` command against another run artifact to classify regressions and recoveries over time._
@@ -47,13 +67,14 @@ _Use the `diff` command against another run artifact to classify regressions and
 
 | Focus | Check | Status | Duration (ms) | Message |
 | --- | --- | --- | --- | --- |
-| healthy | attack-sim | pass | 0.25 | Safe attack simulation found no high-risk MCP attack-readiness findings. |
+| healthy | attack-sim | pass | 0.27 | Safe attack simulation found no high-risk MCP attack-readiness findings. |
 | healthy | conformance | pass | 0.51 | All 7 conformance checks passed. |
-| healthy | prompts | pass | 0.19 | Advertised capability responded with the minimal expected shape (2 items). |
-| healthy | schema-quality | pass | 0.50 | All 4 item(s) have good schema quality. |
+| healthy | prompts | pass | 0.24 | Advertised capability responded with the minimal expected shape (2 items). |
+| healthy | schema-quality | pass | 0.52 | All 4 item(s) have good schema quality. |
 | healthy | security | pass | 0.19 | No security issues detected. |
 | healthy | security-lite | pass | 0.02 | No security issues detected (lightweight scan). |
-| healthy | tools | pass | 0.89 | Advertised capability responded with the minimal expected shape (2 items). |
+| healthy | tools | pass | 1.39 | Advertised capability responded with the minimal expected shape (2 items). |
+| review | runtime-profile | partial | 0.12 | Detected 4 potential egress target(s) and 0 potential state mutation(s) with high confidence. |
 | confirm intent | resources | unsupported | 0.00 | Resources are not advertised by the target. |
 
 ## Evidence Snippets
@@ -142,6 +163,18 @@ Summary: Advertised capability responded with the minimal expected shape (2 item
   - Identifiers: ref_search_documentation, ref_read_url
   - Diagnostics: Ref MCP Server running on stdio
 
+### runtime-profile — partial
+
+Summary: Detected 4 potential egress target(s) and 0 potential state mutation(s) with high confidence.
+
+- Endpoint: `runtime-profile/analyze`
+  - Advertised: `true`
+  - Responded: `true`
+  - Minimal shape present: `true`
+  - Item count: `4`
+  - Identifiers: none
+  - Diagnostics: Egress entries: 4, State mutations: 0, Confidence: high
+
 ### resources — unsupported
 
 Summary: Resources are not advertised by the target.
@@ -165,5 +198,5 @@ npm run cli -- report --run <path-to-run-artifact.json> --format markdown
 
 - Artifact type: `run`
 - Schema version: `1.0.0`
-- Run ID: `run_2026-07-06T194951606Z_e657d5a4`
+- Run ID: `run_2026-07-15T223322301Z_3fb8821d`
 - Gate: `pass`

package/docs/safety-index/artifacts/resend-mcp.json

@@ -0,0 +1,66 @@
+{
+  "artifactType": "run",
+  "schemaVersion": "1.0.0",
+  "gate": "fail",
+  "runId": "run_2026-07-15T223503064Z_8b8b0ec6",
+  "createdAt": "2026-07-15T22:35:03.064Z",
+  "toolVersion": "1.32.1",
+  "target": {
+    "targetId": "resend-mcp",
+    "adapter": "local-process",
+    "command": "npx",
+    "args": [
+      "-y",
+      "resend-mcp"
+    ],
+    "cwd": ".",
+    "metadata": {
+      "package": "resend-mcp",
+      "purpose": "mcp-safety-index",
+      "riskClass": "Email sending platform access",
+      "failureClass": "Email send/domain boundary",
+      "whyItMatters": "Resend MCP servers can send emails, manage domains, and track delivery — agents could send transactional and marketing emails on behalf of verified domains."
+    }
+  },
+  "environment": {
+    "platform": "darwin 25.5.0",
+    "nodeVersion": "v22.22.1"
+  },
+  "summary": {
+    "total": 3,
+    "pass": 0,
+    "fail": 0,
+    "partial": 0,
+    "unsupported": 0,
+    "flaky": 0,
+    "skipped": 3,
+    "gate": "fail"
+  },
+  "checks": [
+    {
+      "id": "tools",
+      "capability": "tools",
+      "status": "skipped",
+      "durationMs": 0,
+      "message": "Skipped because startup failed before the MCP session initialized. See the failure diagnosis.",
+      "evidence": []
+    },
+    {
+      "id": "prompts",
+      "capability": "prompts",
+      "status": "skipped",
+      "durationMs": 0,
+      "message": "Skipped because startup failed before the MCP session initialized. See the failure diagnosis.",
+      "evidence": []
+    },
+    {
+      "id": "resources",
+      "capability": "resources",
+      "status": "skipped",
+      "durationMs": 0,
+      "message": "Skipped because startup failed before the MCP session initialized. See the failure diagnosis.",
+      "evidence": []
+    }
+  ],
+  "fatalError": "Could not establish a plain stdio MCP session for target `resend-mcp`.\nCommand: npx -y resend-mcp\nDiagnosis: The process exited or detached before MCP initialization completed.\nRaw error: MCP error -32000: Connection closed\nLikely causes:\n- The package may expect extra startup arguments or environment variables.\n- The package may not behave like a plain local-process stdio target under this invocation.\n- The server may be crashing immediately and only leaving clues on stderr.\nNext steps:\n- Run the command manually and look for usage output, auth prompts, or crash text.\n- Check whether the package expects a different transport or an app-oriented startup flow.\n- Use the recent stderr lines below before assuming this is a harness bug.\nRecent stderr:\n- Error: No API key. Set RESEND_API_KEY or use --key=<your-resend-api-key>"
+}

package/docs/safety-index/artifacts/resend-mcp.md

@@ -0,0 +1,102 @@
+# MCP Observatory Run Report
+
+Generated at 2026-07-15T22:35:03.064Z
+
+## Target and Environment Metadata
+
+- Target: `resend-mcp`
+- Adapter: `local-process`
+- Command: `npx -y resend-mcp`
+- Server: `unknown `
+- Platform: `darwin 25.5.0`
+- Node: `v22.22.1`
+
+## Executive Summary
+
+| Gate | Total | Pass | Fail | Partial | Unsupported | Flaky | Skipped |
+| --- | --- | --- | --- | --- | --- | --- | --- |
+| fail | 3 | 0 | 0 | 0 | 0 | 0 | 3 |
+
+## At a Glance
+
+- Safety verdict: **Blocked** — One or more checks can break agent dependence and should be fixed before production use.
+- Top risks: startup: server failed to start
+- Regression/schema drift: Run `mcp-observatory diff <previous-run.json> <current-run.json>` to classify regressions and schema drift.
+- Failing checks: none
+- Partial or flaky checks: none
+- Skipped checks: tools, prompts, resources
+- Unsupported checks: none
+- Suggested next step: Run the target command manually, compare stderr with the diagnosis below, and only raise timeoutMs if startup is genuinely slow.
+- CI next step: `Add CI: npx @kryptosai/mcp-observatory setup-ci --all --command "npx -y <server-package>"`
+
+## What Was Not Tested
+
+- 🔒 network_egress: No outbound network calls were attempted during scan
+- 🔒 filesystem_mutation: Filesystem write operations were not exercised
+- 🔒 credential_access: Credential scanning was not performed
+- ℹ️ destructive_payloads: Destructive payloads were not attempted (safe-mode only)
+
+## Regressions and Recoveries
+
+_Use the `diff` command against another run artifact to classify regressions and recoveries over time._
+
+## Failure Diagnosis
+
+```text
+Could not establish a plain stdio MCP session for target `resend-mcp`.
+Command: npx -y resend-mcp
+Diagnosis: The process exited or detached before MCP initialization completed.
+Raw error: MCP error -32000: Connection closed
+Likely causes:
+- The package may expect extra startup arguments or environment variables.
+- The package may not behave like a plain local-process stdio target under this invocation.
+- The server may be crashing immediately and only leaving clues on stderr.
+Next steps:
+- Run the command manually and look for usage output, auth prompts, or crash text.
+- Check whether the package expects a different transport or an app-oriented startup flow.
+- Use the recent stderr lines below before assuming this is a harness bug.
+Recent stderr:
+- Error: No API key. Set RESEND_API_KEY or use --key=<your-resend-api-key>
+```
+
+## Full Capability Status Table
+
+| Focus | Check | Status | Duration (ms) | Message |
+| --- | --- | --- | --- | --- |
+| inspect startup | prompts | skipped | 0.00 | Skipped because startup failed before the MCP session initialized. See the failure diagnosis. |
+| inspect startup | resources | skipped | 0.00 | Skipped because startup failed before the MCP session initialized. See the failure diagnosis. |
+| inspect startup | tools | skipped | 0.00 | Skipped because startup failed before the MCP session initialized. See the failure diagnosis. |
+
+## Evidence Snippets
+
+### prompts — skipped
+
+Summary: Skipped because startup failed before the MCP session initialized. See the failure diagnosis.
+
+_No evidence was captured._
+
+### resources — skipped
+
+Summary: Skipped because startup failed before the MCP session initialized. See the failure diagnosis.
+
+_No evidence was captured._
+
+### tools — skipped
+
+Summary: Skipped because startup failed before the MCP session initialized. See the failure diagnosis.
+
+_No evidence was captured._
+
+## Reproduction Commands
+
+```bash
+npm run cli -- run --target <path-to-target-config.json>
+npm run cli -- report --run <path-to-run-artifact.json> --format markdown
+```
+
+## Artifact Provenance
+
+- Artifact type: `run`
+- Schema version: `1.0.0`
+- Run ID: `run_2026-07-15T223503064Z_8b8b0ec6`
+- Gate: `fail`

package/docs/safety-index/artifacts/rozgar-mcp.json

@@ -0,0 +1,66 @@
+{
+  "artifactType": "run",
+  "schemaVersion": "1.0.0",
+  "gate": "fail",
+  "runId": "run_2026-07-15T223600962Z_4893f12e",
+  "createdAt": "2026-07-15T22:36:00.962Z",
+  "toolVersion": "1.32.1",
+  "target": {
+    "targetId": "rozgar-mcp",
+    "adapter": "local-process",
+    "command": "npx",
+    "args": [
+      "-y",
+      "rozgar-mcp"
+    ],
+    "cwd": ".",
+    "metadata": {
+      "package": "rozgar-mcp",
+      "purpose": "mcp-safety-index",
+      "riskClass": "Pakistani job platform API access",
+      "failureClass": "Job listing/application/candidate boundary",
+      "whyItMatters": "Rozgar.com is Pakistan's largest job platform serving millions of job seekers and employers. MCP servers exposing job listings, candidate applications, and recruiter tools handle sensitive employment data at national scale."
+    }
+  },
+  "environment": {
+    "platform": "darwin 25.5.0",
+    "nodeVersion": "v22.22.1"
+  },
+  "summary": {
+    "total": 3,
+    "pass": 0,
+    "fail": 0,
+    "partial": 0,
+    "unsupported": 0,
+    "flaky": 0,
+    "skipped": 3,
+    "gate": "fail"
+  },
+  "checks": [
+    {
+      "id": "tools",
+      "capability": "tools",
+      "status": "skipped",
+      "durationMs": 0,
+      "message": "Skipped because startup failed before the MCP session initialized. See the failure diagnosis.",
+      "evidence": []
+    },
+    {
+      "id": "prompts",
+      "capability": "prompts",
+      "status": "skipped",
+      "durationMs": 0,
+      "message": "Skipped because startup failed before the MCP session initialized. See the failure diagnosis.",
+      "evidence": []
+    },
+    {
+      "id": "resources",
+      "capability": "resources",
+      "status": "skipped",
+      "durationMs": 0,
+      "message": "Skipped because startup failed before the MCP session initialized. See the failure diagnosis.",
+      "evidence": []
+    }
+  ],
+  "fatalError": "Could not establish a plain stdio MCP session for target `rozgar-mcp`.\nCommand: npx -y rozgar-mcp\nDiagnosis: The process exited or detached before MCP initialization completed.\nRaw error: MCP error -32000: Connection closed\nLikely causes:\n- The package may expect extra startup arguments or environment variables.\n- The package may not behave like a plain local-process stdio target under this invocation.\n- The server may be crashing immediately and only leaving clues on stderr.\nNext steps:\n- Run the command manually and look for usage output, auth prompts, or crash text.\n- Check whether the package expects a different transport or an app-oriented startup flow.\n- Use the recent stderr lines below before assuming this is a harness bug.\nRecent stderr:\n- npm error 404  'rozgar-mcp@*' is not in this registry.\n- npm error 404\n- npm error 404 Note that you can also install from a\n- npm error 404 tarball, folder, http url, or git url.\n- npm error A complete log of this run can be found in: /Users/williamweishuhn/.npm/_logs/2026-07-15T22_36_01_034Z-debug-0.log"
+}

package/docs/safety-index/artifacts/rozgar-mcp.md

@@ -0,0 +1,106 @@
+# MCP Observatory Run Report
+
+Generated at 2026-07-15T22:36:00.962Z
+
+## Target and Environment Metadata
+
+- Target: `rozgar-mcp`
+- Adapter: `local-process`
+- Command: `npx -y rozgar-mcp`
+- Server: `unknown `
+- Platform: `darwin 25.5.0`
+- Node: `v22.22.1`
+
+## Executive Summary
+
+| Gate | Total | Pass | Fail | Partial | Unsupported | Flaky | Skipped |
+| --- | --- | --- | --- | --- | --- | --- | --- |
+| fail | 3 | 0 | 0 | 0 | 0 | 0 | 3 |
+
+## At a Glance
+
+- Safety verdict: **Blocked** — One or more checks can break agent dependence and should be fixed before production use.
+- Top risks: startup: server failed to start
+- Regression/schema drift: Run `mcp-observatory diff <previous-run.json> <current-run.json>` to classify regressions and schema drift.
+- Failing checks: none
+- Partial or flaky checks: none
+- Skipped checks: tools, prompts, resources
+- Unsupported checks: none
+- Suggested next step: Run the target command manually, compare stderr with the diagnosis below, and only raise timeoutMs if startup is genuinely slow.
+- CI next step: `Add CI: npx @kryptosai/mcp-observatory setup-ci --all --command "npx -y <server-package>"`
+
+## What Was Not Tested
+
+- 🔒 network_egress: No outbound network calls were attempted during scan
+- 🔒 filesystem_mutation: Filesystem write operations were not exercised
+- 🔒 credential_access: Credential scanning was not performed
+- ℹ️ destructive_payloads: Destructive payloads were not attempted (safe-mode only)
+
+## Regressions and Recoveries
+
+_Use the `diff` command against another run artifact to classify regressions and recoveries over time._
+
+## Failure Diagnosis
+
+```text
+Could not establish a plain stdio MCP session for target `rozgar-mcp`.
+Command: npx -y rozgar-mcp
+Diagnosis: The process exited or detached before MCP initialization completed.
+Raw error: MCP error -32000: Connection closed
+Likely causes:
+- The package may expect extra startup arguments or environment variables.
+- The package may not behave like a plain local-process stdio target under this invocation.
+- The server may be crashing immediately and only leaving clues on stderr.
+Next steps:
+- Run the command manually and look for usage output, auth prompts, or crash text.
+- Check whether the package expects a different transport or an app-oriented startup flow.
+- Use the recent stderr lines below before assuming this is a harness bug.
+Recent stderr:
+- npm error 404  'rozgar-mcp@*' is not in this registry.
+- npm error 404
+- npm error 404 Note that you can also install from a
+- npm error 404 tarball, folder, http url, or git url.
+- npm error A complete log of this run can be found in: /Users/williamweishuhn/.npm/_logs/2026-07-15T22_36_01_034Z-debug-0.log
+```
+
+## Full Capability Status Table
+
+| Focus | Check | Status | Duration (ms) | Message |
+| --- | --- | --- | --- | --- |
+| inspect startup | prompts | skipped | 0.00 | Skipped because startup failed before the MCP session initialized. See the failure diagnosis. |
+| inspect startup | resources | skipped | 0.00 | Skipped because startup failed before the MCP session initialized. See the failure diagnosis. |
+| inspect startup | tools | skipped | 0.00 | Skipped because startup failed before the MCP session initialized. See the failure diagnosis. |
+
+## Evidence Snippets
+
+### prompts — skipped
+
+Summary: Skipped because startup failed before the MCP session initialized. See the failure diagnosis.
+
+_No evidence was captured._
+
+### resources — skipped
+
+Summary: Skipped because startup failed before the MCP session initialized. See the failure diagnosis.
+
+_No evidence was captured._
+
+### tools — skipped
+
+Summary: Skipped because startup failed before the MCP session initialized. See the failure diagnosis.
+
+_No evidence was captured._
+
+## Reproduction Commands
+
+```bash
+npm run cli -- run --target <path-to-target-config.json>
+npm run cli -- report --run <path-to-run-artifact.json> --format markdown
+```
+
+## Artifact Provenance
+
+- Artifact type: `run`
+- Schema version: `1.0.0`
+- Run ID: `run_2026-07-15T223600962Z_4893f12e`
+- Gate: `fail`