fix(spec): require actionId when an action wants a response

[BBC6BAE9]

Description

Require actionId when a v1.0 renderer action explicitly sets wantResponse to true, and add schema cases covering response-requesting and fire-and-forget actions.

The v1.0 protocol documentation already states that actionId is required in this case, but renderer_to_agent.json did not encode the conditional requirement. As a result, the schema accepted response-requesting actions that an agent could not correlate with an actionResponse.

The condition also requires wantResponse itself to be present, so existing actions that omit the optional field continue to validate. No tracking issue was filed because this is a small schema consistency fix.

Impact

• Existing actions that omit wantResponse remain valid.
• Actions with wantResponse: false remain valid without an actionId.
• Actions with wantResponse: true must include an actionId.

Validation

• python3 specification/v1_0/test/run_tests.py — 138 passed, 0 failed
• python3 specification/scripts/validate.py — Overall Validation: PASSED
• Prettier check — passed for the changed JSON files
• git diff --check — passed

Pre-launch Checklist

One time:

• I signed the CLA.
• I read the Contributors Guide.
• I read the Style Guide.
• I have built and run at least one sample. Not run for this schema-only change.

For this PR:

• I have updated the relevant CHANGELOG.md file. N/A: there is no specification CHANGELOG for this change.
• I updated/added relevant documentation. N/A: the v1.0 protocol documentation already specifies this requirement; this PR aligns the schema with it.
• My code changes (if any) have tests.
• If my branch is on a fork, I have verified that scripts/e2e_test.sh passes. Not run: this Flutter/Gemini E2E requires GEMINI_API_KEY and is unrelated to the schema-only change.

If you need help, consider asking for advice on the discussion board.

[gemini-code-assist]

Code Review

This pull request updates the JSON schema in client_to_server.json to conditionally require actionId when wantResponse is set to true. It also adds test cases in client_messages.json to validate this new schema constraint. I have no feedback to provide.

[polina-c]

Thank you for your contribution. Unfortunately, we must decline this PR at this time.
Our team resources are limited, and our policy is to prioritize the review of PRs that address an existing issue. Consider opening issue
and link your PR in the issue description as one of the options for resolution.