Co-authored-by: Frank Laub <flaub@risc0.com>

* Upgrade docusaurus to 3.0
* Use multi-instance to split versioned from unversioned content
* Split unversioned files into resources directory
* Snap version 0.19

* Add redirects for links to `/api` content
* Update current version links (i.e. main/0.18 -> 0.19)

Change `cargo install cargo-risczero` to `cargo binstall cargo-risczero`

---------

Co-authored-by: Frank Laub <flaub@risc0.com>

This is the beginning of a technical specification of the zkVM as an
execution environment. In this document, I assume that the reader to
understands systems programming terminology but I've added a reference
to OsDevWiki as a resource for those who may not be familiar with the
terminology.

closes: #1035

---------

Co-authored-by: Frank Laub <flaub@risc0.com>

Update Hello world tutorial, move it from GitHub to the docs

Closes #1027

---------

Co-authored-by: Erik Kaneda <erik@risczero.com>
Co-authored-by: Frank Laub <flaub@risc0.com>

It seems that journal is where we put the public outputs, rather than
the private outputs, based on the contexts?

This is an edit to guest-code-101.md.

* Use SHA-256 for internal proving tests (2x faster than poseidon)
* Avoid hanging cargo-risczero tests waiting on stdin
* Avoid building `risc0-zkvm` twice with and without the "prove" feature

Software ecalls should only send data from valid guest addresses.
Restrict this
by checking at the SyscallContext trait so all software ecall handlers
exhibit
this property.

Fixes: risc0/risczero-wip#385

---------

Co-authored-by: Frank Laub <flaub@risc0.com>

- Update Bonsai docs
- Update Bonsai Ethereum Relay README

---------

Co-authored-by: Tim Zerrell <tim.zerrell@risczero.com>
Co-authored-by: Frank Laub <flaub@risc0.com>

Installation of RISC Zero software is outlined as a part of the zkvm
overview page. Link example READMEs to this page.

Closes: #1088

* Fix doc job: install foundry toolchain
* Fix broken links

Co-authored-by: Roy Rotstein <royrotstein@Roys-MacBook-Pro-2.local>
Co-authored-by: Frank Laub <flaub@risc0.com>

Previously, sys_log printed the message via println!. This change writes
sys_log to whatever stdout is pointing to so that the output can be
captured in the same manner in as how user specifies stdout to be
handled.

Closes: #1028

---------

Co-authored-by: Frank Laub <flaub@risc0.com>