strip session-added comments

crates/adapters/activitypub/tests/activity_ids.rs

@@ -1,11 +1,3 @@
-//! Outbound activity ids across a redelivered event, through the real k-ap
-//! `ActivityPubService` (delivery captured via its `EventPublisher` seam).
-//!
-//! k-ap 0.5.0 derives Create ids from the object id (UUIDv5,
-//! `service/broadcast.rs:285-288`) but mints Update/Delete/Move/actor-update ids
-//! randomly (`broadcast.rs:81,129,157,210,321,343,377` -> `url_scheme.rs:53`,
-//! `Uuid::new_v4`) with no override.
-
 use std::sync::Arc;
 use std::time::Duration;
 
@@ -189,8 +181,6 @@ async fn activitypub_is_idempotent_when_run_twice() {
     assert_eq!(first, second, "a redelivered Create keeps its activity id");
 }
 
-/// Characterises the k-ap 0.5.0 limitation recorded in ADR-0015. If k-ap starts
-/// minting deterministic Delete ids this fails: upgrade the ADR and flip it.
 #[tokio::test]
 async fn redelivered_delete_gets_a_fresh_activity_id_known_k_ap_limitation() {
     let mut h = harness().await;
@@ -207,8 +197,6 @@ async fn redelivered_delete_gets_a_fresh_activity_id_known_k_ap_limitation() {
     assert_ne!(first, second);
 }
 
-/// Queued events of a deleted account must not sign and send from its
-/// tombstone; the account's own Delete still goes out.
 #[tokio::test]
 async fn a_deleted_account_sends_nothing_but_its_delete() {
     let mut h = harness().await;
@@ -240,7 +228,6 @@ async fn a_deleted_account_sends_nothing_but_its_delete() {
         signing_actor_id: h.user.value(),
     };
 
-    // The review repository panics if the handler gets past the guard.
     for event in [&logged, &added, &queued] {
         h.handler.handle(event).await.unwrap();
     }