feat: automation rules

Owners and admins can set rules of the kind «when a ticket is created,
moves, gets assigned, gets a comment or its pull request merges; if it is
of this type, priority, area or label; then move it, assign it, label it,
change its priority, comment or put it in the active sprint». Rules act as
TaskStream within the workflow, run once per event and trigger no others.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

libs/api/tracker/presenters/src/lib/graphql/enums.ts

@@ -1,5 +1,9 @@
 import { registerEnumType } from '@nestjs/graphql';
-import { IssueSort } from '@task-stream/api/tracker/application';
+import {
+  AutomationActionKind,
+  AutomationTriggerKind,
+  IssueSort,
+} from '@task-stream/api/tracker/application';
 import {
   IssueLinkType,
   IssuePriority,
@@ -33,6 +37,14 @@ registerEnumType(SprintStatus, {
   description: 'PLANNED, ACTIVE (one per project at a time) or CLOSED',
 });
 registerEnumType(LinkDirection, { name: 'LinkDirection' });
+registerEnumType(AutomationTriggerKind, {
+  name: 'AutomationTrigger',
+  description: 'What starts a rule',
+});
+registerEnumType(AutomationActionKind, {
+  name: 'AutomationAction',
+  description: 'What a rule does to the ticket',
+});
 registerEnumType(IssueSort, {
   name: 'IssueSort',
   description: 'RECENT: last updated first. RANK: backlog order.',