v1.1.0

Swipium 1.1.0

Expands the public MCP tool surface from 42 to 59 tools, advancing the roadmap's device-parity, visual-intelligence, seeded-state, and reporting phases. The additions are backward compatible — existing tools, input schemas, and consent gates are unchanged, so 1.0.1 clients keep working and pick up the new tools after a restart.

Added

• Device / app environment parity (no raw adb / simctl): qa_device_info, qa_permissions, qa_orientation, qa_geolocation, qa_network, qa_metro, qa_app_control, qa_screen_info, qa_screen_record. Mutating actions are consent-gated and recorded; network changes are auto-restored at report end.
• Local-first visual intelligence: qa_visual (baseline capture, regression diff, image-target matching with tappable coordinates, optional OCR) and qa_visual_find_text (OCR text location with coordinate-space conversion).
• Seeded state: qa_seed, qa_state_prepare, qa_state_verify, qa_state_teardown — create and verify a precondition instead of only reporting it as missing. All mutating actions are consent-gated.
• Report history: qa_report_compare (diff a run against a baseline report) and qa_run_history (pass rate, failures, flaky flows, confidence calibration).
• New MCP prompt swipium_guardrail_validation for a non-destructive bundle-loss guardrail check on debug RN/Expo builds.

Fixed

• qa_metro stop now signals the whole detached process group, terminating the Metro bundler on port 8081 rather than only its npx launcher, and only signals a PID still confirmed to be a Metro/Node process; Swipium-started Metro is also stopped on server shutdown.
• qa_screen_record status reports an auto-stopped Android time-limit recording honestly while retaining the entry so the video can still be saved.
• iOS WDA text entry, Expo iOS build reporting, structured iOS attach timing, and report verdict bucketing fixes carried from the same line of work.

Mutating device, network, and seed actions remain consent-gated with auto-restore. Remote AI vision, Maestro interop, real-device, and ticket workflows stay out of the public surface.