feat(product): ship transcript-first Braid terminal - #25
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.
What ships
Direct proof
pnpm check: 667 tests, 665 passed, 2 external-only rows skipped, 0 failed; 15/15 performance checks; 24/24 live-contract checks; CLI Bridge adversarial matrix passed./ask; 3/3 findings supported.The exact cloud artifact is committed at
artifacts/verification/live/tangle-sandbox-braid-execution-stress-production-20260812.json.Honest boundary
The current Tangle cloud route is ephemeral. Braid does not claim crash-safe cloud reattachment, checkpoint migration, or cloud fork until the shared provider exposes exact recovery and control. That work remains tracked in agent-runtime #800 and agent-sdk #146. Missing normalized tool-result parts remain tracked in agent-runtime #762.