feat: MCP server — docs + introspection tooling for flex_track

[alirezat66]

Summary

Provide a Model Context Protocol (MCP) integration so editors/agents can reliably answer questions about flex_track (APIs, routing, events, troubleshooting) with structured tools/resources.

Problem

• Large README + deep routing model is hard for humans and tools to navigate consistently.
• Teams want repeatable “assistant-grade” guidance tied to this package’s semantics.

Goals

• MVP: read-only resources (docs excerpts, checklists, links to pub.dev API).
• Safe defaults: no surprise network calls; local-first operation.
• Maintainable: clear ownership + CI smoke where feasible.

Non-goals (MVP)

• Arbitrary remote code execution, or sending real analytics traffic from MCP tools.

Acceptance criteria

• Publishable artifact documented (choose one: dart run …, separate package under /packages, or Node MCP — document install/run).
• Tooling surface documented in repo README (“Editor integration”).
• Security posture documented: local-only by default; any future “dry-run event” tool is explicitly scoped and safe.
• Resources/tools list includes at minimum: quickstart, routing concepts, consent flags, widget wrappers, inspector notes.
• Smoke verification documented (manual steps acceptable for MVP; optional CI).

Stretch (later)

• Optional tool: structured debugEvent-like dry run from JSON payload (debug builds only).

---

Scope suggestion

- Start as a sibling package/repo if it avoids bloating the core SDK tarball.