lang/no/gallery.php (1)

138-139: Localize new no strings to avoid mixed-language UI

Line 138 and Line 139 are still English in the Norwegian locale file, so users will see inconsistent language.

Proposed localization patch

-            'generate_slug' => 'Generate slug from title',
-            'copy_slug_url' => 'Copy URL to clipboard',
+            'generate_slug' => 'Generer slug fra tittel',
+            'copy_slug_url' => 'Kopier URL til utklippstavlen',

lang/ru/gallery.php (1)

136-138: New slug translation keys added; two strings remain in English.

Lines 137-138 contain English text ('Generate slug from title', 'Copy URL to clipboard') in this Russian translation file. Line 136 uses a hybrid approach with the technical term "Slug" followed by a Russian explanation, which is reasonable.

Given the existing pattern in this file (many other strings also remain untranslated), this is consistent with the current approach but may warrant localization in a future pass.

💬 Suggested Russian translations

             'slug' => 'Slug (дружественный URL)',
-            'generate_slug' => 'Generate slug from title',
-            'copy_slug_url' => 'Copy URL to clipboard',
+            'generate_slug' => 'Сгенерировать slug из названия',
+            'copy_slug_url' => 'Скопировать URL в буфер обмена',

Based on learnings: "The user ildyria does not prioritize strict localization consistency for new menu items in language files."

lang/it/gallery.php (1)

137-139: Translations are in English rather than Italian.

These new slug-related strings are in English. Consider translating them to Italian for consistency with the rest of the file:

• 'Slug (friendly URL)' → 'Slug (URL amichevole)'
• 'Generate slug from title' → 'Genera slug dal titolo'
• 'Copy URL to clipboard' → 'Copia URL negli appunti'

tests/Unit/Rules/SlugRuleTest.php (1)

31-43: Minor: Handle null values in assertion messages.

In assertPasses (line 35), concatenating a potentially null value will produce "Expected slug "" to pass..." which works but could be clearer. Consider using var_export($value, true) or a null-coalescing string for better debugging output.

💡 Optional improvement for clearer assertion messages

 private function assertPasses(SlugRule $rule, mixed $value): void
 {
     $failed = false;
     $rule->validate('slug', $value, function () use (&$failed): void { $failed = true; });
-    self::assertFalse($failed, 'Expected slug "' . $value . '" to pass but it failed.');
+    self::assertFalse($failed, 'Expected slug "' . var_export($value, true) . '" to pass but it failed.');
 }

 private function assertFails(SlugRule $rule, mixed $value): void
 {
     $failed = false;
     $rule->validate('slug', $value, function () use (&$failed): void { $failed = true; });
-    self::assertTrue($failed, 'Expected slug "' . $value . '" to fail but it passed.');
+    self::assertTrue($failed, 'Expected slug "' . var_export($value, true) . '" to fail but it passed.');
 }

tests/Unit/Http/AlbumSlugCrudTest.php (1)

98-378: Extract a reusable payload builder for album/tag-album patch requests.

The repeated full payload arrays across many tests increase maintenance drift risk when request fields change. A small helper (base payload + overrides) would keep these tests easier to update and less error-prone.

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro