Update to Autonom

{
  "description": "Design and run a layered Flutter test strategy across unit, widget, golden, integration, platform-channel, and native-UI tests with focused commands and reproducible device setup.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 189
    },
    {
      "relative_path": "references/testing-boundaries.md",
      "size_in_bytes": 758
    }
  ],
  "name": "flutter-testing",
  "skill_md_contents": "---\nname: flutter-testing\ndescription: Design and run a layered Flutter test strategy across unit, widget, golden, integration, platform-channel, and native-UI tests with focused commands and reproducible device setup.\n---\n\n# Flutter Testing\n\nPick the narrowest layer that proves the behavior.\n\n| Layer | Owns |\n| --- | --- |\n| unit | pure mapping, validation, state, repositories |\n| widget | UI states, semantics, forms, callbacks without a full device |\n| golden | visual contracts with pinned fonts/locale/size/renderer |\n| integration_test | full Flutter flows on a real target |\n| native | Kotlin/plugin implementation |\n| Patrol / Espresso / UI Automator | permissions, notifications, platform views |\n\n```bash\npython3 <marketplace-root>/scripts/flutter_exec.py --root . -- --version\n```\n\nRead `references/testing-boundaries.md` when Flutter and native UI meet.\n\n## Loop\n\n1. Read the change, acceptance criteria, nearby tests, past flakes.\n2. Draft happy / boundary / failure / lifecycle / a11y / platform cases.\n3. Implement highest-signal missing tests first.\n4. Run, refine once from failures, then widen the suite.\n\n## Commands\n\n```bash\nflutter test test/path/to/test.dart\nflutter test --plain-name \"specific behavior\"\nflutter test integration_test/app_test.dart -d <device-id>\n```\n\nUse `flutter drive` only when the project’s driver/lab requires it.\n\n## Stability\n\nPrefer type/text/semantics/key finders. Avoid unbounded `pumpAndSettle` when\nanimations or streams never idle. Control clocks, randomness, network, and\nstorage.\n\n## Platform channels\n\nFake the Dart side, unit-test native handlers, and keep one device path for\neach critical channel.\n"
}