From 8b05b8a76dd5b951d9559a161a85bd7c0c381cbe Mon Sep 17 00:00:00 2001
From: Claude <developers@lethean.io>
Date: Tue, 24 Mar 2026 13:11:29 +0000
Subject: [PATCH 1/3] fix: cascade delete namespaces when workspace is removed

Change namespaces.workspace_id FK from nullOnDelete to cascadeOnDelete
so that namespaces are properly cleaned up when their parent workspace
is deleted, instead of being orphaned with a null workspace_id.

Fixes #10

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
---
 ..._delete_namespaces_on_workspace_delete.php | 40 +++++++++++++++++++
 1 file changed, 40 insertions(+)
 create mode 100644 Migrations/2026_03_24_000000_cascade_delete_namespaces_on_workspace_delete.php

diff --git a/Migrations/2026_03_24_000000_cascade_delete_namespaces_on_workspace_delete.php b/Migrations/2026_03_24_000000_cascade_delete_namespaces_on_workspace_delete.php
new file mode 100644
index 0000000..bb5f6a5
--- /dev/null
+++ b/Migrations/2026_03_24_000000_cascade_delete_namespaces_on_workspace_delete.php
@@ -0,0 +1,40 @@
+<?php
+
+declare(strict_types=1);
+
+use Illuminate\Database\Migrations\Migration;
+use Illuminate\Database\Schema\Blueprint;
+use Illuminate\Support\Facades\Schema;
+
+return new class extends Migration
+{
+    /**
+     * Change namespaces.workspace_id FK from nullOnDelete to cascadeOnDelete.
+     *
+     * Fixes #10 — namespaces were orphaned with null workspace_id when
+     * the parent workspace was deleted.
+     */
+    public function up(): void
+    {
+        Schema::table('namespaces', function (Blueprint $table) {
+            $table->dropForeign(['workspace_id']);
+
+            $table->foreign('workspace_id')
+                ->references('id')
+                ->on('workspaces')
+                ->cascadeOnDelete();
+        });
+    }
+
+    public function down(): void
+    {
+        Schema::table('namespaces', function (Blueprint $table) {
+            $table->dropForeign(['workspace_id']);
+
+            $table->foreign('workspace_id')
+                ->references('id')
+                ->on('workspaces')
+                ->nullOnDelete();
+        });
+    }
+};
-- 
2.45.3


From 70ad94d66d2f2ec76974e70026007bb0f04a77a3 Mon Sep 17 00:00:00 2001
From: Claude <developers@lethean.io>
Date: Tue, 24 Mar 2026 13:11:34 +0000
Subject: [PATCH 2/3] fix: add FK constraints on feature_code columns to
 entitlement_features

Add foreign key constraints from usage_alert_history.feature_code,
entitlement_boosts.feature_code, and entitlement_usage_records.feature_code
to entitlement_features.code to prevent orphaned records.

Uses cascadeOnUpdate (code renames propagate) and restrictOnDelete
(cannot delete a feature that has usage/alert/boost records).

Fixes #12

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
---
 ...4_000000_add_feature_code_foreign_keys.php | 57 +++++++++++++++++++
 1 file changed, 57 insertions(+)
 create mode 100644 Migrations/2026_03_24_000000_add_feature_code_foreign_keys.php

