@bdayadev/flutter-ultra-mcp 0.0.0

package/.claude-plugin/plugin.json

@@ -0,0 +1,14 @@
+{
+  "$schema": "https://json.schemastore.org/claude-code-plugin-manifest.json",
+  "name": "flutter",
+  "version": "0.1.0",
+  "description": "Durable cross-platform Flutter automation via 8 specialized MCP servers, in-app mixin binding, and an optional DevTools panel. Replaces marionette_mcp and the official dart mcp-server for Claude Code.",
+  "author": {
+    "name": "Bdaya-Dev",
+    "url": "https://github.com/Bdaya-Dev"
+  },
+  "homepage": "https://github.com/Bdaya-Dev/flutter-ultra-mcp",
+  "repository": "https://github.com/Bdaya-Dev/flutter-ultra-mcp",
+  "license": "Apache-2.0",
+  "keywords": ["flutter", "dart", "mcp", "automation", "testing", "devtools", "claude-code"]
+}

package/.mcp.json

@@ -0,0 +1,67 @@
+{
+  "mcpServers": {
+    "flutter-ultra-build": {
+      "command": "node",
+      "args": ["${CLAUDE_PLUGIN_ROOT}/packages/flutter-ultra-build/dist/index.js"],
+      "env": {
+        "FLUTTER_ULTRA_DATA": "${CLAUDE_PLUGIN_DATA}"
+      }
+    },
+    "flutter-ultra-runtime": {
+      "command": "node",
+      "args": ["${CLAUDE_PLUGIN_ROOT}/packages/flutter-ultra-runtime/dist/bin.js"],
+      "env": {
+        "FLUTTER_ULTRA_DATA": "${CLAUDE_PLUGIN_DATA}",
+        "FLUTTER_ULTRA_STATE_DIR": "${CLAUDE_PLUGIN_DATA}/state"
+      }
+    },
+    "flutter-ultra-gesture": {
+      "command": "node",
+      "args": ["${CLAUDE_PLUGIN_ROOT}/packages/flutter-ultra-gesture/dist/bin.js"],
+      "env": {
+        "FLUTTER_ULTRA_STATE_DIR": "${CLAUDE_PLUGIN_DATA}/state"
+      }
+    },
+    "flutter-ultra-browser": {
+      "command": "node",
+      "args": ["${CLAUDE_PLUGIN_ROOT}/packages/flutter-ultra-browser/dist/bin.js"],
+      "env": {
+        "PLAYWRIGHT_BROWSERS_PATH": "${CLAUDE_PLUGIN_DATA}/browsers",
+        "FLUTTER_ULTRA_STATE_DIR": "${CLAUDE_PLUGIN_DATA}/state"
+      }
+    },
+    "flutter-ultra-native-mobile": {
+      "command": "node",
+      "args": ["${CLAUDE_PLUGIN_ROOT}/packages/flutter-ultra-native-mobile/dist/bin.js"],
+      "env": {
+        "FLUTTER_ULTRA_GO_IOS_BIN": "${CLAUDE_PLUGIN_ROOT}/sidecars/go-ios",
+        "FLUTTER_ULTRA_STATE_DIR": "${CLAUDE_PLUGIN_DATA}/state"
+      }
+    },
+    "flutter-ultra-native-desktop": {
+      "command": "node",
+      "args": ["${CLAUDE_PLUGIN_ROOT}/packages/flutter-ultra-native-desktop/dist/bin.js"],
+      "env": {
+        "FLUTTER_ULTRA_MAC_HELPER": "${CLAUDE_PLUGIN_ROOT}/sidecars/mac-helper/flutter-ultra-mac",
+        "FLUTTER_ULTRA_LINUX_HELPER": "${CLAUDE_PLUGIN_ROOT}/sidecars/linux-helper/at-spi-bridge.py",
+        "FLUTTER_ULTRA_STATE_DIR": "${CLAUDE_PLUGIN_DATA}/state"
+      }
+    },
+    "flutter-ultra-devtools": {
+      "command": "node",
+      "args": ["${CLAUDE_PLUGIN_ROOT}/packages/flutter-ultra-devtools/dist/index.js"],
+      "env": {
+        "FLUTTER_ULTRA_STATE_DIR": "${CLAUDE_PLUGIN_DATA}/state"
+      }
+    },
+    "flutter-ultra-patrol": {
+      "command": "node",
+      "args": ["${CLAUDE_PLUGIN_ROOT}/packages/flutter-ultra-patrol/dist/bin.js"],
+      "env": {
+        "FLUTTER_ULTRA_STATE_DIR": "${CLAUDE_PLUGIN_DATA}/state",
+        "FLUTTER_ULTRA_PATROL_FORK": "${CLAUDE_PLUGIN_ROOT}/vendor/patrol",
+        "PATROL_WEB_BROWSER_ARGS": "--enable-unsafe-swiftshader,--disable-renderer-backgrounding,--disable-background-timer-throttling"
+      }
+    }
+  }
+}

