strip session-added comments

crates/bootstrap/tests/bootstrap_test.rs

@@ -1,5 +1,3 @@
-//! The composition root assembles on a fresh database, with every adapter real.
-
 mod support;
 
 #[tokio::test]
@@ -21,9 +19,6 @@ async fn worker_builds_on_a_fresh_database() {
         .expect("worker builds");
 }
 
-/// Without the federation feature, following another local user still works
-/// (the request lands as pending for the target):
-/// the local social ports are wired in place of the ActivityPub ones.
 #[cfg(not(feature = "federation"))]
 #[tokio::test]
 async fn federation_off_build_wires_local_social() {
@@ -68,8 +63,6 @@ async fn federation_off_build_wires_local_social() {
     );
 }
 
-/// The server never talks to the bus: whatever `EVENT_BUS_BACKEND` says, a
-/// change and its event land in the outbox table. No NATS server is reachable here.
 #[tokio::test]
 async fn server_publishes_to_the_outbox_even_when_bus_is_nats() {
     let pool = support::memory_pool().await;
@@ -108,8 +101,6 @@ async fn server_publishes_to_the_outbox_even_when_bus_is_nats() {
     assert_eq!(queued, 1);
 }
 
-/// Handler names key the processed-event ledger, so each must be unique. The
-/// check runs over the real wiring, in both federation builds.
 #[tokio::test]
 async fn handler_names_are_unique() {
     let pool = support::memory_pool().await;
@@ -126,8 +117,6 @@ async fn handler_names_are_unique() {
     );
     let mut sorted = names.clone();
     sorted.sort_unstable();
-    // Names key the ledger: a rename re-runs events inside the retention
-    // window, so changing this list must be a deliberate edit.
     let mut expected = vec![
         "account_purge",
         "image_cleanup",
@@ -143,7 +132,6 @@ async fn handler_names_are_unique() {
         expected.extend(["activitypub", "follow_backfill"]);
     }
     expected.sort_unstable();
-    // Image conversion ("image_conversion") is disabled in the test config.
     assert_eq!(sorted, expected);
 }
 
@@ -157,8 +145,6 @@ async fn queued(pool: &sqlx::SqlitePool, event_type: &str) -> i64 {
     .unwrap()
 }
 
-/// A local follow writes both follow rows and its event in one commit, in
-/// both federation builds.
 #[tokio::test]
 async fn a_local_follow_lands_with_its_event_in_the_outbox() {
     let (router, pool) = support::server().await;
@@ -189,8 +175,6 @@ async fn a_local_follow_lands_with_its_event_in_the_outbox() {
     assert_eq!(queued(&pool, "FollowRequested").await, 1);
 }
 
-/// The k_ap path owns its transaction, so the adapter publishes the event
-/// itself once the k_ap write has succeeded.
 #[cfg(feature = "federation")]
 #[tokio::test]
 async fn a_remote_block_publishes_its_event_after_the_k_ap_write() {
@@ -217,9 +201,6 @@ async fn a_remote_block_publishes_its_event_after_the_k_ap_write() {
     assert_eq!(queued(&pool, "ActorBlocked").await, 1);
 }
 
-/// A token outlives the account that owns it, so every authenticated route
-/// must re-check the account: a deleted user gets exactly what an anonymous
-/// caller gets.
 #[tokio::test]
 async fn a_deleted_users_token_is_rejected() {
     let (router, pool) = support::server().await;
@@ -255,9 +236,6 @@ async fn a_deleted_users_token_is_rejected() {
     assert_eq!(headers.get("location").unwrap(), "/login");
 }
 
-/// A deleted account stays resolvable inside k-ap (to sign its `Delete`), but
-/// every ActivityPub document for it answers 410, while the classic profile
-/// page stays 404.
 #[cfg(feature = "federation")]
 #[tokio::test]
 async fn actor_document_for_a_tombstone_is_gone() {
@@ -301,8 +279,6 @@ async fn actor_document_for_a_tombstone_is_gone() {
     assert_eq!(status, 404, "the classic profile page stays 404");
 }
 
-/// Remote servers posting to a deleted account's inbox are told it is gone,
-/// before any signature check.
 #[cfg(feature = "federation")]
 #[tokio::test]
 async fn posting_to_a_tombstones_inbox_is_gone() {