Yichen Jiang b239db6aeb test(net): assert the proxy-name contract on a platform that folds case ...

The Windows coverage lane failed on four cases that assume `http_proxy` and
`HTTP_PROXY` are separate variables. They are one variable there: `process.env`
is case-insensitive, and the launch snapshot folds names for the same reason. A
scenario built on "the user set only the lowercase name" cannot exist.

Two of them assert a contract rather than a spelling, so they now hold either
way: what reaches a child for a scheme the user named is the user's own value
and never the derived one, and a nested install carries the active policy's
value rather than the outer install's published one. Both read over the pair of
names instead of one.

The other two are about the case distinction itself. Neither can hold on a
folded environment, so each asserts what that platform does instead of skipping:
the later entry wins where a preference cannot be expressed, and a diagnostic
names the spelling resolution asked for. Both were verified against the folding
arm rather than reasoned about.

2026-08-29 13:37:29 +08:00

..

install.spec.ts

test(net): assert the proxy-name contract on a platform that folds case

2026-08-29 13:37:29 +08:00

matcher-parity.spec.ts

fix(net): route by the policy, and give a child the routing its parent has

2026-08-29 13:17:12 +08:00

plugin.spec.ts

test: start every suite from an environment with no proxy

2026-08-29 13:17:12 +08:00

policy.spec.ts

test(net): assert the proxy-name contract on a platform that folds case

2026-08-29 13:37:29 +08:00