Update comments for clarity in Sign_In_With_Google tests.

Refine comments in the Sign_In_With_GoogleTest and Web_TagTest classes
to enhance readability and understanding of the test logic.
This improves maintainability and helps future developers grasp the
purpose of the tests more easily.

Author: shervElmi

tests/phpunit/integration/Modules/Sign_In_With_Google/Web_TagTest.php

@@ -237,18 +237,17 @@ public function test_render_tag__emits_connect_markers_only_when_flag_on() {
 		$user_id = $this->factory()->user->create( array( 'role' => 'editor' ) );
 		wp_set_current_user( $user_id );
 
-		// With the flag on, the rendered script tags the request as the
-		// connect-existing-profile flow and includes the matching nonce.
+		// With the flag on, the rendered script tags the request as the connect-existing-profile
+		// flow and includes the matching nonce.
 		$this->web_tag->set_is_connect_existing_profile( true );
 		$output = $this->capture_render_tag_output();
 		$this->assertStringContainsString( "response.integration='connect_existing_profile'", $output, 'Rendered script should set the connect_existing_profile integration when the flag is on.' );
 		$this->assertStringContainsString( 'response.connect_nonce=', $output, 'Rendered script should include the connect nonce assignment when the flag is on.' );
 		$this->assertStringContainsString( wp_create_nonce( Authenticator::CONNECT_NONCE_ACTION ), $output, 'Rendered nonce should match wp_create_nonce for CONNECT_NONCE_ACTION.' );
 
-		// Toggle the flag off on the same instance to guard against a vacuous
-		// pass if the marker strings ever change. The positive phase above
-		// fails first when that happens, signalling the negative assertions
-		// below need updating too.
+		// Toggling the flag off on the same instance guards against a vacuous pass if the marker
+		// strings ever change. The positive phase above fails first when that happens, signalling
+		// that the negative assertions below need updating too.
 		$this->web_tag->set_is_connect_existing_profile( false );
 		$output = $this->capture_render_tag_output();
 		$this->assertStringNotContainsString( "response.integration='connect_existing_profile'", $output, 'Rendered script should not include the connect integration when the flag is off.' );
@@ -263,9 +262,8 @@ public function test_render_tag__forces_button_render_loop_on_connect_flow_even_
 
 		$output = $this->capture_render_tag_output();
 
-		// Logged-in users normally skip the button render loop; the connect
-		// flow flips that gate so the placeholder div on the profile page
-		// can still be wired up.
+		// Logged-in users normally skip the button render loop. The connect flow flips that gate
+		// so the placeholder div on the profile page can still be wired up.
 		$this->assertStringContainsString( 'google.accounts.id.renderButton', $output, 'Connect flow should force the button render loop even when the user is logged in.' );
 		$this->assertStringContainsString( 'googlesitekit-sign-in-with-google__frontend-output-button', $output, 'Render loop should target the SiwG placeholder class.' );
 	}

tests/phpunit/integration/Modules/Sign_In_With_GoogleTest.php

@@ -506,9 +506,8 @@ public function test_maybe_render_profile_signinwithgoogle__skips_when_show_user
 		global $wp_actions;
 		unset( $wp_actions['show_user_profile'] );
 
-		// HTTPS setup so `Tag_Guard::can_activate()` doesn't short-circuit
-		// first - the `did_action` gate must be the only thing keeping the
-		// connect script out (anti-vacuous).
+		// HTTPS setup keeps `Tag_Guard::can_activate()` from short-circuiting first, so the
+		// `did_action` gate is the only thing left to keep the connect script out (anti-vacuous).
 		$this->enable_https_login_env();
 		$this->register_and_connect_module();
 
@@ -521,9 +520,8 @@ public function test_maybe_render_profile_signinwithgoogle__skips_when_show_user
 	}
 
 	public function test_maybe_render_profile_signinwithgoogle__skips_when_user_already_linked() {
-		// HTTPS setup so `Tag_Guard::can_activate()` doesn't short-circuit
-		// first - the `Hashed_User_ID` gate must be the only thing keeping
-		// the connect script out (anti-vacuous).
+		// HTTPS setup keeps `Tag_Guard::can_activate()` from short-circuiting first, so the
+		// `Hashed_User_ID` gate is the only thing left to keep the connect script out (anti-vacuous).
 		$this->enable_https_login_env();
 		$this->register_and_connect_module();
 
@@ -539,9 +537,8 @@ public function test_maybe_render_profile_signinwithgoogle__skips_when_user_alre
 	}
 
 	public function test_maybe_render_profile_signinwithgoogle__skips_when_module_not_connected() {
-		// HTTPS setup so the `wp_login_url()` half of `Tag_Guard::can_activate()`
-		// passes - the only thing keeping the connect script out should be
-		// the missing `clientID` (anti-vacuous).
+		// HTTPS setup keeps the `wp_login_url()` half of `Tag_Guard::can_activate()` passing, so
+		// the missing `clientID` is the only thing left to keep the connect script out (anti-vacuous).
 		$this->enable_https_login_env();
 		$this->module->register();
 		// Intentionally skip setting `clientID` so `build_registrable_tag()`
@@ -579,9 +576,8 @@ public function test_resolve_authenticator_class__returns_profile_authenticator_
 	public function test_resolve_authenticator_class__falls_back_to_base_for_connect_when_logged_out() {
 		wp_set_current_user( 0 );
 
-		// AC4: a `connect_existing_profile` request without an authenticated
-		// session must fall back to the base `Authenticator` so `wp-login.php`
-		// behaves like a fresh sign-in.
+		// A `connect_existing_profile` request without an authenticated session must fall back
+		// to the base `Authenticator` so `wp-login.php` behaves like a fresh sign-in (AC4).
 		$this->assertSame(
 			Authenticator::class,
 			$this->call_resolve_authenticator_class( 'connect_existing_profile' ),