test(daemon): assert the durable close event survives a failed close-time save

Review feedback on #1392 (thymikee), final P2 item: the previous commit
removed the actions rollback because there's no surviving session to
duplicate the close action on, but nothing actually asserted the
durable events.ndjson action.recorded:close event stays put. Flush and
read it back so a future rollback or event-order change can't silently
recreate the in-memory/durable mismatch the removed rollback used to
paper over asymmetrically.

Author: thymikee

src/daemon/handlers/__tests__/session-device-claims.test.ts

@@ -307,4 +307,20 @@ test('#1391: a close-time script save failure still clears the advisory claim an
   assert.equal(store.get('close-save-script-failure'), undefined);
   assert.deepEqual(inspectDeviceClaims({ serial: android.id }), []);
   assert.equal(fs.readFileSync(targetPath, 'utf8'), 'pre-existing\n');
+
+  // No rollback: the durable `action.recorded: close` event this close wrote
+  // to events.ndjson (before the script write failed) survives — teardown
+  // never withholds it, since there is no surviving session for a later
+  // write to duplicate it against. Guards against a future rollback or
+  // event-order change silently recreating the in-memory/durable mismatch
+  // this test's own name warns about.
+  await store.flushEvents('close-save-script-failure');
+  const events = store.readEvents('close-save-script-failure').events;
+  const closeEvent = events.find(
+    (event) => event.kind === 'action.recorded' && event.command === 'close',
+  );
+  assert.ok(
+    closeEvent,
+    'expected a durable action.recorded:close event to survive the failed save',
+  );
 });