PR #23635 runtime verification, Linux VM, 2026-10-28 UTC
main: 0c80751701 (github/main), /home/user/main
head: be1abfc3156037d27da90a2c69859e4191e0c3fb, /home/user/t3code

$ git worktree add ../main github/main
$ cd ../main && timeout 600 vp i
exit 0
$ setsid nohup timeout 6000 vp run dev > /tmp/main-dev.log 2>&1 &
[dev-runner] serverPort=16733 webPort=8693

Chrome via repository Playwright 1.60.0, /usr/bin/google-chrome.
UI: Add project > Git URL > https://bitbucket.org/snakeyaml/snakeyaml.git > Create & Clone.
UI: select GPT-6.1-Sol, submit read-only request for git origin and current branch.
main: completed; origin=https://bitbucket.org/snakeyaml/snakeyaml.git, branch=master, PR23635-MAIN-REAL.
UI: Pull requests > Filters > Project > snakeyaml is disabled, Unavailable.
WebSocket pullRequests.list: bitbucket configured=false, paused until rate limit resets.
Original pagination bug could NOT be reproduced.
Stopped main by captured process-group PID before starting head.

$ git switch --detach be1abfc3156037d27da90a2c69859e4191e0c3fb
$ timeout 600 vp i
exit 0
$ setsid nohup timeout 6000 vp run dev > /tmp/dev.log 2>&1 &
[dev-runner] serverPort=13773 webPort=5733
UI: Add project > Local folder > /home/user/snakeyaml.
UI: GPT-6.1-Sol read-only turn completed; same origin and branch, PR23635-HEAD-REAL.
UI: Pull requests > Load more pull requests.
WebSocket pullRequests.list initial page: 99 GitCafe entries, truncated=true.
Continuation: 99 GitCafe entries, zero overlap with initial page, cursor delivered=198.
Bitbucket configured=false; detail=Bitbucket rejected the configured credentials. Check them in Settings -> Source Control.
UI: Filters > Project > snakeyaml is disabled, Unavailable.

Public read-only Bitbucket REST initially returned real snakeyaml #88:
updated_on=2026-02-26T08:28:25.275452+00:00.
No same-millisecond pair found. Subsequent boundary query returned:
Rate limit for this resource has been exceeded
No mocks, API stand-ins, fixtures, or demo data used.
No source changes, commits, or pushes made.
CI observed: 28 successful, 0 failing, 0 pending. No new code checks run.
Conclusion: changed Bitbucket pagination behavior remains unverified.