feat(flaky-unit-test-analysis): enhance suggestedFix schema and update task prompt

- Updated the `suggestedFix` field in `finalize-schema.json` to include a description for formatting TypeScript snippets.
- Modified `task-prompt.md` to clarify that `suggestedFix` must be a properly formatted code snippet, ensuring no prose is included.
- Refactored `flaky-sticky-comment.ts` to handle multi-line suggested fixes correctly, preserving indentation and formatting in the output.
- Introduced support for dynamic window counts in the history table, improving the representation of flaky test data.

Author: NicolasMassart

.ai-pr-analyzer/modes/flaky-unit-test-analysis/finalize-schema.json

@@ -35,7 +35,10 @@
           },
           "snippet": { "type": "string" },
           "explanation": { "type": "string" },
-          "suggestedFix": { "type": "string" },
+          "suggestedFix": {
+            "type": "string",
+            "description": "The corrected code snippet ONLY, formatted as real TypeScript with line breaks (use \\n between lines and preserve indentation). Do NOT write prose sentences here — keep all explanation in the `explanation` field."
+          },
           "historicalHintUsed": { "type": "boolean" }
         },
         "required": [

.ai-pr-analyzer/modes/flaky-unit-test-analysis/task-prompt.md

@@ -18,6 +18,7 @@ For each file:
 3. Check .ai-pr-analyzer/flaky-history.json (read_file) for a historical hint on this file.
 4. Match against the J1-J10 patterns from the loaded skill.
 5. For every match, record: file, line, patternId, patternName, severity, snippet, explanation, suggestedFix, and whether the historical hint was used.
+   - `suggestedFix` MUST be the corrected code snippet ONLY, formatted as real TypeScript with actual line breaks (`\n`) and indentation — never a single-line prose paragraph. Keep all reasoning and instructions in `explanation`.
 
 If a file has no matches, do not invent findings — omit it from findings.
 

.github/scripts/flaky-sticky-comment.ts

@@ -118,8 +118,14 @@ function buildFindingsSection(findings: Finding[]): string {
       const hint = f.historicalHintUsed ? ' _(matches historical failure signal)_' : '';
       out += `- **${f.patternId} — ${f.patternName}** (${f.severity})${hint}${f.line ? ` — line ${f.line}` : ''}\n`;
       out += `  - ${f.explanation}\n`;
-      // Fenced block so multi-line fixes render correctly in GitHub Markdown.
-      out += `  - Suggested fix:\n    \`\`\`ts\n    ${f.suggestedFix}\n    \`\`\`\n`;
+      // Every line of the fix must carry the 4-space indent that keeps the
+      // fenced block nested inside this list item; indenting only the first
+      // line would push the rest out of the list and collapse the code block.
+      const indentedFix = f.suggestedFix
+        .split('\n')
+        .map((line) => `    ${line}`)
+        .join('\n');
+      out += `  - Suggested fix:\n    \`\`\`ts\n${indentedFix}\n    \`\`\`\n`;
     }
     out += '\n';
   }