Flutter MCP Toolkit changelog

package_identifier

ghcr.io/arenukvern/flutter-mcp-toolkit:7.0.1 → ghcr.io/arenukvern/flutter-mcp-toolkit:7.1.1

version

7.0.1 → 7.1.1

https://docs.page/llms.txt

+ - [Set up a site](https://use.docs.page/quickstart.md): quickstart in Markdown

package_identifier

ghcr.io/arenukvern/flutter-mcp-toolkit:7.0.0 → ghcr.io/arenukvern/flutter-mcp-toolkit:7.0.1

version

7.0.0 → 7.0.1

https://raw.githubusercontent.com/arenukvern/mcp_flutter/HEAD/AGENTS.md

− This project is indexed by GitNexus as **mcp_flutter** (4960 symbols, 10728 relationships, 300 execution flows). Use the GitNexus MCP tools to understand code, assess impact, and navigate safely.− > If any GitNexus tool warns the index is stale, run `npx gitnexus analyze` in terminal first.− - **MUST run impact analysis before editing any symbol.** Before modifying a function, class, or method, run `gitnexus_impact({target: "symbolName", direction: "upstream"})` and report the blast radius (direct callers, affected processes, risk level) to the user.− - **MUST run `gitnexus_detect_changes()` before committing** to verify your changes only affect expected symbols and execution flows.− - When exploring unfamiliar code, use `gitnexus_query({query: "concept"})` to find execution flows instead of grepping. It returns process-grouped results ranked by relevance.− - When you need full context on a specific symbol — callers, callees, which execution flows it participates in — use `gitnexus_context({name: "symbolName"})`.− - NEVER edit a function, class, or method without first running `gitnexus_impact` on it.− - NEVER rename symbols with find-and-replace — use `gitnexus_rename` which understands the call graph.− - NEVER commit changes without running `gitnexus_detect_changes()` to check affected scope.− | Visual harness maintenance | `docs/superpowers/plans/2026-05-26-visual-reconstruct-next.md` |+ This project is indexed by GitNexus as **mcp_flutter** (5951 symbols, 12839 relationships, 300 execution flows). Use the GitNexus MCP tools to understand code, assess impact, and navigate safely.+ > Index stale? Run `node .gitnexus/run.cjs analyze` from the project root — it auto-selects an available runner. No `.gitnexus/run.cjs` yet? `npx gitnexus analyze` (npm 11 crash → `npm i -g gitnexus`; #1939).+ - **MUST run impact analysis before editing any symbol.** Before modifying a function, class, or method, run `impact({target: "symbolName", direction: "upstream"})` and report the blast radius (direct callers, affected processes, risk level) to the user.+ - **MUST run `detect_changes()` before committing** to verify your changes only affect expected symbols and execution flows. For regression review, compare against the default branch: `detect_changes({scope: "compare", base_ref: "main"})`.+ - When exploring unfamiliar code, use `query({search_query: "concept"})` to find execution flows instead of grepping. It returns process-grouped results ranked by relevance.+ - When you need full context on a specific symbol — callers, callees, which execution flows it participates in — use `context({name: "symbolName"})`.+ - For security review, `explain({target: "fileOrSymbol"})` lists taint findings (source→sink flows; needs `analyze --pdg`).+ - NEVER edit a function, class, or method without first running `impact` on it.+ - NEVER rename symbols with find-and-replace — use `rename` which understands the call graph.+ - NEVER commit changes without running `detect_changes()` to check affected scope.+ | Automation chain (harness, drivers, oka) | `docs/start_here/automation_chain.mdx` · skill `flutter-mcp-automation-chain` · `packages/harness/` |

package_identifier

ghcr.io/arenukvern/flutter-mcp-toolkit:6.0.0 → ghcr.io/arenukvern/flutter-mcp-toolkit:7.0.0

version

6.0.0 → 7.0.0

package_identifier

ghcr.io/arenukvern/flutter-mcp-toolkit:5.1.0 → ghcr.io/arenukvern/flutter-mcp-toolkit:6.0.0

version

5.1.0 → 6.0.0