Fix: accept Windows' refused-connection wording in the isolation test

[0xLeif]

Summary

• default_temp_env_points_github_at_a_dead_port failed on test (windows-latest) in the v1.8.0 release PR chore: release v1.8.0 #532. The error: io: no connection could be made because the target machine actively refused it. (os error 10061).
• Cause: chore: release v1.8.0 #532's lockfile moves ureq from 3.3.0 to 3.4.2. ureq 3.3.0 replaced every refused connect with a synthetic "Connection refused", so every OS printed the same words. ureq 3.4 passes the OS error through (last_err in transport/tcp.rs). Linux and macOS still say Connection refused (os error 111/61), but Windows now uses WSAECONNREFUSED's own text. main is green only because it still pins ureq 3.3.0. Any lockfile refresh brings this failure in.
• Fix: accept actively refused / os error 10061 alongside connection refused. Both halves of the proof stay: the child's GitHub base must start with http://127.0.0.1:, and the failure must be a refusal. A bare failed still doesn't count, so a real api.github.com failure still fails the test.
• Adds the SpecSync change record accept-windows-refused-connection-wording-in-the-isolation-test (bug-fix, no spec change). It's a draft awaiting definition approval. specsync change check --strict --require-coverage 100 and lifecycle enforce --all pass with it present.
• Addresses corvid-agent's CHANGES_REQUESTED on chore: release v1.8.0 #532 (option 1: widen the assertion). The Windows matrix cell stays.

Test Plan

• fledge run test -- --test isolation on main's lockfile (ureq 3.3.0), macOS: 4 passed
• Same test on chore: release v1.8.0 #532's lockfile (ureq 3.4.2), macOS: 4 passed
• Spawned-binary stderr observed: 3.3.0 prints io: Connection refused, 3.4.2 prints io: Connection refused (os error 61)
• fledge lanes run verify (fmt, lint, test, build, spec-check, validate-templates) passes
• fledge trust verify --range origin/main..HEAD passes (augur: proceed, risk 18)
• test (windows-latest) green here with ureq 3.3.0 (run 36257383427)
• test (windows-latest) green with ureq 3.4.2 (run 36257571327). That run was a workflow_dispatch probe of main + this fix + chore: release v1.8.0 #532's release commit. The log shows Compiling ureq v3.4.2 then default_temp_env_points_github_at_a_dead_port ... ok
• SpecSync: definition approval → change check → scoped review → change finalize, before merge

🤖 Generated with Claude Code

https://claude.ai/code/session_01V3ZZAEiUP7xRJPozhZb6rL

[chatgpt-codex-connector]

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	✅ Completed 2026-09-26T17:01:20.185280Z	0cda5e8	PR opened

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

[github-actions]

✅ Corvin says...

      _
    <(^\  .oO(Caw! ^v^)
     |/(\
      \(\\
      " "\\

"Caw! Your code sparkles like a dropped french fry."

CI Summary

Check	Status
Dependency Audit	✅ Passed
Integration (3 OS)	✅ Passed
Lint (fmt + clippy)	✅ Passed
Spec Validation	✅ Passed
Tests (3 OS)	✅ Passed

---

_{Powered by corvid-pet}