Enhance Qualitizer: Integration with Health Dashboard

[htnguyen19]

Why: the two tools overlap in intent (both watch CDF run health) but Project Health is a Streamlit+Function snapshot and Qualitizer runs on the newer Flows Framework. Rather than keep two codebases, I ported the high-value, low-effort pieces of Project Health into Qualitizer as a new Health Checks category.

What's in this PR:
• New Health Checks category: "Run Health"— per-resource uptime %, healthy/unhealthy/no-runs summary, and aggregated recent failures for extraction pipelines, workflows, transformations, and functions. Configurable uptime thresholds, persisted in localStorage.
• Global TimeRangeContext— 12h / 1d / 7d / 30d selector in the top bar, shared across views. Closes Qualitizer's fixed-1h-window limitation.
• Dataset filter — dropdown in the top bar, wired through a new DatasetFilterContext. Scopes Run Health panels (and gives other views a drop-in hook for future use).
• Transformations list — two new columns, Uptime 24h and S / F (successful / failed), so the existing list now surfaces the same signal as Project Health without needing a separate page.

[gemini-code-assist]

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize the Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counterproductive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for GitHub and other Google products, sign up here.