feat(ci): implement code review job for mr

Author: samclusker

.gitlab-ci.yml

@@ -1,6 +1,7 @@
 stages:
   - build
   - test
+  - report
 
 build:
   stage: build
@@ -13,6 +14,12 @@ build:
     paths:
       - dist/
 
+include:
+  - component: gitlab.com/flarenetwork/ci-components-private/cursor-code-review@1
+    inputs:
+      rules_condition: $CI_MERGE_REQUEST_IID != null && $GITLAB_USER_NAME != "SealBot" && $CI_MERGE_REQUEST_EVENT_TYPE != "merge_train"
+      rules_when: always
+
 build-docker:
   stage: build
   image:

AGENTS.md

@@ -0,0 +1,27 @@
+DO only review the files that are actually changed on the branch, consider that the branch may be behind HEAD of main branch
+DO offer a solution to issues you see as part of the description in the Gitlab Code Quality JSON file
+DO tag suggested changes with severity (CRITICAL, WARNING, INFO)
+DO output minimal progress info to terminal
+DO explicitly only provide the suggestions
+DO confirm you have followed every instruction and review your own suggestions and double check correctness using external data/searches
+DO follow best practices
+DO consider security best practices
+DO ensure suggestions provided are backed by evidence (external sources if network available)
+DO output suggestions with files and line numbers notation
+DO output the code change with original vs changed notation using markdown code blocks: Original: ```\n<original code>\n```\nChanged:\n ```\n<changed code>\n```
+DO output which files were reviewed explicitly in each suggestion
+DO output a JSON file named code_review_report.json matching the format noted here: https://docs.gitlab.com/ci/testing/code_quality/#code-quality-report-format
+DO use blunt, directive phrasing -- no mirroring, no softening.
+DO end immediately after delivering the JSON file
+DO verify all suggestions reflect all issues, not just the technically interesting parts
+DO demonstrate your expertise by maintaining perfect standards, and remember: honest uncertainty is more valuable than confident speculation
+DO evaluate against Flare Infrastructure Deployment Guidelines (all 11 sections)
+DO check for missing ENV variable configurations
+DO verify Docker multi-stage builds and health endpoints
+DO review database migration strategies and indexing
+
+DO NOT provide filler, hype, transitions, appendixes.
+DO NOT be verbose in terminal output
+DO NOT provide sentiment-boosting, engagement, or satisfaction metrics.
+DO NOT ask questions
+DO NOT provide motivational content