feat: show criticalityReason context for safe schema changes based on usage

[jenishasubedi05]

Background

Closes #6892

When a schema change is marked as "safe" due to conditional breaking change settings (usage threshold or client exclusion), the schema check view gives no explanation of why. Developers have to manually cross-reference the target's Conditional Breaking Changes configuration to understand why a change passed.

Description

This PR surfaces the existing criticalityReason field through to the frontend UI.

Changes:

• packages/services/api/src/modules/schema/providers/inspector.ts — Added reason: change.criticality.reason to pass the criticality reason through the model
• packages/web/app/src/components/target/history/errors-and-changes.tsx — Added criticalityReason to both GraphQL fragments and displays it inline next to "Safe based on usage data" in the schema check results view

Checklist

• Tests added/updated
• pnpm graphql:generate run after GraphQL changes
• No breaking changes

[gemini-code-assist]

Code Review

This pull request introduces support for Windows path separators in build scripts, adds the criticalityReason field to the schema changes UI, configures a named volume for ClickHouse in Docker Compose, and updates dependency configurations. However, several issues need to be addressed: temporary bundled .mjs files containing local absolute paths should be removed, the prebuild script skip in package.json should be reverted, JSX whitespace and indentation in errors-and-changes.tsx should be cleaned up, and the Byte Order Mark (BOM) in schema-v1.graphql must be removed to avoid parsing errors.

Important

The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.

[gemini-code-assist]

These bundled .mjs files (e.g., dev.config.node.bundled_*.mjs) appear to be temporary build artifacts generated during development. They contain hardcoded local absolute paths (e.g., C:\\Users\\College\\Desktop\\console...) and should not be committed to the repository. Please remove these files and ensure they are covered by .gitignore.

[gemini-code-assist]

Changing the "prebuild" script to "echo skip" disables the cleanup of deploy-tmp directories. This can lead to stale build artifacts or bloated deployments. Please revert this change or explain why it is necessary.

Suggested change

	"prebuild": "echo skip",
	"prebuild": "rimraf deploy-tmp && rimraf packages/**/deploy-tmp",

[gemini-code-assist]

Clean up the indentation of the closing </span> tag and remove the unnecessary empty lines/whitespace added within the JSX block to keep the code clean and maintainable.

Suggested change

	{change.isSafeBasedOnUsage && change.criticalityReason && (
	<span className="text-xs text-muted-foreground ml-1">
	({change.criticalityReason})
	</span>
	)}
	{change.isSafeBasedOnUsage && change.criticalityReason && (
	<span className="text-xs text-muted-foreground ml-1">
	({change.criticalityReason})
	</span>
	)}

[gemini-code-assist]

The file starts with a Byte Order Mark (BOM) character (\ufeff). UTF-8 BOMs are discouraged as they can cause parsing issues with some GraphQL tools and CLI parsers. Please save the file as standard UTF-8 without BOM.

Suggested change

	type Query {
	hello: String
	legacyField: String
	}
	type Query {
	hello: String
	legacyField: String
	}

[jenishasubedi05]

Hi! I've addressed all the review feedback from the bot:

• Removed the temporary bundled .mjs build artifacts
• Reverted the prebuild script change in package.json
• Fixed indentation in errors-and-changes.tsx
• Removed schema-v1.graphql test file

Ready for another look when you have time!

[jonathanawesome]

Thanks for the contribution, and for addressing the bot's earlier feedback! Good feature idea. A few things to sort out before it can go in.

Blocker: the import line in errors-and-changes.tsx reads AccordionItem,2 (stray 2).

Use severityReason instead. criticalityReason is deprecated in favor of severityReason, and both resolve to the same backend value. This component already fetches and renders severityReason, so you can build the same UI from it without adding a new fragment field. That should shrink the change down to roughly just the new <span>.

A question on the other changes: five of the six files aren't related to this feature, and they look like Windows/Docker workarounds: the ClickHouse named-volume swap in docker-compose.dev.yml, plus the path-separator and fileURLToPath tweaks in vite.config.ts, runify.ts, build-example.mjs, and server/index.ts. Are you on Windows and running into issues getting Console working locally? If so, these fixes could be genuinely useful, but we'd like them in a separate PR dedicated to Windows dev support so we can review them properly. Could you pull them out of this one?

Minor: clean up the leftover blank lines after the new <span> and in the fragment. Also, the description references inspector.ts, which isn't in the diff.

Since this is a UI change, could you also add before/after screenshots to the PR description? That makes it much easier to review the visual result.

Happy to re-review once the scope is trimmed. Thanks again!