Issues/feedback related to v0.3

[gobinoob]

Issues and feedback related v0.3

### Tasks
- [x] Readability of "Help" section needs to be improved
- [x] Behaviour of the "Instructions" section is inapproriate - it simply toggles between appearing and disappearing when "instructions" is clicked. And also it replaces the output section which loses results of the last run.
- [ ] Implement links for each example, in a way they can be shared individually
- [x] Advice provider example runs into failures
- [x] Std library example runs into failures
- [x] Behaviour of "proving" toast component when tried to prove on a failing code needs to be fixed
- [ ] The button to download the ".masm" files is counterintuitive - it is hardly recognizable as a download button
- [ ] According to its behaviour the collapse button in the input panel is supposed to change from "+" to "-" rather than changing its colour from green to grey.
- [ ] https://github.com/0xPolygonMiden/examples/issues/174
- [ ] The debug view has few areas where it can be fixed/improved: the relevance of green numbers at the initial stage is very less, the "|<" and "<<" buttons does not appear to work when pressed first - shall be disabled in that case,
- [ ] It's hard to understand what is the VM's stack when going backwards; esp. if the state is changed to use a table.
- [x] Using the buttons ">>" and ">|" seem to print only the last state of the VM. That is not super useful for debugging one wants to see all intermediary values.
- [x] Verification of the matrix multiplication doesn't work
- [x] There is no output shown when "Prove" button is clicked

[Dominik1999]

Behaviour of the "Instructions" section is inappropriate

Can you elaborate on this?

[Dominik1999]

"Proving" appears to blocks the browser as it runs in the render thread. Ideally proving should run on a worker thread.

I think for this point we need a different issue and maybe this can be done by our contractor even?

[gobinoob]

Behaviour of the "Instructions" section is inappropriate

Can you elaborate on this?

Behaviour of the "Instructions" section is inappropriate - it simply toggles between appearing and disappearing when "instructions" is clicked. And also it replaces the output section which loses results of the last run.

Maybe we need to think of a better way of handling the instruction section - right now, it just appears to interfering a program's flow of run/debug/prove/verify.
Since it's going to be a direct reference for the code, it may not be a good idea to handle it in a separate page like how "Help" is done .
Either we can reduce size of the "instruction section" so that it always sits along with the output/program info box on the right side or we can embed a CLI in the playground which can provide information(instructions being one of them) or a way of interfacing with the VM and rollup - sounds a bit advanced but I had this idea in the initial mockup.

[gobinoob]

"Proving" appears to blocks the browser as it runs in the render thread. Ideally proving should run on a worker thread.

I think for this point we need a different issue and maybe this can be done by our contractor even?

Maybe we can consider that too; they could have put more thought in their approach here so that it's structured well on the background. It is not entirely about the frontend/can be fixed just on the surface.