Parity CI: environment-only failures (server fixtures, npm install, runner-specific)

[proggeramlug]

Summary

Several test-parity/known_failures.json entries are categorized ci-env: they fail on the Linux CI runner for environmental reasons, not Perry compiler bugs. They had no tracking issue (issue: null). This is their shared home.

These are not fixed by changing Perry — they need CI-side fixtures or runner setup.

Entries

Need a TCP/TLS echo-server fixture (pass locally with a server running; CI has none):

• test_issue_422_socket_connect
• test_net_min
• test_net_socket
• test_net_upgrade_tls (needs the TLS-upgrade companion server)
• test_sock_write_map

Need an npm install in CI:

• test_ramda_sum (parity harness can't npm install ramda)

Runner-specific / decorator-metadata flake:

• test_decorators_nest_js_common_canary (expected-output mismatch under the Linux runner; tied to NestJS decorator metadata-inheritance follow-ups — re-home to a dedicated decorator-parity issue if it turns out to be a real compiler gap rather than runner noise)

Suggested resolution

Add the echo-server lifecycle (already present in run_parity_tests.sh as start_echo_server/start_tls_upgrade_server) to the CI job, or gate these tests behind a requires-fixture marker so they don't need to live in the skip-list. Part of #793.

[andrewtdiz]

I am taking a focused parity-harness cleanup slice for the net companion-server entries in this CI-env tracker.

Scope for this PR: make the legacy top-level net/TLS companion-server readiness checks self-contained in run_parity_tests.sh instead of depending on runner nc availability, then remove the stale known-failure entries for the echo/TLS-backed net fixtures once the focused filters pass. I will leave test_ramda_sum in place because that still depends on npm package installation, not the net fixture lifecycle.

[andrewtdiz]

Opened draft PR #4285 for the focused net companion-fixture cleanup under this tracker.

Scope:

• replace the runner's nc readiness probes with a Python socket probe for the echo and TLS-upgrade companion servers;
• add missing guardrails for the TLS helper when Python or the server script is unavailable;
• remove the now-green net/TLS fixture entries from test-parity/known_failures.json.

Validated on the rebased branch with Node v26:

• test_issue_422_socket_connect: 1 pass / 0 fail
• test_net_min: 1 pass / 0 fail
• test_net_socket: 1 pass / 0 fail
• test_net_upgrade_tls: 1 pass / 0 fail via expected-output path
• test_sock_write_map: 1 pass / 0 fail

test_ramda_sum remains listed because it still depends on npm package installation, not the net companion-server lifecycle.

[andrewtdiz]

Follow-up on the PR scope: after checking the current fixture, test_ramda_sum is no longer an npm-package install case; it is a self-contained runtime mini-reproducer. I validated it under Node v26 with ./run_parity_tests.sh --filter test_ramda_sum and it passed 1 / 0 / 0.

I updated draft PR #4285 to remove that final #1634 ci-env entry as well, so the PR now retires all known-failure entries owned by this issue. Module-inventory and stream/web entries remain unchanged.