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).

This commit is contained in:

makeittech

2026-08-06 09:38:18 +03:00

parent 359225d363

commit 59a6c1b70d

17 changed files with 96 additions and 7 deletions

									
										packages/web/server/lib/projects/project-config.js
									
		+1
		-1
	
												View File
												
				@@ -2,7 +2,7 @@ import { DateTime, IANAZone } from 'luxon';

				import parser from 'cron-parser';

				const PROJECT_CONFIG_VERSION = 1;

				const MAX_TASK_NAME_LENGTH = 80;

				export const MAX_TASK_NAME_LENGTH = 80;

				const MAX_TASK_PROMPT_LENGTH = 20_000;

				const MAX_CRON_LENGTH = 200;

				const MAX_LAST_ERROR_LENGTH = 2_000;