fix(tasks): guard loop name length and surface loop ownership in the UI

Review follow-up:

- Reject loop files whose frontmatter name exceeds MAX_TASK_NAME_LENGTH
  (80): task names are clamped at storage time, so a raw name longer than
  the limit could never match the stored task identity. The file is treated
  as malformed (definition: null) instead of creating an unreachable
  definition; MAX_TASK_NAME_LENGTH is now exported from project-config.js
  and shared with loops.js.
- Surface loop-sourced tasks in the scheduled-tasks dialog: tasks carrying
  loopFile show a 'Managed by loop file <path>' note, and the enable
  toggle / edit / delete actions are disabled with an explanatory tooltip,
  since the file remains authoritative and would revert any such change.
  run-now stays available. New locale keys added to all 11 message files
  (i18n parity test enforces exact key sets).
- ScheduledTask type gains an optional loopFile field (additive, unknown
  to older clients).

packages/ui/src/lib/i18n/messages/uk.ts

@@ -269,6 +269,9 @@ export const dict: Record<I18nKey, string> = {
   "sessions.scheduledTasks.dialog.taskToggle.pauseAria": "Призупинити {taskName}",
   "sessions.scheduledTasks.dialog.taskToggle.enabled": "Увімкнено",
   "sessions.scheduledTasks.dialog.taskToggle.paused": "Призупинено",
+  'sessions.scheduledTasks.dialog.loopFile.note': 'Керується файлом циклу {file}',
+  'sessions.scheduledTasks.dialog.loopFile.toggleDisabled': 'Активність контролюється файлом циклу; встановіть enabled у frontmatter Markdown',
+  'sessions.scheduledTasks.dialog.loopFile.actionsDisabled': 'Завдання циклів налаштовуються у файлі Markdown .agents/loops',
   "sessions.scheduledTasks.editor.title.edit": "Редагувати заплановане завдання",
   "sessions.scheduledTasks.editor.title.new": "Нове заплановане завдання",
   "sessions.scheduledTasks.editor.description": "Налаштувати завдання на стороні сервера, яке створює нову сесію і надсилає запит.",