Conversation
brsbl
added this pull request to stack #3532
September 11, 2026 20:31
…-composers-sidebar-thr_8j56at3ii2
…-composers-sidebar-thr_8j56at3ii2
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.
Human comments
What was wrong
The app shared one New thread composer buffer across panes. A second draft could replace the first, and saved draft resources had no app navigation or lifecycle discovery.
What changed
sdk.drafts.open,bb thread draft open --split, and inspect/set/reset parity forsidebar.lifecycleFilter.This layer depends only on the durable resource foundation. Core palette delivery remains independent; its coordinated draft/filter adapter follows separately.
How you verified
Current head
79b0dd25a4f30045cc2204bee3dc7caa9ceaf318is verified against parentd70cb6fe262bf3ad7ad98d29c820dd2c63bd94ec. Both incorporate main’s machine-provider release.Focused verification and review disposition
The isolated branch app was launched with
scripts/bb-dev-app currentusing Node 22.19.0. Browser checks used one Chrome for Testing profile, with 1440 × 960 desktop and 390 × 844 phone CSS viewports at 2× density.Review fixes were limited to passive recovery ownership, archived-pane identity, fresh split activation, project creation in the current draft, dependent reasoning selection, and ready-provider initialization.
P2 follow-up, intentionally excluded: independent browser stores with identical legacy prompt bytes but different options can collide on the import identity. The server rejects the mismatched retry and the local bytes remain preserved.
No local tests, typechecks, or lint were run. Browser fault injection blocked only an owned draft's save URL. The native folder picker was cancelled in the isolated daemon to exercise the real path-entry fallback. Temporary synthetic submission/project fixtures were removed.
Before and after
Both revisions use the same isolated fixture data, route
/?draft=drf_ui_regression_list, theme, viewport, and layout-restore sequence. Before is parent headd70cb6fe262bf3ad7ad98d29c820dd2c63bd94ec; after is exact head79b0dd25a4f30045cc2204bee3dc7caa9ceaf318. Desktop restoration previously shared the singleton; compact restoration previously returned to the welcome state.Compact lifecycle controls, after opting into Drafts and Archived:
BB-Thread-ID: thr_8j56at3ii2