{"id":77655,"plugin_id":"plugins_6ae8cc5ee77c81918ab31ed7701a28de","kind":"skill","collection_source":"plugin_package","comparison_source":null,"observed_at":"2026-11-03T00:15:27.375Z","digest":"1b15483f2e06f88be9d866d83487eeb9b96233a4d8c88bdbc0c4a471e9aa9fba","against":null,"payload":{"description":"Run reproducible functional, UI, accessibility, integration and platform-specific checks on websites, PWAs, native Apple, Android or cross-platform projects before handoff.","included_files":[],"name":"test-app","skill_md_contents":"---\nname: test-app\ndescription: Run reproducible functional, UI, accessibility, integration and platform-specific checks on websites, PWAs, native Apple, Android or cross-platform projects before handoff.\n---\n\n# Test App\n\n1. Read `../../references/testing-and-evidence.md` and `../../templates/evidence-report.md`; inspect scripts and environment capabilities.\n2. Select relevant test layers: formatting/typecheck, unit, API/integration, browser E2E, accessibility, visual screenshots, offline/PWA, Swift tests/Xcode UI tests, Android instrumentation/Compose UI tests.\n3. Execute real commands where supported. Store command, platform, dependency versions (when relevant), exit code, count and evidence paths. Never infer passing tests from code review.\n4. Distinguish PASS, FAIL, NOT RUN, BLOCKED and PARTIAL. For missing credentials or unavailable macOS simulator, mark appropriately and supply exact follow-up steps.\n5. Review security separately; prohibit release claims if critical broken flows, data-loss risk, failed security gates or build failure remain. Do not assert that passing tests proves universal correctness.\n6. Provide verification matrix, findings, fix/retest ledger, and honest release readiness statement.\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}