Repository navigation
Conversation
Replace the screenshots, which showed a named machine and a thread ID, with captures of a synthetic demo-studio/atlas queue served by a fixture gh, and include docs/ in the package files. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This was referenced Oct 20, 2026
Owner
Author
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 changed
pull-requests/release tags enabled.Verification
plugin/pull-requestsartifact00d3cb9ffrom8f48e738; installed its detached checkout into fresh bbf9eae1c44.Screenshots needed
demo-studio/atlasrepository; PR 42 “Improve keyboard navigation”, passing CI, approved review, linked “Keyboard navigation” thread. Seed an isolated bb project with that synthetic remote and a localghfixture executable returning a synthetic viewer, search/read responses, and branch PR. Create the project through the isolated CLI, then seed one idle synthetic thread and ready environment in the fresh instance’s SQLite database; insert that synthetic thread ID into the fixture’s same-serverBB-Threadmarker. Start the isolated server with the fixture directory first in both its process PATH and its shell-resolved PATH. Name the source machine “Demo workstation”. Keep IDs, hostnames, paths, and account details out of the frame.src/navigation.tspatch from the fixture’s files response; select Changes for PR 42. Capture enough surrounding bb chrome to identify the surface without revealing identifiers.The assigned screenshot worker owns capture and image edits. Use real isolated bb UI, synthetic content only, images at least 1200 pixels wide and at most 2 MiB. Replace the existing personal-source screenshot and update repository references when capturing.
Fixes #484
Screenshots
Before:
main0cd4457, described in text because the old images show a named machine and a thread ID · After: b0ecc31 · Captured at 2× from an isolated bb (get-bb/bb main 46da8461) with this PR's build installed from source. A fixturegh(first on the server PATH and on the shell-resolved PATH, with an empty gh config) returned a synthetic viewer and thedemo-studio/atlasPRs 42–44; the "Keyboard navigation" thread was linked by bb's own branch lookup and the PR body's same-serverBB-Threadmarker. Machine named "Demo workstation". No GitHub account was used.This commit also adds
docsto the packagefilesand points the root catalog at the new images. With Needs attention on, only the failing PR 44 matches: the plugin doesn't count PR 43's pending review request as needing attention.BB-Thread-ID: thr_dk2hhevm82