feat(core,mcp,web-integration): enhance aiKeyboardPress to support key combinations

[xnmeet]

Overview

usage

await agent.aiKeyboardPress(["Meta","A"]);
await agent.aiKeyboardPress("Meta+A");

Features Implemented
✅ AI-powered element location: keyBoardPress uses the same intelligent element detection as other actions
✅ YAML workflow support: keyBoardPress actions can be included in automated workflows
✅ Caching support: Leverages existing task caching mechanisms

Testing
Comprehensive test coverage has been added:

Unit tests: Core type validation and plan building logic
Integration tests: End-to-end keyBoardPress execution scenarios

Validation Steps
To verify this implementation:

Manual testing:

const agent = new PageAgent(page);
await agent.aiKeyboardPress(["Meta","A"]);

Backward Compatibility
✅ No breaking changes: All existing APIs remain unchanged
✅ Type safety: Full TypeScript support with proper type inference

[netlify]

✅ Deploy Preview for midscene ready!

Name	Link
🔨 Latest commit	e0b6b44
🔍 Latest deploy log	https://app.netlify.com/projects/midscene/deploys/683eff3400b72200083b112e
😎 Deploy Preview	https://deploy-preview-799--midscene.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[xnmeet]

is there anyone can help review this pr @zhoushaw @yuyutaotao

[quanru]

I understand that the combination keys can be used directly on the page object. Have you encountered a situation that cannot be resolved with this method?

[xnmeet]

I understand that the combination keys can be used directly on the page object. Have you encountered a situation that cannot be resolved with this method?

This change targets two scenarios: the first is to use AI to locate the area and then trigger the key combination. The second is to eliminate the accuracy of some commands caused by AI method reasoning.