refactor(grasp-audit): split ValidRepo into Sent/Served, add tolerant purgatory

- Rename ValidRepo to ValidRepoSent (announcement sent, may be in purgatory)
- Add ValidRepoServed (announcement queryable after git data pushed)
- Add send_event_and_note_purgatory() for tolerant purgatory detection
- Update fixtures to use tolerant method instead of strict assertion
- Update event_acceptance_policy tests to use ValidRepoServed

This enables tests to pass regardless of purgatory implementation status
while still having explicit purgatory tests that verify the behavior.

1 files changed, 1 insertions, 1 deletions

diff --git a/grasp-audit/README.md b/grasp-audit/README.md
index 4d2401f..2cc9247 100644
--- a/grasp-audit/README.md
+++ b/grasp-audit/README.md
@@ -245,7 +245,7 @@ pub async fn test_something(client: &AuditClient) -> TestResult {
             let ctx = TestContext::new(client);
 
             // 2. Prerequisites (cached per-TestContext)
-            let repo = ctx.get_fixture(FixtureKind::ValidRepo).await?;
+            let repo = ctx.get_fixture(FixtureKind::ValidRepoSent).await?;
 
             // 3. Test-specific event
             let my_event = client.create_issue(&repo, "Title", "Content", vec![])?;