Refresh Unity-Unterm ANSI color vendor

[dudetru25]

What changed

• refresh both vendored Unity-Unterm package mirrors to fork commit e4adaebe6235a6547314e4171e1a34229cde157e
• import the macOS and Windows native library/debugger artifacts from the fork's GitHub-hosted push run
• update the pinned workflow run, attestation, source ref, binary SHA-256 values, and vendor validator expectations
• document restored ANSI colors for agent-launched terminal sessions

Why

Unity can inherit TERM=dumb and NO_COLOR=1 when launched from an agent host. The fork fix removes that host-only color opt-out at the Unterm PTY boundary while preserving an interactive user's explicit NO_COLOR preference, allowing Codex error/interruption text and other semantic terminal colors to render correctly.

Depends on rankupgames/Unity-Unterm#4.

Provenance

• source commit: e4adaebe6235a6547314e4171e1a34229cde157e
• build run: 29298714732
• attestation: 35179180
• all four native artifacts and Third Party Notices.md verified against the exact source digest/ref, pinned signer workflow, and GitHub-hosted runners
• build-provenance checksums matched before import

Validation

• npm run validate — 205 tests passed across the runtime, simplified-context, and remote-shell suites; vendor validation and both npm audits passed
• node unity-cursor-toolkit/scripts/validate-vendored-unterm.js — 80 files validated in both package mirrors
• npx --no-install vsce package --no-dependencies --out /tmp/unity-cursor-toolkit-ansi-smoke.vsix — passed
• canonical/smoke changelogs, manifests, and native artifacts are byte-identical

---

^{Need help on this PR? Tag /codesmith with what you need. Autofix is disabled.}