validateIntegration
Validate integration readiness before testing: checks manifest, dependencies, permissions, and toolchain, returning a graded report with errors/warnings to prevent failed test runs.
Instructions
Pre-test gate that runs ~15 severity-tiered checks over the whole project — manifest present + parses, generated-file markers + hashes, dependency declared, library-version freshness, Android Meta-DAT repo declaration, bootstrap wiring (ExtentosGlasses.create / Extentos.create), connection-page config, toolchain (AGP/Gradle) floors, foreground-service hints, and permissions. The permissions check DERIVES the permissions your declared capabilities imply and verifies they're present in the REAL app/src/main/AndroidManifest.xml elements (Android) or the app target's Info.plist keys (iOS) — the runtime source of truth, not the manifest JSON's permissions array. Returns { valid, checks, summary }: each checks[] entry is { name, passed, severity?: 'error' | 'warn' | 'info', details?, fix? }. valid is true when zero ERROR-severity checks fail; warn/info are advisories that don't block. summary reads 'Safe to test' ONLY at zero warnings — any warning demotes it to 'review before testing'. So treat this as a graded readiness report, not a binary pass/fail. USE after making changes, before testing. DON'T USE for reading state without judging it (use inspectIntegration).
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| projectPath | No | Absolute (or cwd-relative) path to the project root. Optional — defaults to the MCP server's current working directory (process.cwd()); pass it explicitly whenever the project isn't the cwd. |