PR #29335 runtime verification, Linux Boat VM
main: 07a1e799d6 (github/main fetched this turn)
PR: 9754f122c66a4b0c92d3cbe1bc2a71b7fdd56b02

Separate dev instances, one at a time. Fresh app state. Playwright from repo dependencies and /usr/bin/google-chrome. Created project through Add project > Local folder, selected Codex gpt-6.1-sol, submitted actual provider turns. Provider executed timeout 30 node --input-type=module with the imported satisfiesSemverRange and new Function from its toString(). Both commands exited 0. Provider tool output was expanded and inspected in the client.

version   range      main imported/recreated   PR imported/recreated
0.5.0     ^0         false/false              true/true
0.0.4     ^0.0       false/false              true/true
1.0.0     ^0         false/false              false/false
0.1.0     ^0.0       false/false              false/false
0.0.4     ^0.0.3     false/false              false/false
0.0.0     ^0.0.0     true/true                true/true
0.0.1     ^0.0.0     false/false              false/false
24.10.0   >=24.10    true/true                true/true
24.9.9    >=24.10    false/false              false/false

Neighbor: Settings > Providers > Refresh provider status completed, Checked just now, Codex v0.164.0 Available.
Blacksmith: vp test run packages/shared/src/semver.test.ts packages/ssh/src/tunnel.test.ts apps/server/src/provider/providerCompatibility.test.ts => 3 files, 29 tests passed.
Existing CI: 28 successful, 0 failing, 0 pending.

Limit: the published compatibility manifest has no ^0 or ^0.0 rule. The changed helper is verified inside real provider tool execution, not a live compatibility-policy decision using those shorthands. No fake policy data was injected. Native clients, WSL, actual SSH bootstrap, other providers and remote/tunnel modes were not exercised.
No source edits, commits or pushes.