Persist last_good outside the cache and bundle a static Cloudflare IP fallback

Author: ruerdev

.claude/skills/laravel-best-practices/SKILL.md

@@ -94,7 +94,7 @@ Check sibling files, related controllers, models, or tests for established patte
 ### 9. Queue & Job Patterns → `rules/queue-jobs.md`
 
 - `retry_after` must exceed job `timeout`; use exponential backoff `[1, 5, 10]`
-- `ShouldBeUnique` to prevent duplicates; `WithoutOverlapping::untilProcessing()` for concurrency
+- `ShouldBeUnique` to prevent duplicates; `ShouldBeUniqueUntilProcessing` for early lock release
 - Always implement `failed()`; with `retryUntil()`, set `$tries = 0`
 - `RateLimited` middleware for external API calls; `Bus::batch()` for related jobs
 - Horizon for complex multi-queue scenarios
@@ -187,4 +187,4 @@ Always use a sub-agent to read rule files and explore this skill's content.
 
 1. Identify the file type and select relevant sections (e.g., migration → §16, controller → §1, §3, §5, §6, §10)
 2. Check sibling files for existing patterns — follow those first per Consistency First
-3. Verify API syntax with `search-docs` for the installed Laravel version
+3. Verify API syntax with `search-docs` for the installed Laravel version

.claude/skills/laravel-best-practices/rules/advanced-queries.md

@@ -103,4 +103,4 @@ public function scopeOrderByLastLogin($query): void
         ->take(1)
     );
 }
-```
+```

.claude/skills/laravel-best-practices/rules/architecture.md

@@ -82,7 +82,7 @@ $this->app->bind(PaymentGateway::class, StripeGateway::class);
 
 ## Default Sort by Descending
 
-When no explicit order is specified, sort by `id` or `created_at` descending. Explicit ordering prevents cross-database inconsistencies between MySQL and Postgres.
+When no explicit order is specified, sort by `id` or `created_at` descending. Without an explicit `ORDER BY`, row order is undefined.
 
 Incorrect:
 ```php
@@ -199,4 +199,4 @@ class Customer extends Model
         return $this->belongsToMany(Role::class);
     }
 }
-```
+```

.claude/skills/laravel-best-practices/rules/blade-views.md

@@ -33,4 +33,4 @@ return view('dashboard', compact('users'))
 
 ## Use `@aware` for Deeply Nested Component Props
 
-Avoids re-passing parent props through every level of nested components.
+Avoids re-passing parent props through every level of nested components.

.claude/skills/laravel-best-practices/rules/caching.md

@@ -2,7 +2,7 @@
 
 ## Use `Cache::remember()` Instead of Manual Get/Put
 
-Atomic pattern prevents race conditions and removes boilerplate.
+Cleaner cache-aside pattern that removes boilerplate. use `Cache::lock()` for race conditions.
 
 Incorrect:
 ```php
@@ -67,4 +67,4 @@ If Redis goes down, the app falls back to a secondary store automatically.
 
 ```php
 'failover' => ['driver' => 'failover', 'stores' => ['redis', 'database']],
-```
+```

.claude/skills/laravel-best-practices/rules/collections.md

@@ -41,4 +41,4 @@ More declarative than overriding `newCollection()`.
 ```php
 #[CollectedBy(UserCollection::class)]
 class User extends Model {}
-```
+```

.claude/skills/laravel-best-practices/rules/config.md

@@ -2,7 +2,7 @@
 
 ## `env()` Only in Config Files
 
-Direct `env()` calls return `null` when config is cached.
+Direct `env()` calls may return `null` when config is cached.
 
 Incorrect:
 ```php
@@ -70,4 +70,4 @@ If the application already uses language files for localization, use `__()` for
 ```php
 // Only when lang files already exist in the project
 return back()->with('message', __('app.article_added'));
-```
+```

.claude/skills/laravel-best-practices/rules/db-performance.md

@@ -189,4 +189,4 @@ return view('users.index', compact('users'));
 @foreach ($users as $user)
     {{ $user->profile->name }}
 @endforeach
-```
+```

.claude/skills/laravel-best-practices/rules/eloquent.md

@@ -145,4 +145,4 @@ Order::where('status', 'pending')->get();
 
 Prefer Eloquent queries and relationships over `DB::table()` whenever possible — they already reference the model's table. When `DB::table()` or raw joins are unavoidable, always use `(new Model)->getTable()` to keep the reference traceable.
 
-**Exception — migrations:** In migrations, hardcoded table names via `DB::table('settings')` are acceptable and preferred. Models change over time but migrations are frozen snapshots — referencing a model that is later renamed or deleted would break the migration.
+**Exception — migrations:** In migrations, hardcoded table names via `DB::table('settings')` are acceptable and preferred. Models change over time but migrations are frozen snapshots — referencing a model that is later renamed or deleted would break the migration.

.claude/skills/laravel-best-practices/rules/error-handling.md

@@ -69,4 +69,4 @@ class InvalidOrderException extends Exception
         return ['order_id' => $this->orderId];
     }
 }
-```
+```