Update comments

Author: Riddlerrr

spec/chrono_model/time_machine/transaction_timestamp_spec.rb

@@ -68,9 +68,10 @@
   end
 
   describe 'records updated in the same transaction' do
-    # This test reproduces the issue where clock_timestamp() in UPDATE triggers
-    # causes records updated within the same transaction to have different timestamps,
-    # making them invisible in as_of() queries.
+    # This test covers the case where an UPDATE trigger uses a non-transaction-stable
+    # timestamp (e.g., clock_timestamp()), which can cause records updated within the
+    # same transaction to end up with different validity start times and become
+    # invisible in as_of() queries.
     #
     # Scenario:
     # 1. Create an "overlap_bro" record
@@ -90,9 +91,9 @@
 
       bro_created_at = bro.history.last.validity.begin
 
-      # Query all overlappers as of the bro's creation time
-      # With clock_timestamp() in UPDATE trigger, updated overlappers would have
-      # a later timestamp and would NOT be visible here
+      # Query all overlappers as of the bro's creation time.
+      # If UPDATE triggers used a non-transaction-stable timestamp, updated overlappers would
+      # have a later validity start and would NOT be visible here.
       overlappers_at_bro_time = Overlapper.as_of(bro_created_at).where(overlap_bro_id: bro.id)
 
       expect(overlappers_at_bro_time.count).to eq(3),