fix(frontend): prevent value loss when changing argument category to template

When editing an argument in the MCP catalog Configuration Schema step and
changing its category from team/user to template, the argument value would
disappear and become uneditable, causing the table to display empty cells.

This fix adds:
- Value input field in ConfigItemModal with conditional visibility
- Auto-population logic that sets value=name when changing to template
- Validation to ensure template items have required values
- Enhanced i18n translations for value field help text and placeholders

The watcher automatically fills the value field when switching to template
category while still allowing manual editing for cases where the value
differs from the name (e.g., package-name vs @org/package).

Author: Lasim

services/frontend/src/components/admin/mcp-catalog/steps/ConfigurationSchemaStepAdd.vue

@@ -742,6 +742,13 @@ const validateForm = () => {
     }
   }
 
+  // Validate value field for template items
+  if (formDataLocal.value.category === 'template') {
+    if (!formDataLocal.value.value || !formDataLocal.value.value.trim()) {
+      errors.value = t('mcpCatalog.form.configurationSchema.modal.validation.valueRequired')
+    }
+  }
+
   formErrors.value = errors
   return Object.keys(errors).length === 0
 }
@@ -984,6 +991,32 @@ watch(localData, () => {
     })
   }
 }, { deep: true })
+
+// Watch for category changes to auto-populate value for template arguments
+watch(() => formDataLocal.value.category, (newCategory, oldCategory) => {
+  // When changing TO template category
+  if (newCategory === 'template' && oldCategory !== 'template') {
+    // For arguments: auto-populate value with name if value is empty
+    if (formDataLocal.value.type === 'arg' && !formDataLocal.value.value) {
+      formDataLocal.value.value = formDataLocal.value.name
+    }
+    // For env/headers/query params: keep existing value or leave empty for user to fill
+
+    // Always lock template items by default
+    formDataLocal.value.locked = true
+  }
+
+  // When changing FROM template to team/user
+  if (oldCategory === 'template' && newCategory !== 'template') {
+    // Unlock the item (team/user items can be unlocked)
+    formDataLocal.value.locked = false
+
+    // For arguments: clear the value (team/user args don't need pre-filled values)
+    if (formDataLocal.value.type === 'arg') {
+      formDataLocal.value.value = ''
+    }
+  }
+})
 </script>
 
 <template>

services/frontend/src/components/admin/mcp-catalog/steps/ConfigurationSchemaStepAdd/ConfigItemModal.vue

@@ -111,6 +111,43 @@ const updateFormField = (field: keyof ConfigItem, value: any) => {
           </div>
         </div>
 
+        <!-- Value Field (for template items and editing) -->
+        <div v-if="formData.category === 'template' || formData.type === 'arg'" class="space-y-2">
+          <Label for="item-value">
+            {{ $t('mcpCatalog.form.configurationSchema.modal.fields.value.label') }}
+            <span v-if="formData.category !== 'template'" class="text-muted-foreground text-xs ml-2">
+              ({{ $t('mcpCatalog.form.configurationSchema.modal.fields.value.optionalForTeamUser') }})
+            </span>
+          </Label>
+          <Input
+            id="item-value"
+            :model-value="formData.value"
+            @update:model-value="(value) => updateFormField('value', value)"
+            :placeholder="
+              formData.type === 'arg'
+                ? $t('mcpCatalog.form.configurationSchema.modal.fields.value.placeholderArg')
+                : formData.type === 'env'
+                  ? $t('mcpCatalog.form.configurationSchema.modal.fields.value.placeholderEnv')
+                  : formData.type === 'header'
+                    ? $t('mcpCatalog.form.configurationSchema.modal.fields.value.placeholderHeader')
+                    : $t('mcpCatalog.form.configurationSchema.modal.fields.value.placeholderQueryParam')
+            "
+            :class="{ 'border-destructive': formErrors.value }"
+            class="font-mono"
+            :required="formData.category === 'template'"
+          />
+          <div v-if="formErrors.value" class="text-sm text-destructive">
+            {{ formErrors.value }}
+          </div>
+          <p class="text-sm text-muted-foreground">
+            {{
+              formData.category === 'template'
+                ? $t('mcpCatalog.form.configurationSchema.modal.fields.value.helpTextTemplate')
+                : $t('mcpCatalog.form.configurationSchema.modal.fields.value.helpTextTeamUser')
+            }}
+          </p>
+        </div>
+
         <!-- Category -->
         <div class="space-y-2">
           <Label for="item-category">{{ $t('mcpCatalog.form.configurationSchema.modal.fields.category.label') }}</Label>

services/frontend/src/i18n/locales/en/mcp-catalog.ts

@@ -305,7 +305,14 @@ export default {
           },
           value: {
             label: 'Value',
-            placeholder: 'Example: --verbose or package-name'
+            optionalForTeamUser: 'optional for team/user items',
+            placeholder: 'Enter value',
+            placeholderArg: 'e.g., -y, --transport, stdio',
+            placeholderEnv: 'e.g., 1.0, production, true',
+            placeholderHeader: 'e.g., application/json, Bearer token',
+            placeholderQueryParam: 'e.g., api-key-value, true',
+            helpTextTemplate: 'This value will be locked and passed to the MCP server at runtime',
+            helpTextTeamUser: 'Optional: Set a default value for this configuration item'
           },
           category: {
             label: 'Category',
@@ -334,7 +341,7 @@ export default {
         validation: {
           nameRequired: 'Name is required',
           nameExists: 'Name already exists for this type',
-          valueRequired: 'Value is required for template arguments'
+          valueRequired: 'Value is required for template items'
         }
       }
     },