When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

• UI deployment: https://agents-manage-gakl6pm4w.preview.inkeep.com
• API deployment: https://agents-711zr52je.preview.inkeep.com

• What failed: The app returns HTTP 500 instead of rendering the login page because compile-time transform/parser errors occur in UI source files.
• Impact: Users cannot access login, project settings, or agent pages in the manage UI when this build is deployed with the same compiler settings. This is a full UI availability break for core management workflows.
• Steps to reproduce:
  1. Start the local development services for manage UI and API on localhost.
  2. Open http://localhost:3000/login in the browser.
  3. Observe the HTTP 500 response and compile-time errors referencing model-configuration.tsx and output-schema-filters.tsx.
• Stub / mock context: A local developer auth/bootstrap flow and seeded viewer/project/agent data were used to exercise the permission scenario on localhost, but no fake route responses or UI-level behavior stubs were used for the observed 500 failure.
• Code analysis: I reviewed the compiler config patch and the referenced failing UI modules. The PR enables enableJsxOutlining by default in the React compiler patch, and the failing files include TSX patterns now reported as transform/parser failures, which aligns with a real code regression rather than a mocked response or bypassed assertion path.
• Why this is likely a bug: The failure is caused by deterministic compile-time errors in shipped UI source/configuration, so the application cannot serve core routes and this cannot be explained by test-only mocks or environment stubbing.

Relevant code:

patches/babel-plugin-react-compiler.patch (lines 27-33)