package/CODE_OF_CONDUCT.md

@@ -0,0 +1,83 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+We as members, contributors, and leaders pledge to make participation in our community a harassment-free experience for everyone, regardless of age, body size, visible or invisible disability, ethnicity, sex characteristics, gender identity and expression, level of experience, education, socio-economic status, nationality, personal appearance, race, caste, color, religion, or sexual identity and orientation.
+
+We pledge to act and interact in ways that contribute to an open, welcoming, diverse, inclusive, and healthy community.
+
+## Our Standards
+
+Examples of behavior that contributes to a positive environment for our community include:
+
+- Demonstrating empathy and kindness toward other people
+- Being respectful of differing opinions, viewpoints, and experiences
+- Giving and gracefully accepting constructive feedback
+- Accepting responsibility and apologizing to those affected by our mistakes, and learning from the experience
+- Focusing on what is best not just for us as individuals, but for the overall community
+
+Examples of unacceptable behavior include:
+
+- The use of sexualized language or imagery, and sexual attention or advances of any kind
+- Trolling, insulting or derogatory comments, and personal or political attacks
+- Public or private harassment
+- Publishing others' private information, such as a physical or email address, without their explicit permission
+- Other conduct which could reasonably be considered inappropriate in a professional setting
+
+## Enforcement Responsibilities
+
+Community leaders are responsible for clarifying and enforcing our standards of acceptable behavior and will take appropriate and fair corrective action in response to any behavior that they deem inappropriate, threatening, offensive, or harmful.
+
+Community leaders have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, and will communicate reasons for moderation decisions when appropriate.
+
+## Scope
+
+This Code of Conduct applies within all community spaces, and also applies when an individual is officially representing the community in public spaces. Examples of representing our community include using an official e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be reported to the community leaders responsible for enforcement at https://github.com/Bdaya-Dev/flutter-ultra-mcp/security/advisories/new. All complaints will be reviewed and investigated promptly and fairly.
+
+All community leaders are obligated to respect the privacy and security of the reporter of any incident.
+
+## Enforcement Guidelines
+
+Community leaders will follow these Community Impact Guidelines in determining the consequences for any action they deem in violation of this Code of Conduct:
+
+### 1. Correction
+
+**Community Impact**: Use of inappropriate language or other behavior deemed unprofessional or unwelcome in the community.
+
+**Consequence**: A private, written warning from community leaders, providing clarity around the nature of the violation and an explanation of why the behavior was inappropriate. A public apology may be requested.
+
+### 2. Warning
+
+**Community Impact**: A violation through a single incident or series of actions.
+
+**Consequence**: A warning with consequences for continued behavior. No interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, for a specified period of time. This includes avoiding interactions in community spaces as well as external channels like social media. Violating these terms may lead to a temporary or permanent ban.
+
+### 3. Temporary Ban
+
+**Community Impact**: A serious violation of community standards, including sustained inappropriate behavior.
+
+**Consequence**: A temporary ban from any sort of interaction or public communication with the community for a specified period of time. No public or private interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, is allowed during this period. Violating these terms may lead to a permanent ban.
+
+### 4. Permanent Ban
+
+**Community Impact**: Demonstrating a pattern of violation of community standards, including sustained inappropriate behavior, harassment of an individual, or aggression toward or disparagement of classes of individuals.
+
+**Consequence**: A permanent ban from any sort of public interaction within the community.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 2.1, available at [https://www.contributor-covenant.org/version/2/1/code_of_conduct.html][v2.1].
+
+Community Impact Guidelines were inspired by [Mozilla's code of conduct enforcement ladder][Mozilla CoC].
+
+For answers to common questions about this code of conduct, see the FAQ at [https://www.contributor-covenant.org/faq][FAQ]. Translations are available at [https://www.contributor-covenant.org/translations][translations].
+
+[homepage]: https://www.contributor-covenant.org
+[v2.1]: https://www.contributor-covenant.org/version/2/1/code_of_conduct.html
+[Mozilla CoC]: https://github.com/mozilla/diversity
+[FAQ]: https://www.contributor-covenant.org/faq
+[translations]: https://www.contributor-covenant.org/translations

package/CONTRIBUTING.md

@@ -0,0 +1,108 @@
+# Contributing to flutter-ultra-mcp
+
+Thanks for considering a contribution! This guide covers everything you need to develop, test, and ship changes.
+
+## Prerequisites
+
+- **Node.js** 20 or 22 (LTS)
+- **Flutter** stable channel
+- **Dart** 3.5+
+- Git with submodule support
+- Platform-specific tooling for the server you're working on (e.g. Android SDK + `adb` for `flutter-ultra-native-mobile`)
+
+You do not need any Bdaya internal resources. This plugin is fully self-sufficient — a fresh clone, `npm install`, and `npm test` is enough.
+
+## Clone
+
+```bash
+git clone https://github.com/Bdaya-Dev/flutter-ultra-mcp.git
+cd flutter-ultra-mcp
+git submodule update --init --recursive
+npm install
+```
+
+## Repository layout
+
+```
+.claude-plugin/      Plugin manifest
+.mcp.json            Declares all 8 MCP servers
+packages/            8 MCP server packages + 3 Dart packages
+shared/              TS shared libs (vm-service-client, mcp-runtime, state-store, keyring)
+skills/              Claude Code skills (one folder per skill)
+hooks/               PreToolUse / SessionStart / Stop hook configs
+sidecars/            Bundled native helpers (signed/notarized in CI)
+vendor/              Plugin-owned dependencies (e.g. patrol fork submodule)
+scripts/             Cross-platform helper scripts referenced by hooks
+docs/                Architecture + contracts + platform matrix
+.github/workflows/   GitHub Actions CI (per §18.12 of plan)
+```
+
+## Conventional Commits — mandatory
+
+Every commit must follow [Conventional Commits 1.0](https://www.conventionalcommits.org/).
+
+```
+<type>(<scope>)?: <subject>
+```
+
+| Type                                                        | Effect on version | Example                                            |
+| ----------------------------------------------------------- | ----------------- | -------------------------------------------------- |
+| `feat`                                                      | minor bump        | `feat(gesture): add scroll_until_visible`          |
+| `fix`                                                       | patch bump        | `fix(runtime): handle DDS reconnect race`          |
+| `feat!` / `fix!` / `BREAKING CHANGE:` footer                | major bump        | `feat(api)!: rename screenshot to take_screenshot` |
+| `perf`                                                      | patch bump        | `perf(browser): cache Playwright contexts`         |
+| `refactor`, `docs`, `test`, `chore`, `build`, `ci`, `style` | no version change | `chore(deps): bump zod to 3.25`                    |
+
+`commitlint` runs as a `commit-msg` hook (installed by `husky`) and as a PR-blocking CI check.
+
+## Branches
+
+- **`main`** — production
+- **`next`** — pre-release (prerelease tag `next`)
+- **`alpha`** / **`beta`** — unstable channels
+
+## Adding a new MCP server
+
+1. Copy the layout of an existing `packages/flutter-ultra-*/` package
+2. Add an entry to `.mcp.json` at the repo root
+3. Add a `tsconfig.json` project reference in the root `tsconfig.json`
+4. Implement tools using `@flutter-ultra/mcp-runtime` scaffolding
+5. Add unit + integration tests under `packages/<name>/tests/`
+6. Update `skills/` for any user-facing workflows
+
+## Adding a new skill
+
+Skills are markdown files at `skills/<name>/SKILL.md`. Follow the conventions in plan §16.8.
+
+## Local testing
+
+```bash
+# Build all packages
+npm run build
+
+# Run all unit + integration tests
+npm test
+
+# Run a single package's tests
+npm test --workspace=@flutter-ultra/runtime
+
+# Lint + format
+npm run lint
+npm run format
+```
+
+Use `npx @modelcontextprotocol/inspector --cli node packages/<name>/dist/index.js --method tools/list` to smoke-test a built server.
+
+## Pull requests
+
+1. Add a [changeset](https://github.com/changesets/changesets): `npm run changeset`
+2. All CI gates must pass (lint, unit, integration, contract, coverage thresholds, MCP Inspector smoke).
+3. Squash-merge with a Conventional Commits subject. Reviewers will preserve the conventional commit by editing the merge subject if needed.
+
+## Code of Conduct
+
+This project adopts the [Contributor Covenant 2.1](CODE_OF_CONDUCT.md). By participating you agree to abide by its terms.
+
+## License
+
+Contributions are licensed under Apache-2.0 (see [LICENSE](LICENSE)).

package/LICENSE

@@ -0,0 +1,201 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

package/README.md

@@ -0,0 +1,77 @@
+# flutter-ultra-mcp
+
+> Durable cross-platform Flutter automation for Claude Code — 8 specialized MCP servers, an in-app Dart mixin binding, and an optional DevTools panel. Replaces `marionette_mcp` and the official `dart mcp-server` with a crash-resilient multi-process architecture.
+
+[![License: Apache 2.0](https://img.shields.io/badge/License-Apache_2.0-blue.svg)](https://opensource.org/licenses/Apache-2.0)
+[![Plugin: Claude Code](https://img.shields.io/badge/Claude_Code-plugin-7C3AED.svg)](https://docs.claude.com/en/docs/claude-code)
+
+## Why
+
+A monolithic Flutter MCP server crashes badly: a malformed `pubspec.yaml` or a flaky AT-SPI binding takes down hot reload, gestures, browser, **and** native automation. We split the surface across **8 MCP servers** so a Linux AT-SPI regression cannot stop your Android tests, and a broken pubspec cannot block your hot reload.
+
+| Server                         | Purpose                                                                   |
+| ------------------------------ | ------------------------------------------------------------------------- |
+| `flutter-ultra-build`          | pubspec, codegen, analyze, format, tests, builds, l10n, assets            |
+| `flutter-ultra-runtime`        | Attach to `flutter run` debug sessions over DDS; introspect VM Service    |
+| `flutter-ultra-gesture`        | Tap, text entry, scroll, screenshot via in-app `ultra_flutter` mixin      |
+| `flutter-ultra-browser`        | Playwright-driven web automation (OAuth redirects, popups, console)       |
+| `flutter-ultra-native-mobile`  | Native overlays on Android (UIAutomator) + iOS (XCUITest) via adb / xcrun |
+| `flutter-ultra-native-desktop` | Native UI on Windows (UIA), macOS (AX), Linux (AT-SPI)                    |
+| `flutter-ultra-devtools`       | Live MCP activity panel inside Flutter DevTools                           |
+| `flutter-ultra-patrol`         | Orchestrate `patrol_cli` for E2E tests (web + Android + iOS)              |
+
+## Install
+
+This is a Claude Code plugin. Install with:
+
+```bash
+/plugin install Bdaya-Dev/flutter-ultra-mcp
+```
+
+Or add via the marketplace:
+
+```bash
+/plugin marketplace add Bdaya-Dev/flutter-ultra-mcp
+/plugin install flutter
+```
+
+After install, the 8 MCP servers register automatically. Drop into any Flutter project, start a debug session, and ask Claude to take a screenshot, scroll a list, or run your patrol suite.
+
+## Quick tour
+
+```bash
+# In a Flutter project
+flutter run -d chrome
+
+# Claude Code session — invoke any included skill
+/flutter:tour          # Route-by-route screenshot tour
+/flutter:drive         # Multi-step user flow automation
+/flutter:debug         # Attach + inspect + triage
+/flutter:test          # Test orchestration
+/flutter:setup         # One-command setup in a new codebase
+```
+
+## Architecture
+
+See [docs/architecture.md](docs/architecture.md) for the full design.
+
+## Documentation
+
+- [Architecture](docs/architecture.md)
+- [Contracts](docs/contracts/)
+- [Platform matrix](docs/platform-matrix.md)
+- [Migration from marionette_mcp](MIGRATION-marionette.md)
+- [Discovery empirics](docs/discovery-empirics.md)
+- [Upstream patrol PRs](docs/UPSTREAM-PATROL-PRS.md)
+
+## Contributing
+
+See [CONTRIBUTING.md](CONTRIBUTING.md) — commit message format, monorepo layout, local test workflow.
+
+## Security
+
+See [SECURITY.md](SECURITY.md) for the loopback-only design and the vulnerability reporting process.
+
+## License
+
+Apache-2.0. See [LICENSE](LICENSE) and the upstream notices in `NOTICE` (where applicable).

package/SECURITY.md

@@ -0,0 +1,19 @@
+# Security Policy
+
+## Reporting a vulnerability
+
+Please report suspected security issues privately via GitHub Security Advisories:
+
+https://github.com/Bdaya-Dev/flutter-ultra-mcp/security/advisories/new
+
+Do not open public issues for security reports.
+
+## Design posture
+
+flutter-ultra-mcp is local-only by design. The 8 MCP servers communicate with their target Flutter apps and helper processes over **loopback transports only** (Unix sockets, named pipes, localhost WebSocket). No server in the plugin opens a non-loopback listener.
+
+Secrets handled by the plugin (signing certs, OIDC tokens, etc.) are stored via the OS keyring through `@flutter-ultra/keyring` and are never written to the filesystem in plaintext.
+
+## Supported versions
+
+Only the latest published release on the `main` branch receives security updates.

package/dart/ultra_flutter/CHANGELOG.md

@@ -0,0 +1,34 @@
+# Changelog
+
+## 0.0.1-dev.1
+
+Initial fork of [`marionette_flutter`](https://github.com/leancodepl/marionette_mcp)
+v0.5.0 (Apache-2.0).
+
+### Breaking changes vs marionette
+
+- Binding is now a **mixin** (`mixin UltraFlutterBinding on WidgetsBinding`)
+  instead of a class. Apps that need other custom bindings (Sentry,
+  integration_test, etc.) compose via `extends WidgetsFlutterBinding with
+  ...`. The convenience `UltraFlutterBinding.ensureInitialized()` covers
+  the no-composition case.
+- Service extensions are now under `ext.flutter.ultra.*` instead of
+  `ext.flutter.marionette.*`.
+- `MarionetteBinding` → `UltraFlutterBinding`, `MarionetteConfiguration`
+  → `UltraConfiguration`, `MarionetteExtensionResult` →
+  `UltraExtensionResult`, `registerMarionetteExtension` →
+  `registerUltraExtension`.
+
+### Added
+
+- `ext.flutter.ultra.clearText` — convenience wrapper around
+  `enterText('')`, saves agents two round-trips.
+- Sentry composition: mix in `SentryWidgetsBindingMixin` directly (no
+  companion package needed).
+
+### Test coverage
+
+- 6 binding/configuration tests new for the mixin form.
+- 91 ported marionette service tests pass unchanged after the rename
+  pass.
+- Full suite: 97/97 green on Flutter stable.