In the Debugger tab, the DebuggerControls bar has an abbreviated mode that is triggered by mediumDeviceWidth
This static width constraint causes an issue because the DebuggerControls bar can be pushed outside of the window bounds by changing the size the the left pane

A more dynamic approach is needed to trigger the abbreviation so that the bar has the best chance of fitting in the remaining space.
It also may be worth investigating whether we can scroll if the abbreviated bar ever does get pushed off the the screen)
Discussion
@jacob314 proposed:
You can probably do something reasonable with InheritedWidget so that the constraints of the right ancestor widget are used to determine what needs to be >1300 pixels instead of relying on the overall window width.
quick summary of what design could work: Inherited widget is just something like class MaxWidth extends InheritedWidget
and the default way to create the MaxWidget is just an AutoMaxWidth widget that uses a LayoutBuilder to figure out what the max width is.
In the Debugger tab, the DebuggerControls bar has an abbreviated mode that is triggered by mediumDeviceWidth
This static width constraint causes an issue because the DebuggerControls bar can be pushed outside of the window bounds by changing the size the the left pane

A more dynamic approach is needed to trigger the abbreviation so that the bar has the best chance of fitting in the remaining space.
It also may be worth investigating whether we can scroll if the abbreviated bar ever does get pushed off the the screen)
Discussion
@jacob314 proposed: