test(a2a): align session.close smoke scenarios with session_id guard

The session_id validation guard added to _handle_session_close in
A2aLocalFacade now raises ValueError when session_id is empty or
missing. Update three pre-existing smoke scenarios that previously
dispatched session.close with empty params to pass an explicit
session_id, aligning the smoke contract with the security fix.

The negative-path scenarios (@tdd_issue_9250) in
a2a_facade_coverage.feature continue to verify the ValueError path
with empty/missing session_id.

ISSUES CLOSED: #9250

features/consolidated_misc.feature

@@ -42,7 +42,7 @@ Feature: Consolidated Misc
 
   Scenario: Dispatch session.close returns status closed
     Given a new A2aLocalFacade with no services
-    When I dispatch operation "session.close" with params {}
+    When I dispatch operation "session.close" with params {"session_id": "01M6SM0KESESS0N00000000000"}
     Then the response status should be "ok"
     And response data key "status" equals "closed"
 
@@ -563,7 +563,7 @@ Feature: Consolidated Misc
   Scenario: M6 smoke A2A session close returns closed status
     Given a m6 smoke test runner
     And a m6 smoke A2A local facade
-    When I m6 smoke dispatch "session.close" with params {}
+    When I m6 smoke dispatch "session.close" with params {"session_id": "01M6SM0KESESS0N00000000000"}
     Then the m6 smoke response status should be "ok"
     And the m6 smoke response data "status" should equal "closed"
 

features/m6_autonomy_acceptance.feature

@@ -35,7 +35,7 @@ Feature: M6 autonomy acceptance smoke tests
     And the m6 smoke response data should contain key "status"
 
   Scenario: M6 smoke A2A session close returns closed status
-    When I m6 smoke dispatch "session.close" with params {}
+    When I m6 smoke dispatch "session.close" with params {"session_id": "01M6SM0KESESS0N00000000000"}
     Then the m6 smoke response status should be "ok"
     And the m6 smoke response data "status" should equal "closed"