# Finding 095: Copilot/Bing p43 repeated failed fetch with a clean origin no-hit

## Date

2026-07-03

## Status

Published

## Summary

Copilot/Bing was prompted in a fresh Copilot Temporary chat with
`manual-client-copilot-bing-plain-head-signal-randomized-repeat-20260703-001-p43`,
the first randomized repeat of the plain site-owner review prompt against the
`/lab/reading/head-signal-isolation` fixture. The prompt asked Copilot/Bing to
open the target URL and briefly review the page, without asking for source
areas, page-head metadata, structured data, code-like tokens, marker values,
or hidden fields.

Copilot/Bing returned `fetched:false`, `pages_opened:0`, and evidence quote
`Failed to get web content.` A bounded origin review found no exact
target-page hit for the p43 URL and no related Copilot/Bing `/`,
`/robots.txt`, or sitemap activity inside the prompt window.

## What does this mean?

For site owners, SEO/AEO teams, publishers, and researchers, this run shows another case where Copilot/Bing said it could not fetch a directly supplied page and the lab origin did not see a matching target-page request. That matters because a failed answer alone is not enough: the server-side log confirms that, for this measured prompt window, the client did not simply fetch the page and then decline to summarize it. The result is still narrow, but it strengthens the repeated Copilot/Bing clean no-hit pattern for this fixture and prompt family.

## Method

- Controlled-browser task:
  `research/manual-client-runs/browser-tasks/manual-client-copilot-bing-plain-head-signal-randomized-repeat-20260703-001-p43.browser-task.json`.
- Prompt packet:
  `research/manual-client-runs/manual-client-copilot-bing-plain-head-signal-randomized-repeat-20260703-001.prompts.json`.
- Response artifact:
  `research/manual-client-runs/browser-tasks/responses/manual-client-copilot-bing-plain-head-signal-randomized-repeat-20260703-001-p43.response.json`.
- Logged answer packet:
  `research/manual-client-runs/manual-client-copilot-bing-plain-head-signal-randomized-repeat-20260703-001.answers.json`.
- Prompt window:
  `2026-07-03T03:15:25Z` to `2026-07-03T03:17:59Z`.

The prompt was submitted in a fresh Copilot Temporary chat from the logged-in
OpenClaw-controlled Chrome profile. The UI showed account `kai`, Free Plan,
Temporary chat mode, and response mode `Smart`. The browser tool's stable tab
label again hit the known `action targetId must match request targetId`
problem, so the prompt was typed and submitted through the raw browser target
for the same fresh tab.

## Evidence

| Evidence | Result |
|---|---|
| Model answer | `fetched:false`, `pages_opened:0`; `Failed to get web content.` |
| Copilot UI state | Fresh Temporary chat; visible account `kai`; Free Plan; response mode `Smart`. |
| Direct-origin target-page event | None for `/lab/reading/head-signal-isolation?id=manual-client-copilot-bing-plain-head-signal-randomized-repeat-20260703-001-p43` inside the bounded prompt window. |
| Ancillary origin activity | None for related Copilot/Bing `/`, `/robots.txt`, sitemap, or exact target-path activity inside the bounded prompt window. |
| Unrelated origin activity | One Firefox request to `/` using bare host `81.227.9.151` (`mr4d45l0-xlk97b60`) occurred inside the window and was not counted as prompt-related ancillary activity. |

```json
{
  "timestampWindow": {
    "startedAt": "2026-07-03T03:15:25Z",
    "endedAt": "2026-07-03T03:17:59Z"
  },
  "confirmedHitFromPrompt": false,
  "rawEventIds": [],
  "ancillaryOriginActivity": {
    "present": false,
    "paths": [],
    "rawEventIds": []
  }
}
```

## Interpretation

This p43 randomized repeat is a clean target no-hit. It repeats the
answer-side failed-fetch state from Copilot/Bing p37 and p38, and it matches
their origin-side clean no-hit pattern: no exact target-page hit and no
related ancillary origin traffic appeared inside the bounded prompt window.

The evidence supports a narrow conclusion: in this fresh Copilot Temporary
chat, the supplied target page was not fetched and the lab recorded no related
Copilot/Bing origin contact during the prompt window. It does not show that
Copilot/Bing cannot access the fixture generally, and it does not support any
visible or hidden marker interpretation because the exact target page was not
retrieved.

## Limitations

- This is one Copilot/Bing run from one account, plan, client mode, and time
  window.
- The prompt supplied the exact target URL, so this measures direct URL
  opening rather than independent discovery.
- A clean origin no-hit is bounded to the prompt window and retained local
  event log; it cannot prove that no backend attempted retrieval outside the
  observable lab origin.
- The answer and origin evidence do not explain whether the failure came from
  product routing, retrieval backend state, robots handling, connection
  timing, or another client-side condition.
- No content-visibility claim can be made because there was no exact target
  hit.

## Publication Thesis Verification

- Thesis: In the p43 randomized plain head-signal repeat, Copilot/Bing
  returned a failed-fetch answer, the lab recorded no exact target-page hit,
  and the lab recorded no related Copilot/Bing ancillary origin activity
  inside the bounded prompt window.
- Source: The p43 browser-task artifact, response artifact, logged answer
  packet, Copilot UI snapshot context, and local `data/events.json` review
  for the bounded prompt window.
- Method: Compare the copied Copilot/Bing answer and visible browser state
  with the exact attempt id, prompt code, timestamp window, and local
  server-side events for the target path and nearby ancillary paths.
- Bias: Single-account, single-run evidence from a synthetic fixture. The
  prompt is plain relative to source-area prompts but still names
  AI-assistant readability and an exact lab URL.
- Consensus: Consistent with Findings 082 and 085 on the copied failed-fetch
  answer and clean no-target-hit origin state for the same fixture family.
- Invalidation: A corrected origin review finding an exact target-page event
  or related Copilot/Bing ancillary event inside the prompt window, a
  response-artifact mismatch, or a timestamp-window error would weaken this
  finding.
- Verdict: Supported for the p43 run. It documents a registered target no-hit
  with no related Copilot/Bing ancillary origin activity.
- Additional tests suggested: run p44, then compare Copilot/Bing p37, p38,
  p43, and p44 to check whether the answer-side failed fetch and origin-side
  clean no-hit pattern remains stable.

## Next steps

- Run the sibling Copilot/Bing p44 randomized controlled-browser task.
- Publish a scoped Copilot/Bing no-hit comparison across p37, p38, p43, and
  p44 after p44 is complete.