feat: templates per ticket type

Each ticket type can carry a starting description and a checklist, edited
in the project settings. New tickets of that type get the description
when they come without one and always get the checklist; the new ticket
form says what the template will add.

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

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

@@ -548,6 +548,21 @@ export class StatusTransitionsInput {
   to!: string[];
 }
 
+@InputType('IssueTemplateInput')
+export class IssueTemplateInput {
+  @Field(() => String, { nullable: true })
+  @IsOptional()
+  @IsString()
+  @MaxLength(5000)
+  description?: string | null;
+  @Field(() => [String], { defaultValue: [] })
+  @IsArray()
+  @ArrayMaxSize(20)
+  @IsString({ each: true })
+  @MaxLength(300, { each: true })
+  checklist!: string[];
+}
+
 @InputType()
 export class IssueTypeOptionInput {
   @Field() @Matches(SETTING_ID) id!: string;
@@ -555,6 +570,11 @@ export class IssueTypeOptionInput {
   @Field() @IsString() icon!: string;
   @Field() @IsString() color!: string;
   @Field({ defaultValue: false }) @IsBoolean() archived!: boolean;
+  @Field(() => IssueTemplateInput, { nullable: true })
+  @IsOptional()
+  @ValidateNested()
+  @Type(() => IssueTemplateInput)
+  template?: IssueTemplateInput | null;
 }
 
 @InputType()