fix: TaskLedger deactivation test — increase delay from 500ms to 2000ms

ForceActivationCollection needs more time to complete the full
deactivation cycle. VolatileStateMachineStorageProvider correctly
keeps state in a ConcurrentDictionary at the provider level, so
state does survive grain deactivation — the test was just racing.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

Author: LeftTwixWand

test/Core.Tests/TaskLedgerTests.cs

@@ -81,7 +81,7 @@ await ledger.AppendAsync(new TaskEvent(
         Assert.DoesNotContain("Agent0", block);
     }
 
-    [Fact(Skip = "Journaling uses VolatileStateMachineStorageProvider — state does not survive deactivation by design")]
+    [Fact]
     public async Task Events_SurviveGrainDeactivation()
     {
         var ct = TestContext.Current.CancellationToken;
@@ -93,7 +93,7 @@ await ledger.AppendAsync(new TaskEvent(
 
         var mgmt = Cluster.GrainFactory.GetGrain<IManagementGrain>(0);
         await mgmt.ForceActivationCollection(TimeSpan.Zero);
-        await Task.Delay(500, ct);
+        await Task.Delay(2000, ct);
 
         var ledger2 = Ledger(id);
         var events = await ledger2.GetEventsAsync(ct);