mirror of
https://github.com/CopilotKit/CopilotKit.git
synced 2026-09-14 16:26:20 +08:00
Jordan Ritter
d2c232aade
These two pills fail turn-2 across every integration due to a confirmed useInterrupt/useHeadlessInterrupt RESUME-PATH hook bug in the published @copilotkit/react-core/v2 package: the backend resumes and streams the confirmation (HTTP 200, full body) but the frontend never appends the confirmation assistant bubble, so the harness DOM settle-check stays frozen at baseline and times out. The real fix is a react-core package release, which is out of scope (no releases). Use the existing per-integration not_supported_features mechanism (same shape ag2/agno/crewai/llamaindex/mastra already use for these IDs): move gen-ui-interrupt and interrupt-headless out of `features:` and into `not_supported_features:` in the 12 integrations that still declared them wired (incl. the langgraph-python reference, which needed a new NSF block). The demo entries stay wired so the pages remain live; the D6 driver reclassifies these features as `skipped-incapable` green side-rows (surfaced in the aggregate `skipped[]`/`incapable[]`) instead of counting them as RED regressions. Each manifest carries a documented reason comment referencing the react-core resume-bubble bug and the pending release. This is an honest skip — shown as not-supported/skipped, not a fabricated pass. Validated by regenerating the registry/catalog with zero validation errors (no feature/NSF conflict).