Debug Handoff Packet Flow

# Browser-Specific Bug Reproduction Sheet

Browser-specific bugs are often reported as “it works on my machine.” That phrase hides the variables that matter: browser version, OS, viewport, extensions, auth state, network condition, and data state. A reproduction sheet makes those variables explicit.

## Minimum environment
Record browser name and version, OS, viewport size, device class, logged-in or logged-out state, and whether extensions were enabled. For mobile Safari or embedded webviews, include the device and app container when relevant.

## Steps and expected result
Write numbered steps from a clean start. Avoid vague actions like “open the settings.” Use labels the user can see. Expected behavior should be specific: modal opens, button becomes disabled, API call returns 201, focus moves to input.

## Observed result
Capture what happened and where the first divergence appeared. A screenshot can help, but a screenshot without the prior step is incomplete. If console errors or network failures appear, include a small log slice.

## Control test
Run the same steps in one other browser or profile when possible. If it fails only in Safari private mode or only with an extension, that is not a side note; it is the reproduction boundary.

## Practical format
Environment, Data setup, Steps, Expected, Observed, Not reproduced, Unknown. This structure keeps the report small while preserving the variables needed for real debugging.

Browser-Specific Bug Reproduction Sheet

// COMMENTS

ON THIS PAGE