diff --git a/Migrations/2026_03_24_000000_add_feature_code_foreign_keys.php b/Migrations/2026_03_24_000000_add_feature_code_foreign_keys.php
new file mode 100644
index 0000000..9680b1b
--- /dev/null
+++ b/Migrations/2026_03_24_000000_add_feature_code_foreign_keys.php
@@ -0,0 +1,57 @@
+<?php
+
+declare(strict_types=1);
+
+use Illuminate\Database\Migrations\Migration;
+use Illuminate\Database\Schema\Blueprint;
+use Illuminate\Support\Facades\Schema;
+
+return new class extends Migration
+{
+    /**
+     * Add foreign key constraints on feature_code columns to prevent orphaned records.
+     *
+     * Fixes #12: feature_code in usage_alert_history not constrained to entitlement_features.
+     */
+    public function up(): void
+    {
+        Schema::table('entitlement_usage_alert_history', function (Blueprint $table) {
+            $table->foreign('feature_code', 'usage_alert_feature_code_fk')
+                ->references('code')
+                ->on('entitlement_features')
+                ->cascadeOnUpdate()
+                ->restrictOnDelete();
+        });
+
+        Schema::table('entitlement_boosts', function (Blueprint $table) {
+            $table->foreign('feature_code', 'boosts_feature_code_fk')
+                ->references('code')
+                ->on('entitlement_features')
+                ->cascadeOnUpdate()
+                ->restrictOnDelete();
+        });
+
+        Schema::table('entitlement_usage_records', function (Blueprint $table) {
+            $table->foreign('feature_code', 'usage_records_feature_code_fk')
+                ->references('code')
+                ->on('entitlement_features')
+                ->cascadeOnUpdate()
+                ->restrictOnDelete();
+        });
+    }
+
+    public function down(): void
+    {
+        Schema::table('entitlement_usage_alert_history', function (Blueprint $table) {
+            $table->dropForeign('usage_alert_feature_code_fk');
+        });
+
+        Schema::table('entitlement_boosts', function (Blueprint $table) {
+            $table->dropForeign('boosts_feature_code_fk');
+        });
+
+        Schema::table('entitlement_usage_records', function (Blueprint $table) {
+            $table->dropForeign('usage_records_feature_code_fk');
+        });
+    }
+};
-- 
2.45.3


From d2548f7a627d89f4c017c83e175660bdc978b29d Mon Sep 17 00:00:00 2001
From: Claude <developers@lethean.io>
Date: Tue, 24 Mar 2026 13:11:34 +0000
Subject: [PATCH 3/3] fix: cascade delete child features when parent is removed

The self-referential FK on entitlement_features.parent_feature_id used
nullOnDelete(), which orphaned child features when a parent was deleted.
Children that belong to a pool have no meaning without their parent, so
cascade deletion is the correct behaviour.

Adds a migration that drops and re-creates the FK with cascadeOnDelete().

Fixes #40

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
---
 ...0000_fix_parent_feature_cascade_delete.php | 47 +++++++++++++++++++
 1 file changed, 47 insertions(+)
 create mode 100644 Migrations/2026_03_24_000000_fix_parent_feature_cascade_delete.php

diff --git a/Migrations/2026_03_24_000000_fix_parent_feature_cascade_delete.php b/Migrations/2026_03_24_000000_fix_parent_feature_cascade_delete.php
new file mode 100644
index 0000000..81698fa
--- /dev/null
+++ b/Migrations/2026_03_24_000000_fix_parent_feature_cascade_delete.php
@@ -0,0 +1,47 @@
+<?php
+
+declare(strict_types=1);
+
+use Illuminate\Database\Migrations\Migration;
+use Illuminate\Database\Schema\Blueprint;
+use Illuminate\Support\Facades\Schema;
+
+return new class extends Migration
+{
+    /**
+     * Change parent_feature_id FK from nullOnDelete to cascadeOnDelete.
+     *
+     * nullOnDelete orphans child features when a parent is removed — they lose
+     * their hierarchy but still exist with a null parent_feature_id.  Children
+     * that belong to a pool have no meaning without their parent, so cascade
+     * deletion is the correct behaviour.
+     *
+     * Fixes #40
+     */
+    public function up(): void
+    {
+        Schema::table('entitlement_features', function (Blueprint $table) {
+            $table->dropForeign(['parent_feature_id']);
+
+            $table->foreign('parent_feature_id')
+                ->references('id')
+                ->on('entitlement_features')
+                ->cascadeOnDelete();
+        });
+    }
+
+    /**
+     * Revert to the original nullOnDelete behaviour.
+     */
+    public function down(): void
+    {
+        Schema::table('entitlement_features', function (Blueprint $table) {
+            $table->dropForeign(['parent_feature_id']);
+
+            $table->foreign('parent_feature_id')
+                ->references('id')
+                ->on('entitlement_features')
+                ->nullOnDelete();
+        });
+    }
+};
-- 
2.45.3