feat: start a project from another one's configuration

Creating a project can name one the creator owns or administers: its
statuses, transitions, types, areas, custom fields and automation rules
are copied once (paused rules stay paused; rules assigning to someone who
is not in the new project are left out). GraphQL templateProjectId, REST
template (id or key), MCP create_project template, and a select in the
web's new-project form.

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

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

@@ -55,6 +55,15 @@ export class CreateProjectInput {
   @IsOptional()
   @IsBoolean()
   isPublic?: boolean;
+
+  @Field(() => ID, {
+    nullable: true,
+    description:
+      'A project you own or administer to start from: its statuses, transitions, types, areas, custom fields and automation rules are copied',
+  })
+  @IsOptional()
+  @IsUUID()
+  templateProjectId?: string | null;
 }
 
 @InputType()

libs/api/tracker/presenters/src/lib/graphql/project.resolver.ts

@@ -151,7 +151,11 @@ export class ProjectResolver {
     @CurrentUser() me: User,
     @Args('input') input: CreateProjectInput,
   ) {
-    return this.projects.create(me.id, input);
+    const { templateProjectId, ...fields } = input;
+    return this.projects.create(me.id, {
+      ...fields,
+      templateId: templateProjectId,
+    });
   }
 
   @Mutation(() => CommandResultGql)