mirror of
https://github.com/CopilotKit/CopilotKit.git
synced 2026-09-14 16:26:20 +08:00
Benjamin Taylor
783fc89337
Narrows this PR to OSS-566 + OSS-568. The OSS-565 CI-suppression effort is backed out entirely: - the 10 workflows' `COPILOTKIT_TELEMETRY_DISABLED` / `DO_NOT_TRACK` env and the egress-block steps - `examples/e2e/playwright.config.ts` env defaults - the runtime/shared test-env manipulation and the `telemetry-opt-out-env` helper - the `navigator.webdriver` check and its tests Every reverted path is byte-identical to the merge-base — verified rather than assumed, since `git checkout origin/main -- <path>` would otherwise have imported main's newer content for files that had moved on. One piece is deliberately kept, because it is not about CI: the jsdom egress guard. These tests run with a real `fetch`, and the inspector's telemetry is fire-and-forget, so any test touching a banner / threads / open path without stubbing fetch POSTs a real `oss.inspector.*` event to the live sink — from developer machines as well as CI. The announcement-dismissal tests did exactly that before the guard, and the new `opened` / `banner_dismissed` tests hit the same send path, so shipping the events without it would make our own dataset dirtier. Its comments no longer cite OSS-565; the rationale stands on its own. What remains: `oss.inspector.opened` with open-source attribution, the `banner_viewed` surface split, and first-class `banner_dismissed`. No inspector telemetry waits on the /info handshake. Verified: web-inspector 112, runtime 1,760, shared 199 (the last two now on main's own test files). tsc clean, oxfmt clean, oxlint 9 warnings all pre-existing. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>