feat: move unfinished tickets between releases

- Bulk editing gets «Release…» (open releases or none), and the list
  view a release filter, also reachable from each release («Ver en la
  lista», ?release=).
- Archiving a release asks where its unfinished tickets go, as closing
  a sprint does: ReleaseArchivedEvent carries `moveTo` (an open release
  of the same project, or none) and the saga moves them there; finished
  ones stay. In GraphQL, REST and the MCP's archive_release.
- Chapter 10 lists the next features and the ideas to weigh.

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

apps/mcp/src/app/tools/releases.resolver.ts

@@ -188,15 +188,26 @@ export class ReleasesResolver {
   @Tool({
     name: 'archive_release',
     description:
-      'Archive a planned release that will not ship; its tickets leave it.',
-    paramsSchema: z.object({ releaseId }),
+      'Archive a planned release that will not ship. Its unfinished tickets move to moveTo (another open release of the project, from list_releases) or, without it, leave it.',
+    paramsSchema: z.object({
+      releaseId,
+      moveTo: z
+        .string()
+        .uuid()
+        .optional()
+        .describe('Open release that takes the unfinished tickets'),
+    }),
     annotations: { readOnlyHint: false, destructiveHint: true },
   })
-  archive({ releaseId }: { releaseId: string }, ctx: McpContext) {
+  archive(
+    { releaseId, moveTo }: { releaseId: string; moveTo?: string },
+    ctx: McpContext,
+  ) {
     return toolResult(() =>
       this.api.data(
         this.api.as(ctx).POST('/api/releases/{releaseId}/archive', {
           params: { path: { releaseId } },
+          body: { moveTo: moveTo ?? null },
         }),
       ),
     );