mirror of
https://github.com/CopilotKit/CopilotKit.git
synced 2026-09-14 16:26:20 +08:00
Benjamin Taylor
44631fc328
The two entry-point skills point at documentation, so the existing guard checks that every docs path they name resolves. The Inspector and Intelligence skills point at the repository instead — an Nx target, a dev-server port, a lab scenario id, a landing-page source file, a Callout snippet — and nothing checked those. They had already drifted. `465abb0239` (OSS-948) deleted `open-inspector-step-angular.mdx`, saying so plainly in its message: the Angular snippet "is deleted in favour of the shared one every other web frontend already uses", because `@copilotkit/angular@0.4.0` auto-mounts a pinned web-inspector and there is no install step left to link. That commit never touched `pane-map.md`, so the map kept pointing at the deleted file and `inspector-docs` kept telling agents Angular uses its own snippet. Both are corrected here. Four assertions, all with unambiguous ground truth: - every `open-inspector-*.mdx` the pane map names exists - every `docs/…mdx` page the pane map names exists - every `showcase/shell-docs/src/…` file `intelligence-docs` says to edit in the same change exists - the Nx target, port, scenario ids and query keys `inspector-workbench` tells an agent to run resolve against `project.json` and the lab Each was mutation-checked: breaking the intelligence path, the port, the scenario, the target, and a docs page reference each fails exactly one test, and the restored tree passes. Deliberately not asserted: which panes the Inspector ships. Panes are not enumerated as data in `packages/web-inspector`, whose entry point is a single fourteen-thousand-line module, so matching a pane label against source proves nothing in either direction. A first draft tried it and passed while the map was in fact wrong — "Pop-out window" is listed unshipped although `src/lib/pop-out.ts` is imported by the package entry and has its own suite — which is worse than no test, because green reads as confirmation. That direction needs a pane registry in the package, not a cleverer regex here; the comment in the suite says so, and the Pop-out row is left for the Inspector owner to rule on rather than guessed at. This is the cheap half of testing a skill: whether it is still true. Whether it measurably helps an agent is the other half, and that needs the lift eval in #5689. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>