B4: ship bridge packaging and smoke docs#148
Merged
Conversation
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
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
Operator Paths
Verification
Upgrade Overview
Protected Areas
Compatibility Impact
This is a bridge-phase packaging and enablement closeout. It does not reopen B1 through B3 implementation architecture; it documents the shipped provider-plus-MCP path as the recommended deployment shape and clarifies the MCP-only fallback.
Migration / Rollout
Publish the updated docs, config examples, smoke helpers, and demo helper together so operators can follow one consistent bridge setup path. No feature-surface migration beyond the documented MCP-only to provider-plus-MCP path is introduced here.
Operator Action
Follow the operator guide, choose the recommended provider_plus_mcp path where possible, use the documented mcp_only fallback only when required, and validate the environment with the provider smoke, MCP smoke, and one-command bridge demo.
Validation
Branch-local verification passed:
Rollback
Revert the squash merge commit to restore the pre-B4 docs and smoke helper state, then rerun the smoke scripts and demo helper before redistributing operator guidance.