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/api/taskstream.schema.ts

@@ -950,7 +950,10 @@ export interface paths {
         };
         get?: never;
         put?: never;
-        /** Archive a planned release (its tickets leave it) */
+        /**
+         * Archive a planned release
+         * @description Its unfinished tickets move to `moveTo` (an open release of the same project) or leave it.
+         */
         post: operations["ReleasesController_archive"];
         delete?: never;
         options?: never;
@@ -2332,6 +2335,13 @@ export interface components {
              */
             markdown: string;
         };
+        ArchiveReleaseDto: {
+            /**
+             * Format: uuid
+             * @description Open release of the same project that takes its unfinished tickets; null or absent: they leave it
+             */
+            moveTo?: string | null;
+        };
         ShowcaseProjectDto: {
             /** Format: uuid */
             id: string;
@@ -7225,7 +7235,11 @@ export interface operations {
             };
             cookie?: never;
         };
-        requestBody?: never;
+        requestBody: {
+            content: {
+                "application/json": components["schemas"]["ArchiveReleaseDto"];
+            };
+        };
         responses: {
             200: {
                 headers: {