# Documentation reproduction

Surface: GitHub's real Markdown Preview in Chromium, logged out, light theme,
1280 x 800 CSS pixels (screenshots at device scale 2). No seeded app data.

For each commit below, open the linked guide, then scroll the paragraph beginning
“When you return to a large thread” into the center of the viewport.

- Before: https://github.com/pingdotgg/t3code/blob/cd3a57ac7221b4151fb7c64a132d9ba59d98beaa/docs/user/providers-claude.md
- After: https://github.com/pingdotgg/t3code/blob/a4a9ab3d78499755656b33746adc0016d4757797/docs/user/providers-claude.md

The browser driver used this JavaScript solely to scroll, without changing content:

```js
const p = [...document.querySelectorAll('article p')]
  .find(p => p.textContent.includes('The mobile app'));
p.scrollIntoView({block: 'center'});
```

Before: the paragraph says mobile shows no chip and summarizes first.
After: it says mobile shows the same chip, labelled with the token count, and
that tapping it keeps full history for that message.

Each final still was visually inspected. Two consecutive screenshots, taken more
than 500 ms apart, were byte-identical on each side before upload.

This is a docs-only correction. No T3 client was started and no mobile chip
interaction was exercised; the documentation is viewed on GitHub, not served
by the T3 client. The scenario runner is therefore not used.
