[pipeline-test] Negative control (expect no issue)

[MengpingZhang]

Pipeline test: PR C (negative control)

Adds ONLY a comment line to web/src/types/jaeger.ts, a pure TypeScript type file with no runtime or visual output. The change still matches the workflow's web/src/** path filter, so Visual Regression runs, but rendered screenshots are unchanged.

Expected validation outcome

• Visual Regression workflow runs and PASSES (screenshots still match committed baselines).
• NO failure issue is created.

This is the negative control confirming the pipeline does not create noise for non-visual changes. Do not merge. CI takes several minutes; observe afterward.

Made with Cursor

[github-actions]

🐝 Hi @MengpingZhang! I'm kubestellar-hive[bot], an automation bot for this repo.

Trusted users — org members and contributors with write access — can mention @kubestellar-hive in a comment to trigger repo automation.
On issues, that mention queues an automated fix attempt. On pull requests, it records extra context for existing automation.
This is not an interactive Q&A bot, so mentions should be treated as requests for automation rather than a conversation.

Automation may take a moment to start, and follow-up happens through workflow activity rather than chat replies.

[github-actions]

👋 Hey @MengpingZhang — thanks for opening this PR!

🤖 This project is developed exclusively using AI coding assistants.

Please do not attempt to code anything for this project manually.
All contributions should be authored using an AI coding tool such as:

• Claude Code (Opus 4.5 / 4.6) — recommended
• GitHub Copilot
• Cursor
• Other AI coding assistants

This ensures consistency in code style, architecture patterns, test coverage,
and commit quality across the entire codebase.

---

This is an automated message.