>>> [!note] Migrated issue <!-- Drupal.org comment --> <!-- Migrated from issue #3636054. --> Reported by: [ai_yas](https://www.drupal.org/user/3871472) Related to !1 >>> <p>Prepared with AI assistance and reviewed against the Recipe behavior and installation tests.</p> <h3>Current status</h3> <p>The implementation is available in <a href="https://git.drupalcode.org/project/ai_code_review/-/merge_requests/1">MR!1</a>, targeting <code>1.x</code>. <a href="https://git.drupalcode.org/issue/ai_code_review-3636054/-/pipelines/1035916">Public CI</a> passed all seven automatic jobs. The Functional suite executed two tests and 40 assertions with no failures or skipped tests on <code>PHP 8.3.36</code> and <code>Drupal 11.4.12</code>. MR!1 was squash-merged into <code>1.x</code> as <code>8912b462c3f51b752ad0a70b5723e17f76805296</code> after review and approval by <code>yas</code>. The accepted commit message and file tree match the reviewed candidate. <a href="https://git.drupalcode.org/project/ai_code_review/-/pipelines/1035918">Post-merge CI</a> also passed all seven automatic jobs and the two Functional tests with 40 assertions. <a href="https://new.drupal.org/contribution-record/11495411">Credits</a> are saved for <code>yas</code> and <code>ai_yas</code>. <a href="https://www.drupal.org/project/ai_code_review/releases/1.0.0-alpha1">Recipe 1.0.0-alpha1</a> is published. Both advertised archives have been inspected; their seven files match the accepted source except packaging-only LICENSE heading whitespace. The Composer distribution matches all seven accepted files exactly.</p> <h3>Problem/Motivation</h3> <p>Site builders need a repeatable way to prepare an AI Code Review UI site and connect it to a separate AI Code Review Server site.</p> <h3>Proposed resolution</h3> <ul> <li>Add the <code>drupal/ai_code_review</code> Recipe for <code>Drupal 11.4</code> and UI <code>1.x</code>.</li> <li>Install the UI module only. Create a dedicated reviewer role with Add, View, and List permissions, preserving existing role properties and unrelated permissions.</li> <li>Document that View access covers reviews across the UI site. Leave edit, delete, administration, and optional cancellation permissions to the site administrator.</li> <li>Document separate Server installation, HTTPS, authentication, provider registration, and connection setup without including credentials or deployment-specific URLs.</li> <li>Add functional Recipe application tests and standard Drupal CI.</li> </ul> <h3>Release follow-up</h3> <ul> <li>Published package and normal Composer installation verification are complete. Application and reapplication on clean and configured sites passed, including existing role and connection-setting preservation.</li> <li>Separate-site verification found missing default policy and review-list configuration on fresh Recipe installations. Functional release acceptance remains incomplete until <span class="drupalorg-gitlab-issue-link project-issue-status-info project-issue-status-2"><a href="https://www.drupal.org/project/ai_code_review/issues/3636118" title="Status: Fixed">#3636118: Fix UI configuration imports during Recipe application</a></span> is resolved and verified. The published alpha tag remains unchanged.</li> </ul> <h3>Local validation</h3> <p>On a fresh <code>Drupal 11.4.12</code> site with the published UI <code>1.0.0-alpha1</code>, Recipe application and reapplication succeeded. Two functional tests passed with 40 assertions. Existing site configuration and role properties were preserved. The documented Composer command succeeded with both alpha packages explicitly required, without lowering global minimum stability. PHP syntax and Drupal coding checks passed. Eight dependency deprecation notices remain; no provider API calls were made. Public CI also passed on PHP 8.3. These pre-release results are distinct from the published-package checks recorded above.</p>