Repository navigation
chore: version packages - #16
Open
github-actions[bot] wants to merge 1 commit into
Open
github-actions[bot] wants to merge 1 commit into
github-actions[bot] wants to merge 1 commit into
Conversation
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
November 6, 2026 17:27
6288159 to
0007ff6
Compare
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
November 6, 2026 17:28
0007ff6 to
0bb156b
Compare
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.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
stuntdouble@0.4.0
Minor Changes
#18
8470d0bThanks @mrprkr! - Each browser step in a run'sactivity.jsonlnow records the page's address (without its query) and title after the step, how long the page kept it waiting (navigations and load states, not fixed pauses), and, for a step that moves the page without typing, a small picture understeps/.run.jsongains"revision": 2and keeps its format, so earlier viewers still read it.#19
80a94efThanks @mrprkr! - Local interviews:.stuntdouble/interviews/<slug>.jsonholds a guide of questions and tasks, and four new MCP tools (start_interview,answer_item,rate_usability,finish_interview) have the actor answer it in character in your own agent's session, then rate the UMUX or UMUX-Lite statements, scored by the same code as the cloud. Each session is written to.stuntdouble/interview-runs/<stamp>-<interview>/interview.json, and the viewer serves it at/api/interview-runs.#17
c9d3fcaThanks @mrprkr! - The run page now leads with highlights (the actor's summary, what needs attention, what it observed and the longest wait), then the score, then tabs for results, the journey, screenshots and activity. The journey draws the pages opened, the browser steps and each verdict with its screenshot on one rail, with the waits between them, as the Stunt Double web report does.