[Fleet Execution] Add CI Visual Testing Script + Agent Skill Example

[jules-fleet]

Objective

Create a Tier 5 CI visual testing workflow that pairs a deterministic script (ci-runner.ts) for regenerating designs and fetching screenshots with an Agent Skill (SKILL.md) guiding visual regression evaluation.

Code-Level Diagnosis

Code path: packages/sdk/examples/ci-visual-testing/
Mechanism: The packages/sdk/examples/ directory lacks the ci-visual-testing structure.
Root cause: Missing integrated example that demonstrates incorporating Stitch-generated designs into an automated CI pipeline with visual diff evaluation.

Current Implementation

// No ci-visual-testing example currently exists

Proposed Implementation

Files to modify: Create packages/sdk/examples/ci-visual-testing/SKILL.md, packages/sdk/examples/ci-visual-testing/README.md, and packages/sdk/examples/ci-visual-testing/scripts/ci-runner.ts.

Integration (Before -> After)

+// Create ci-visual-testing structure
+import { stitch } from "@google/stitch-sdk";
+import "../../_require-key.js";
+// Implement ci-runner script automating design baseline fetching

Test Scenarios

1. Execute cd packages/sdk/examples/ci-visual-testing && bun scripts/ci-runner.ts -> Verify that the runner fetches screenshot URLs suitable for downstream diffing operations.

Target Files

• packages/sdk/examples/ci-visual-testing/SKILL.md
• packages/sdk/examples/ci-visual-testing/README.md
• packages/sdk/examples/ci-visual-testing/scripts/ci-runner.ts

Boundary Rules

Restrict your modifications exclusively to the files listed in the Target Files section. Ensure your source changes are entirely backward-compatible if unowned tests outside your boundary fail. Retain all existing file names and locations outside your explicitly declared target list.

---

Fleet Context

• Source: jules:session:13713548963527251485
• Link: https://jules.google.com/session/13713548963527251485