From 05e4a17949e89055effb161091fe01e2c41dc6c3 Mon Sep 17 00:00:00 2001 From: Brian Krabach Date: Mon, 18 May 2026 17:30:26 -0700 Subject: [PATCH] fix(fmt): apply rustfmt to session.rs test assertions MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Two assert_eq! macros in mod tests had multi-line arg formatting that rustfmt --check rejected. PR #84 landed despite the failing format check because admin-merge bypassed CI. This restores green Rust Core CI. Both diffs collapse: assert_eq!( - start_count, - 1, + start_count, 1, "…" ); No functional change. Co-authored-by: Amplifier --- crates/amplifier-core/src/session.rs | 6 ++---- 1 file changed, 2 insertions(+), 4 deletions(-) diff --git a/crates/amplifier-core/src/session.rs b/crates/amplifier-core/src/session.rs index 6f09070..6598ed5 100644 --- a/crates/amplifier-core/src/session.rs +++ b/crates/amplifier-core/src/session.rs @@ -797,8 +797,7 @@ mod tests { .filter(|(name, _)| name == events::SESSION_START) .count(); assert_eq!( - start_count, - 1, + start_count, 1, "session:start must fire exactly once per session, not per execute() call. \ Got {} events across 3 execute() calls. \ This is the Rust-port regression: lifecycle events belong at session \ @@ -842,8 +841,7 @@ mod tests { .filter(|(name, _)| name == events::SESSION_RESUME) .count(); assert_eq!( - resume_count, - 1, + resume_count, 1, "session:resume must fire exactly once per session, not per execute() call. \ Got {} events across 3 execute() calls.", resume_count