docs(core): docs for 1.0

[yuyutaotao]

No description provided.

[netlify]

✅ Deploy Preview for midscene ready!

Name	Link
🔨 Latest commit	1288300
🔍 Latest deploy log	https://app.netlify.com/projects/midscene/deploys/690d88434194373454005dc1
😎 Deploy Preview	https://deploy-preview-1423--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.

[CLAassistant]

All committers have signed the CLA.

[chatgpt-codex-connector]

💡 Codex Review

midscene/packages/android/src/device.ts

Lines 1629 to 1649 in c3eec50

	AndroidBackButton: defineAction({
	name: 'AndroidBackButton',
	description: 'Trigger the system "back" operation on Android devices',
	paramSchema: z.void().describe('No parameters required'),
	call: async () => {
	await device.back();
	},
	}),
	AndroidHomeButton: defineAction({
	name: 'AndroidHomeButton',
	description: 'Trigger the system "home" operation on Android devices',
	paramSchema: z.void().describe('No parameters required'),
	call: async () => {
	await device.home();
	},
	}),
	AndroidRecentAppsButton: defineAction({
	name: 'AndroidRecentAppsButton',
	description:
	'Trigger the system "recent apps" operation on Android devices',
	paramSchema: z.void().describe('No parameters required'),

System navigation actions now reject empty params on Android

The Android system navigation actions were changed to use z.void() schemas. However the execution pipeline still passes {} for actions that have no parameters (see TaskBuilder.handleActionPlan which feeds plan.param through parseActionParam). z.void() rejects {}, so a plan that emits "AndroidBackButton": {} or any existing YAML using {} will now fail schema validation before the action runs, aborting the task. The previous z.object({}) schema accepted empty objects and matched current callers; this change makes the action unusable unless every caller is updated to pass undefined.

---

midscene/packages/ios/src/device.ts

Lines 976 to 988 in c3eec50

	IOSHomeButton: defineAction({
	name: 'IOSHomeButton',
	description: 'Trigger the system "home" operation on iOS devices',
	paramSchema: z.void().describe('No parameters required'),
	call: async () => {
	await device.home();
	},
	}),
	IOSAppSwitcher: defineAction({
	name: 'IOSAppSwitcher',
	description: 'Trigger the system "app switcher" operation on iOS devices',
	paramSchema: z.void().describe('No parameters required'),
	call: async () => {

iOS system button actions break when called with default {} payloads

Similar to Android, the iOS IOSHomeButton and IOSAppSwitcher actions now declare paramSchema: z.void(). The planner and YAML runner send {} for parameter-less actions, and TaskBuilder validates those payloads via parseActionParam. With a z.void() schema this produces a Zod error (Expected undefined, received object) and the navigation action never executes. Keeping the schema as an empty object maintains backward compatibility with existing callers and avoids blocking these actions at runtime.

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".