[codex] Extract session broker surfaces#100
Conversation
|
To preview the documentation for this pull request, visit the following URL: docs.page/arenukvern/mcp_flutter~100
|
|
Important Review skippedDraft detected. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
# Conflicts: # packages/server_capability_core/pubspec.yaml # packages/server_capability_kernel/pubspec.yaml
- Adjusted project indexing in AGENTS.md to reflect updated symbol and relationship counts. - Updated CHANGELOG.md to document breaking changes in `flutter_mcp_core.dart` and the migration of canonical types to `intentcall_core`. - Added a new command in steward.yaml to check for stale local or root path dependencies in hosted IntentCall. - Updated README.md to reflect the new consumer package policy for IntentCall version 0.2.1. - Enhanced the gesture interaction service to handle web-specific scrolling actions and added new utility functions for semantic snapshot services. - Improved tests for registry discovery and semantic snapshot functionalities. - Cleaned up legacy artifacts in the exec sweep script and ensured proper version checks for IntentCall dependencies.
Summary
mcp_server_dart.validate-runtimefallback reporting so missing host context and helper retry details are visible instead of flattened into a generic screenshot failure.Why
Downstream tools need a reusable realtime broker/session foundation without importing Flutter-VM-shaped internals. This keeps Flutter-specific VM service, screenshots, and extension calls as adapters while consuming the shared session/result/registration surfaces through published IntentCall packages.
Validation
flutter pub getresolvesintentcall_core,intentcall_mcp, andintentcall_sessionfrom hostedhttps://pub.dev.dart analyze packages/server_capability_kernel packages/server_capability_core mcp_server_dart mcp_toolkitflutter test test/control_flow_service_test.dart test/agent_entry_helpers_test.dart test/mcp_toolkit_bootstrap_test.dart test/semantic_snapshot_surface_test.dartfrommcp_toolkitdart test mcp_server_dart/test/core_executor_test.dart mcp_server_dart/test/dynamic_registry_input_schema_test.dart mcp_server_dart/test/registry_discovery_service_test.dart mcp_server_dart/test/session_manager_test.dart mcp_server_dart/test/command_snapshot_service_test.dart mcp_server_dart/test/desktop_capture_recovery_test.dart mcp_server_dart/test/platform_view_capture_flow_test.dart mcp_server_dart/test/desktop_window_screenshot_test.dartdart test packages/server_capability_kernel/test packages/server_capability_core/test mcp_server_dart/test/agent_registry_host_test.dart mcp_server_dart/test/host_test.dart mcp_server_dart/test/host_extras_test.dart mcp_server_dart/test/flutter_inspector_resources_test.dartvalidate-runtimewithout global desktop flags:ok:true,verdict:pass_with_fallback, failure details now reportmissing_flutter_device.validate-runtimewith--flutter-device macos --flutter-project-dir flutter_test_app:ok:true,verdict:pass,captureMode:desktop_window, no fallback.scripts/run_exec_sweep.sh:PASS=35 FAIL=0 SKIP=0.steward probe --json --profile quickgit diff --checkNotes
GitNexus change detection originally reported CRITICAL for the branch because the PR intentionally touches the broader session/broker/dynamic-registry flow. The hosted-package integration itself reports low risk in change detection; the shim impact is medium because it feeds the capability-kernel public surface and is covered by capability/host registration tests.