chore(testdata): upstream-config drift detected (cursor)

[github-actions]

Upstream config drift detected — cursor

Reconciling testagent's corpus with current upstream docs.

Added (7)

Net-new examples found in docs that pass testagent cursor validate --strict.

• testdata/upstream-examples/cursor/hooks-upstream-20260526-f38a22d8.json (from https://cursor.com/docs/hooks.md)
• testdata/upstream-examples/cursor/mcp-upstream-20260526-f158ff1f.json (from https://cursor.com/docs/mcp.md)
• testdata/upstream-examples/cursor/mcp-upstream-20260526-d22bb18c.json (from https://cursor.com/docs/mcp.md)
• testdata/upstream-examples/cursor/mcp-upstream-20260526-03764548.json (from https://cursor.com/docs/mcp.md)
• testdata/upstream-examples/cursor/mcp-upstream-20260526-6044dc9e.json (from https://cursor.com/help/customization/mcp.md)
• testdata/upstream-examples/cursor/mcp-upstream-20260526-d8799949.json (from https://cursor.com/help/customization/mcp.md)
• testdata/upstream-examples/cursor/mcp-upstream-20260526-b771803d.json (from https://cursor.com/help/customization/mcp.md)

Retired (5)

Existing fixtures whose exact bytes are no longer present at the
.source URL we recorded. Only fixtures whose source page was
fetched this run are retired (guards against vendor docs URL
restructures).

• testdata/upstream-examples/cursor/hooks-before-shell-execution-prompt-type.json (last verified 2026-05-20 at https://cursor.com/docs/hooks)
• testdata/upstream-examples/cursor/hooks-before-shell-execution-network-guard.json (last verified 2026-05-20 at https://cursor.com/docs/hooks)
• testdata/upstream-examples/cursor/hooks-before-shell-execution-kube-guard.json (last verified 2026-05-20 at https://cursor.com/docs/hooks)
• testdata/upstream-examples/cursor/hooks-stop-ts-track.json (last verified 2026-05-20 at https://cursor.com/docs/hooks)
• testdata/upstream-examples/cursor/hooks-multi-event-matchers.json (last verified 2026-05-20 at https://cursor.com/docs/hooks)

Skipped — fail --strict

• 6 examples failed testagent cursor validate --strict; tracked separately in update-compatibility.

How to evaluate

Each Added fixture passed testagent cursor validate --strict in the
workflow. That's necessary but not sufficient — runtime behavior of
the actual vendor binary (claude / codex / cursor) is the
canonical source of truth, not the docs page. testagent's job is to
match what the real vendor accepts, even when testagent's own internal
runtime doesn't model every field.

Triage rules:

1. Added: spot-check each fixture matches what the real vendor
   binary would accept. If our validator accepts a fixture but the
   doc example looks stale or wrong (typo, deprecated key), drop it
   from this PR and file an upstream doc bug — don't widen our
   validator to match a wrong doc.
2. Retired: a fixture's exact bytes are no longer in upstream
   docs at the URL we recorded. Default to accepting the retirement.
   Push back only if the fixture exercises a real-world shape the
   vendor still accepts at runtime — in which case keep it locally
   and update the .source URL or add a comment explaining why.
3. Skipped — fail --strict: doc examples we couldn't accept.
   Sometimes the doc is right and we're missing schema coverage
   (→ extend the allowlist via update-compatibility). Sometimes
   the doc is wrong (→ leave it skipped).

When uncertain, run the real cursor binary against the fixture in
a sandbox before merging.

🤖 Generated by .github/workflows/upstream-drift.yml