spec(v0_10): add copyToClipboard standard local action to catalog, do…

[iamrajhans]

Description

This PR adds copyToClipboard as a standard local client action in the v0.10 catalog so agents can request clipboard-copy behavior in a portable, schema-validated way.

What changed:

• Added copyToClipboard function definition to specification/v0_10/json/standard_catalog.json:
  • call: "copyToClipboard"
  • args.text (dynamic string)
  • returnType: "void"
• Added it to $defs.anyFunction in the same schema.
• Updated protocol docs in specification/v0_10/docs/a2ui_protocol.md:
  • Added a local action example using copyToClipboard
  • Added it to the standard functions table
• Added validation coverage in specification/v0_10/test/cases/function_catalog_validation.json:
  • valid call case
  • invalid args type
  • invalid return type
  • invalid text type
• Added an eval prompt case in specification/v0_10/eval/src/prompts.ts for copyToClipboard.

Notes:

• This PR intentionally does not add confirm, based on discussion in the linked issue thread.

Fixes #533

Pre-launch Checklist

• I signed the CLA.
• I read the Contributors Guide.
• I read the Style Guide.
• I have added updates to the CHANGELOG.
• I updated/added relevant documentation.
• My code changes (if any) have tests.

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

[gemini-code-assist]

Code Review

This pull request correctly adds the copyToClipboard standard local action. The schema definition in standard_catalog.json and the corresponding validation tests are well-implemented. I've added a couple of suggestions to improve the consistency of the documentation and evaluation prompts regarding the returnType property of the function call. Making these parts more explicit will improve clarity for developers and reliability of LLM-generated code.

[gemini-code-assist]

The prompt text for the LLM is a bit ambiguous about returnType. Given the subtleties of the schema validation where returnType defaults to "boolean", it would be more robust to explicitly ask the LLM to include "returnType": "void" in the function call. This will lead to more reliable JSON generation.

    The button's action should be a client-side function call to 'copyToClipboard' with the argument 'text': 'SAVE20' and a 'returnType' of 'void'.