From f06109e38edfc87cfe3813c68f40cd009c999089 Mon Sep 17 00:00:00 2001
From: DanConwayDev <DanConwayDev@protonmail.com>
Date: Mon, 21 Sep 2026 08:39:47 +0000
Subject: [PATCH] test(audit): order the recursive announcement after its
 fixture

The full parallel suite exposed a rejection in the external-announcement
admission scenario. It replaces the fixture's reciprocal announcement
using only the wall clock, so a same-second update can lose the NIP-01
lower-ID tie-break and return the relay's generic save rejection.

Query the stored predecessor for that author and identifier and choose a
timestamp strictly after it, with checked overflow. Retain the exact-ID
storage assertion and remove the post-acknowledgement propagation sleep.
This orders a real fixture revision; relay authorization and production
replacement rules are unchanged.

The focused integration test and formatting check pass. The failed full
run is retained, and three new full workspace runs will validate the
combined revision under the CI hostile Git configuration.

Assisted-by: Codex (GPT-6)
---
 .../specs/grasp01/event_acceptance_policy.rs  | 27 ++++++++++++++++---
 1 file changed, 24 insertions(+), 3 deletions(-)

diff --git a/grasp-audit/src/specs/grasp01/event_acceptance_policy.rs b/grasp-audit/src/specs/grasp01/event_acceptance_policy.rs
index 337f9b9..f281e2b 100644
--- a/grasp-audit/src/specs/grasp01/event_acceptance_policy.rs
+++ b/grasp-audit/src/specs/grasp01/event_acceptance_policy.rs
@@ -452,6 +452,27 @@ impl EventAcceptancePolicyTests {
                 .to_bech32()
                 .map_err(|e| format!("Failed to convert recursive maintainer pubkey: {}", e))?;
 
+            // This replaces the reciprocal announcement created by the fixture.
+            // Order it after that event explicitly: using the wall clock alone
+            // makes a fast run depend on the equal-timestamp event-ID tie-break.
+            let previous_time = client
+                .query(
+                    Filter::new()
+                        .kind(Kind::GitRepoAnnouncement)
+                        .author(client.recursive_maintainer_keys().public_key())
+                        .identifier(&repo_id),
+                )
+                .await
+                .map_err(|e| format!("Failed to query reciprocal announcement: {e}"))?
+                .iter()
+                .map(|event| event.created_at.as_secs())
+                .max()
+                .ok_or("Fixture reciprocal announcement is not served")?;
+            let replacement_time = previous_time
+                .checked_add(1)
+                .ok_or("Reciprocal announcement timestamp overflow")?
+                .max(Timestamp::now().as_secs());
+
             // Create announcement with external clone URL (not this server)
             let recursive_maintainer_announcement = client
                 .event_builder(
@@ -487,6 +508,7 @@ impl EventAcceptancePolicyTests {
                     "maintainers",
                     vec![client.maintainer_pubkey_hex()],
                 ))
+                .custom_time(Timestamp::from(replacement_time))
                 .build(client.recursive_maintainer_keys())
                 .map_err(|e| format!("Failed to build recursive maintainer announcement: {}", e))?;
 
@@ -498,9 +520,8 @@ impl EventAcceptancePolicyTests {
                 .await
                 .map_err(|e| format!("Failed to send recursive maintainer announcement: {}", e))?;
 
-            // Wait for propagation
-            tokio::time::sleep(Duration::from_millis(200)).await;
-
+            // The successful send acknowledges storage of this external
+            // announcement; verify its exact ID without a propagation sleep.
             // Step 4: Query to verify it was accepted
             let filter = Filter::new()
                 .kind(Kind::GitRepoAnnouncement)