docs(plugin): add SCOPE.md + compose-with-expo-widgets runbook#49
Merged
Conversation
Formalizes the boundary between expo-assistant (invocation surface) and adjacent packages (expo-widgets, expo-av, expo-notifications). Prerequisite context for the rescoping of #32, #33, #34 and the upcoming #30 work. - plugin/SCOPE.md: MUST DO / MUST NOT DO tables, integration patterns for expo-widgets + expo-av, peer-dep policy (prebuild-time check vs runtime coupling), update protocol when boundaries shift - runbook/compose-with-expo-widgets.md: end-to-end integration runbook for the kind-string seam pattern between the two plugins - plugin/AGENTS.md: directs contributors to read SCOPE.md before adding any feature; cross-reference entries for both new docs
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
plugin/SCOPE.md— formalizes the boundary between expo-assistant (the invocation surface owner: AppIntents, AppShortcuts, EntityQuery bridges) and adjacent packages that own presentation surfaces (expo-widgets,expo-av/expo-audio,expo-notifications). MUST DO / MUST NOT DO tables, integration patterns, peer-dependency policy (prebuild-time check rather than runtime coupling), and an update protocol for when boundaries shift.runbook/compose-with-expo-widgets.md— end-to-end integration runbook for the kind-string seam pattern when composing expo-assistant with expo-widgets. Covers install, app.json configuration, JS resolver wiring, verification, and troubleshooting for theWidgetConfigurationIntentcompose case (feat(ios): WidgetConfigurationIntent + Widget Extension scaffolding #33).plugin/AGENTS.md— directs contributors to read SCOPE.md before adding any feature; cross-reference entries for both new docs.Why now
Prerequisite context for the rescoping of #32, #33, #34 that already landed as issue body updates, and for the upcoming #30 (AssistantSchemas) implementation work. Without the boundary doc in main, future contributors will keep relitigating scope decisions per-issue rather than reaching for a single source of truth.
Linked issues
Test plan
🤖 Generated with Claude Code