Maestro Docs release notes

No pages were added or removed. Updates focus on clearer guidance in three areas:

Test reports and artifacts

• Clarified that Maestro stores screenshots, logs, and metadata per session (not only per run).
• Documented Maestro Cloud metadata automatically added to JUnit/HTML reports (cloud.runId, cloud.runUrl, cloud.uploadId, cloud.url), including how CI and agents can use the links.
• Documented timestamps and durations in reports (local timezone, suite-level wall-clock time, HTML formatting).
• Expanded the artifact folder layout: session vs Flow folders, manifest.json / commands.json, platform-specific logs, crash/ANR reports, screenshots, recordings, and AI analysis output.
• Updated guidance on --debug-output and --test-output-dir, including where session-wide vs per-Flow maestro.log files land.

Commands: assertScreenshot

• thresholdPercentage is documented as a Number (default 95) that can come from a variable or JavaScript expression.
• Added usage examples: basic assert against a reference image, and setting the threshold from env.
• Noted that a non-numeric threshold fails with Invalid thresholdPercentage for assertScreenshot instead of falling back to the default.

Permissions

• Documented that permission values (for example on launchApp) can be supplied from a variable or JavaScript expression, so one Flow can cover grant/deny paths via --env or a calling Flow’s env block.
• Minor cleanup of related-resource links and formatting.