ursa-dashboard STDERR block doesn't seem to ever fill

[ndebard]

@mikegros - i've never once seen the STDERR block in the dashboard and the fact that I at least see minimal (likely blank) text saying STDERR appearing in the STDOUT block, we probably have a bug here.

[mikegros]

I think that is not a bug but would definitely be a source of user confusion. The stderr log is set to catch stderr of the URSA process, whereas the stderr you see there is stderr from the URSA issued commands. That stderr (like failures in code URSA wrote that it will debug and fix) is returned to the user as stdout (a stdout print box with sections labeled stdout and stderr) as well as returned to the llm as a string in the URSA workflow.

The stderr log should capture things like URSA crashing if it happened.

That said, it's rare to see anything in the stderr log, which makes that box rarely useful.

I could see dropping it. We don't want to pipe that other stderr to it though because we want to see that associated with the relevant URSA issued commands.

[mikegros]

Fixed in #221 by just hiding the stderr log and cleaning up text there. It really gets little to no output so just takes up space and adds confusion.