@@ -84356,7 +84356,7 @@ var EnvironmentConfigSchema = external_exports.object({
   * With this change, when `countries` is updated by adding one single value,
   * only the newly added value is re-rendered and not the entire list.
   */
-  enableJsxOutlining: external_exports.boolean().default(false),
+  enableJsxOutlining: external_exports.boolean().default(true),
  /*

agents-manage-ui/src/components/shared/model-configuration.tsx (lines 31-37)

const AllowedProvidersSection: FC<{
  allowedProviders?: string[];
  inheritedAllowedProviders?: string[];
  onAllowedProvidersChange: (providers: string[]) => void;
  disabled: boolean;
}> = ({ allowedProviders, inheritedAllowedProviders, onAllowedProvidersChange, disabled }) => {

agents-manage-ui/src/components/evaluation-jobs/output-schema-filters.tsx (lines 101-117)

{filters.map((filter, index) => (
  <div key={index} className="flex gap-2 items-center">
    <div className="flex-1 min-w-[200px]">
      <Select
        value={filter.key || 'none'}
        onValueChange={(value) =>
          updateFilter(index, 'key', value === 'none' ? '' : value)
        }
      >
        <SelectTrigger className="bg-background">
          <SelectValue placeholder="Select field" />
        </SelectTrigger>

• What failed: The shared model configuration path is affected by compiler transform failures, so fallback controls cannot be trusted as a stable executable path in the baseline build.
• Impact: Fallback model management is blocked or unstable in affected settings pages, preventing reliable resilience configuration. This can delay safe rollout of model failover behavior for projects.
• Steps to reproduce:
  1. Navigate to /default/projects//settings and expand Configure default models.
  2. Use Add fallback model, cancel, and add again, then save and reload.
  3. Observe that baseline runs are blocked by the same compiler regression on the shared model configuration path.
• Stub / mock context: The retry flow created a local test project and briefly ran with the React compiler disabled to probe fallback behavior, but baseline verification still showed the compiler regression blocking the original settings path.
• Code analysis: The fallback UI and handlers live in ModelConfiguration and are rendered behind the same route that crashes on compiler diagnostics. The PR’s compiler defaults change is a plausible root cause because disabling the compiler was used only as a temporary workaround during retries, while final verification still confirms baseline failure in the unmodified path.
• Why this is likely a bug: The route fails in baseline production code/configuration, so fallback workflow failure is attributable to a real app regression rather than just test orchestration.

Relevant code:

patches/babel-plugin-react-compiler.patch (lines 27-33)

@@ -84356,7 +84356,7 @@ var EnvironmentConfigSchema = external_exports.object({
    * With this change, when `countries` is updated by adding one single value,
    * only the newly added value is re-rendered and not the entire list.
    */
-  enableJsxOutlining: external_exports.boolean().default(false),
+  enableJsxOutlining: external_exports.boolean().default(true),
   /*

agents-manage-ui/src/components/shared/model-configuration.tsx (lines 248-262)

{showPendingSelector && (
  <div className="flex items-center gap-2">
    <span className="text-xs text-muted-foreground w-4 shrink-0">
      {savedModels.length + 1}.
    </span>
    <div className="flex-1">
      <ModelSelector
        value=""
        gatewayOnly
        defaultOpen
        onValueChange={(newValue) => {
          setShowPendingSelector(false);
          if (newValue) {
            onFallbackModelsChange([...(fallbackModels ?? []), newValue]);

agents-manage-ui/next.config.ts (lines 39-42)

reactCompiler: {
  // Fail the build on any compiler diagnostic
  panicThreshold: 'all_errors',
},

• What failed: The settings surface fails to render due to compile-time React/Babel errors, so rapid model switching cannot be executed; expected behavior is a successful render that allows model edits and save attempts.
• Impact: Project settings model configuration is blocked in this build, preventing admins from editing or validating model behavior in the UI. This also blocks downstream scenarios that depend on this route.
• Steps to reproduce:
  1. Open http://localhost:3000/default/projects and navigate to a project settings page.
  2. Expand the default model configuration UI so ModelConfiguration and related settings components render.
  3. Observe compile-time React/Babel errors and route render failure before rapid model switching can be executed.
• Stub / mock context: No feature-level mock data or route interception was used while reproducing this failure. The check exercised the live local compile path, where project settings failed before user interactions could proceed.
• Code analysis: The run fails in production code paths, not in a test stub: the PR enables enableJsxOutlining by default in the React compiler patch, and this build keeps compiler panics as hard failures. The failing route renders ModelConfiguration and related settings JSX, and the reported compile failures (including output-schema-filters.tsx) are consistent with compiler/codegen regressions after that config change.
• Why this is likely a bug: Valid project settings code is crashing under the enabled compiler configuration, and the route cannot render in normal app execution, which is a real product defect rather than test setup interference.

Relevant code:

patches/babel-plugin-react-compiler.patch (lines 27-33)

@@ -84356,7 +84356,7 @@ var EnvironmentConfigSchema = external_exports.object({
   * With this change, when `countries` is updated by adding one single value,
   * only the newly added value is re-rendered and not the entire list.
   */
-  enableJsxOutlining: external_exports.boolean().default(false),
+  enableJsxOutlining: external_exports.boolean().default(true),
  /*

agents-manage-ui/next.config.ts (lines 39-42)

reactCompiler: {
  // Fail the build on any compiler diagnostic
  panicThreshold: 'all_errors',
},

agents-manage-ui/src/components/shared/model-configuration.tsx (lines 96-116)

{effectiveProviders.map((provider, index) => (
  <li
    key={provider}
    className={cn(
      'flex items-center gap-2 px-3 py-2 transition-colors',
      index > 0 && 'border-t',
      dragOverId === provider ? 'bg-muted/30' : 'hover:bg-muted/30'
    )}
    draggable={!disabled && !isInherited}
    data-id={provider}
    onDragStart={(e) => setDraggingId(e.currentTarget.dataset.id as string)}
    onDragOver={(e) => {
      e.preventDefault();
      setDragOverId(e.currentTarget.dataset.id as string);
    }}

• What failed: The route crashes before the inherited/explicit controls render, so stale-provider-options clearing logic cannot execute at all.
• Impact: Teams cannot verify or apply inheritance-to-explicit model transitions in project defaults. This blocks a high-risk configuration path and leaves expected behavior untestable in the affected build.
• Steps to reproduce:
  1. Navigate to /default/projects//settings.
  2. Expand Configure default models.
  3. Attempt to reach the inherited model section and switch to an explicit model.
  4. Observe the compiler crash before controls render.
• Stub / mock context: No stubs, mocks, or bypasses were applied for this test in the recorded run.
• Code analysis: I traced LOGIC-1 to the same shared ModelConfiguration path used by project settings and confirmed the compiler pipeline is configured to fail hard on diagnostics. With JSX outlining enabled by the PR patch, transform diagnostics prevent the settings component tree from loading, which blocks LOGIC-1 before business logic runs.
• Why this is likely a bug: The feature path is blocked by a compiler regression in shipped source/configuration, not by test-only mocking or missing setup.

Relevant code:

patches/babel-plugin-react-compiler.patch (lines 27-33)

@@ -84356,7 +84356,7 @@ var EnvironmentConfigSchema = external_exports.object({
    * With this change, when `countries` is updated by adding one single value,
    * only the newly added value is re-rendered and not the entire list.
    */
-  enableJsxOutlining: external_exports.boolean().default(false),
+  enableJsxOutlining: external_exports.boolean().default(true),
   /*

agents-manage-ui/next.config.ts (lines 39-42)

reactCompiler: {
  // Fail the build on any compiler diagnostic
  panicThreshold: 'all_errors',
},

agents-manage-ui/src/components/projects/form/project-models-section.tsx (lines 56-66)

<ModelConfiguration
  value={field.value || ''}
  providerOptions={
    providerOptionsField.value ? JSON.stringify(providerOptionsField.value, null, 2) : ''
  }
  label=""
  placeholder="Select base model"
  canClear={false}
  isRequired={true}
  onModelChange={field.onChange}

• What failed: The route-level compilation failure prevents a stable render of the settings UI path, so ordering persistence behavior cannot be exercised in the normal product flow.
• Impact: Provider-priority ordering cannot be safely validated or configured through the project settings UI. This blocks a key fallback/routing control path for model traffic.
• Steps to reproduce:
  1. Navigate to /default/projects//settings and open Configure default models.
  2. Select a gateway-routable base model and switch to Specific providers mode.
  3. Attempt to perform drag-and-drop ordering and save.
  4. Observe compile/runtime instability on the settings route in baseline verification.
• Stub / mock context: During retries, the run temporarily disabled the React compiler and enabled local AI gateway capability flags to attempt the ordering workflow, then used baseline verification to confirm the original compiler regression remained the root defect.
• Code analysis: I reviewed both the failing settings component tree and the second file reported by diagnostics. Runtime compiler output reports duplicate declaration generation in output-schema-filters.tsx and parse failure in model-configuration.tsx under the enabled JSX outlining configuration, which supports a real code/config regression rather than a transient test harness issue.
• Why this is likely a bug: Multiple deterministic compiler diagnostics hit production components after this PR’s compiler config change, and they block the user flow before LOGIC-2 assertions can run.

Relevant code:

patches/babel-plugin-react-compiler.patch (lines 27-33)

@@ -84356,7 +84356,7 @@ var EnvironmentConfigSchema = external_exports.object({
    * With this change, when `countries` is updated by adding one single value,
    * only the newly added value is re-rendered and not the entire list.
    */
-  enableJsxOutlining: external_exports.boolean().default(false),
+  enableJsxOutlining: external_exports.boolean().default(true),
   /*

agents-manage-ui/src/components/evaluation-jobs/output-schema-filters.tsx (lines 101-107)

{filters.map((filter, index) => (
  <div key={index} className="flex gap-2 items-center">
    <div className="flex-1 min-w-[200px]">
      <Select
        value={filter.key || 'none'}
        onValueChange={(value) =>
          updateFilter(index, 'key', value === 'none' ? '' : value)

agents-manage-ui/src/components/shared/model-configuration.tsx (lines 103-106)

)}
draggable={!disabled && !isInherited}
data-id={provider}
onDragStart={(e) => setDraggingId(e.currentTarget.dataset.id as string)}

• What failed: The page throws compile-time transform errors and never renders model configuration controls, so users cannot save project model config.
• Impact: Project-level model configuration is unavailable until the compiler regression is fixed. This blocks saving and validating core model settings for admins.
• Steps to reproduce:
  1. Navigate to /default/projects//settings.
  2. Open Configure default models.
  3. Observe that the route fails with compiler transform errors instead of rendering the model configuration UI.
• Stub / mock context: No stubs, mocks, or bypasses were applied for this test in the recorded run.
• Code analysis: I reviewed the shared model configuration component import path used by the project settings route and the React compiler configuration. The PR enables JSX outlining in the compiler patch while reactCompiler remains active with panicThreshold: 'all_errors', and runtime errors show transform output breaking on hyphenated prop names plus duplicate declaration generation.
• Why this is likely a bug: The compiler configuration change in this PR introduces a deterministic transform failure in production code paths, and the settings route cannot render even before user interaction.

Relevant code:

patches/babel-plugin-react-compiler.patch (lines 27-33)

@@ -84356,7 +84356,7 @@ var EnvironmentConfigSchema = external_exports.object({
    * With this change, when `countries` is updated by adding one single value,
    * only the newly added value is re-rendered and not the entire list.
    */
-  enableJsxOutlining: external_exports.boolean().default(false),
+  enableJsxOutlining: external_exports.boolean().default(true),
   /*

agents-manage-ui/next.config.ts (lines 39-42)

reactCompiler: {
  // Fail the build on any compiler diagnostic
  panicThreshold: 'all_errors',
},

agents-manage-ui/src/components/shared/model-configuration.tsx (lines 125-135)

<Button
  variant="ghost"
  size="icon"
  className="h-7 w-7 shrink-0"
  onClick={() => {
    const next = (allowedProviders ?? []).filter((p) => p !== provider);
    onAllowedProvidersChange(next);
  }}
  disabled={disabled || isInherited}
  aria-label={`Remove ${providerLabel(provider)}`}
>

• What failed: The app fails to compile/render with source-level compiler errors, so the sub-agent model configuration UI never becomes usable; expected behavior is that the page renders and model settings can be saved and reloaded.
• Impact: Users cannot reach or use the sub-agent model configuration flow in Manage UI when this regression is present. This blocks model updates and validation for agent behavior.
• Steps to reproduce:
  1. Open http://localhost:3000/default/projects.
  2. Navigate to a project agent detail page (/default/projects//agents/).
  3. Open the sub-agent Models section and attempt to edit/save model settings.
  4. Observe compile/render failure instead of the editor loading.
• Stub / mock context: The run used development-only UI/runtime overrides (for example hiding dev overlays and relaxing dev compiler panic behavior) to keep local pages testable while reproducing this issue. No endpoint response stubs or route-level API mocks were applied to the failing sub-agent model flow itself.
• Code analysis: I reviewed the compiler configuration and affected UI modules. The PR enables JSX outlining in the patched React compiler, while Manage UI is configured to panic on compiler diagnostics; this combination aligns with the observed parse/transform failures in model-configuration.tsx and blocks rendering of the route that hosts sub-agent model editing.
• Why this is likely a bug: The failure is tied to production source and compiler settings in this branch, and the route cannot render before any test-only interaction could affect behavior.

Relevant code:

patches/babel-plugin-react-compiler.patch (lines 27-33)

@@ -84356,7 +84356,7 @@ var EnvironmentConfigSchema = external_exports.object({
    * With this change, when `countries` is updated by adding one single value,
    * only the newly added value is re-rendered and not the entire list.
    */
-  enableJsxOutlining: external_exports.boolean().default(false),
+  enableJsxOutlining: external_exports.boolean().default(true),
   /*
    * Enables instrumentation codegen. This emits a dev-mode only call to an

agents-manage-ui/next.config.ts (lines 39-42)

reactCompiler: {
  // Fail the build on any compiler diagnostic
  panicThreshold: 'all_errors',
},

agents-manage-ui/src/components/shared/model-configuration.tsx (lines 92-137)

{isSpecific && (
  <div className="space-y-2">
    <div className="border rounded-md text-xs">
      <ul>
        {effectiveProviders.map((provider, index) => (
          <li
            key={provider}
            className={cn(
              'flex items-center gap-2 px-3 py-2 transition-colors',
              index > 0 && 'border-t',
              dragOverId === provider ? 'bg-muted/30' : 'hover:bg-muted/30'
            )}
            draggable={!disabled && !isInherited}
            data-id={provider}
            onDragStart={(e) => setDraggingId(e.currentTarget.dataset.id as string)}
            onDragOver={(e) => {
              e.preventDefault();
              setDragOverId(e.currentTarget.dataset.id as string);
            }}
            onDragLeave={() => setDragOverId('')}
            onDrop={(e) => {
              handleReorder(draggingId, e.currentTarget.dataset.id as string);
              setDraggingId('');
              setDragOverId('');
            }}
            onDragEnd={() => {
              setDraggingId('');
              setDragOverId('');
            }}
          >
            <GripVertical className="size-4 text-muted-foreground shrink-0 cursor-grab" />
            <span className="text-xs text-muted-foreground w-4 shrink-0">{index + 1}.</span>
            <span className="text-sm grow">{providerLabel(provider)}</span>
            <Button
              variant="ghost"
              size="icon"
              className="h-7 w-7 shrink-0"
              onClick={() => {
                const next = (allowedProviders ?? []).filter((p) => p !== provider);
                onAllowedProvidersChange(next);
              }}
              disabled={disabled || isInherited}
              aria-label={`Remove ${providerLabel(provider)}`}
            >

• What failed: The route hits server/compiler failures (HTTP 500 with compile errors) instead of presenting a stable projects view and allowing navigation to the agent and Try it playground.
• Impact: Mobile users cannot reliably enter the projects-to-agent path, so a core navigation and playground workflow is blocked. The failure happens during app compilation/runtime and prevents normal product use.
• Steps to reproduce:
  1. Open the Manage UI in an authenticated session and set viewport size to 390x844.
  2. Navigate to /default/projects.
  3. Attempt to continue through project -> agent -> Try it flow and observe compile/runtime errors blocking progression.
• Stub / mock context: No stubs, mocks, or bypasses were applied for this test in the recorded run.
• Code analysis: I reviewed the compiler configuration change and both failing component paths. The PR enables JSX outlining by default in the React compiler patch, and current component patterns in model-configuration.tsx and output-schema-filters.tsx align with the reported transform failures (aria-label transform/parsing failure and duplicate declaration during map rendering), making this a production-code regression rather than test setup noise.
• Why this is likely a bug: The failure is reproducible on local app routes and backed by compile-time errors tied to committed source files after the compiler behavior change, so it reflects a real product regression.

Relevant code:

patches/babel-plugin-react-compiler.patch (lines 27-33)

@@ -84356,7 +84356,7 @@ var EnvironmentConfigSchema = external_exports.object({
   * With this change, when `countries` is updated by adding one single value,
   * only the newly added value is re-rendered and not the entire list.
   */
-  enableJsxOutlining: external_exports.boolean().default(false),
+  enableJsxOutlining: external_exports.boolean().default(true),
  /*

agents-manage-ui/src/components/shared/model-configuration.tsx (lines 31-37)

const AllowedProvidersSection: FC<{
  allowedProviders?: string[];
  inheritedAllowedProviders?: string[];
  onAllowedProvidersChange: (providers: string[]) => void;
  disabled: boolean;
}> = ({ allowedProviders, inheritedAllowedProviders, onAllowedProvidersChange, disabled }) => {
  const [addOpen, setAddOpen] = useState(false);

agents-manage-ui/src/components/evaluation-jobs/output-schema-filters.tsx (lines 101-118)

{filters.map((filter, index) => (
  <div key={index} className="flex gap-2 items-center">
    <div className="flex-1 min-w-[200px]">
      <Select
        value={filter.key || 'none'}
        onValueChange={(value) =>
          updateFilter(index, 'key', value === 'none' ? '' : value)
        }
      >
        <SelectTrigger className="bg-background">
          <SelectValue placeholder="Select field" />
        </SelectTrigger>
        <SelectContent>
          <SelectItem value="none">No filter</SelectItem>