fix: added explicit nudge on issues array

Author: jahilldev

api/src/review/review.prompts.spec.ts

@@ -24,7 +24,9 @@ describe('buildReviewPrompt parseRetry guidance', () => {
     expect(p).toContain('"PASS" or "FAIL"');
     expect(p).toContain('NOT a boolean');
     expect(p).toContain('`confidence` MUST be present');
-    expect(p).toContain('issues');
     expect(p).toContain('rationale'); // explicitly warns against this stray key
+    // `issues` is emphasised as the critical field — it is the only thing the fix stage receives.
+    expect(p).toContain('MOST IMPORTANT');
+    expect(p).toContain('ONLY thing passed to the engineer who fixes the code');
   });
 });

api/src/review/review.prompts.ts

@@ -93,7 +93,7 @@ If the server fails to start, skip the browser step and note it in your summary
         `- \`verdict\` MUST be the string "PASS" or "FAIL" (uppercase) — NOT a boolean (\`true\`/\`false\`), number, or any other word.\n` +
         `- \`confidence\` MUST be present, as an integer 0–100.\n` +
         `- \`dimensions\` MUST contain all four boolean keys: \`correctness\`, \`tests\`, \`planCoverage\`, \`security\`.\n` +
-        `- Put every finding inside the \`issues\` array using the exact \`{severity,title,detail,file?}\` shape — do NOT invent other keys (e.g. \`rationale\`, \`findings\`) for them. Free-form reasoning, if any, goes AFTER the closing \`\`\`.`,
+        `- MOST IMPORTANT — \`issues\`: every concrete problem MUST be a structured object in the \`issues\` array with the exact \`{severity,title,detail,file?}\` shape. This array is the ONLY thing passed to the engineer who fixes the code — any finding left out, written as prose, or placed under a stray key (\`rationale\`, \`findings\`, \`explanation\`, …) is INVISIBLE to the fix stage and WILL NOT be fixed. Each \`detail\` must say both what is wrong and how to fix it. Put a FAIL's full reasoning here, not after the block.`,
     );
   }