feat(prover-ray): added guest output to the public inputs

[Soleimani193]

This PR integrates guest output into the prover's public inputs.

Checklist

• I wrote new tests for my new core changes.
• I have successfully ran tests, style checker and build against my new changes locally.
• If this change is deployed to any environment (including Devnet), E2E test coverage exists or is included in this
  PR.
• I have informed the team of any breaking changes if there are any.

---

Note

High Risk
Changes how guest outputs enter the proof’s public inputs and adds a soundness-critical length constraint. A bug here could let a prover pick which output rows are attested.

Overview
Binds the guest program’s pub output memory into the prover’s public-input vector so verifiers see the values the guest wrote, in address order.

zkcdriver now records the single public-output memory (address + data columns) from the schema. risc5.RegisterGuestPublicOutputs pins that memory to a fixed length (NumGuestPublicOutputs) and opens each data cell as a public input; without the length constraint a prover could grow the left-padded module and choose which rows become public. GetGuestPublicOutputs reads those constrained cells rather than the tracer’s output map.

Core.New registers this binding after the arithmetization is defined. Tests cover a matching 8-byte guest and a 9-byte guest that must fail both verification and the length check.

^{Reviewed by Cursor Bugbot for commit 4de9319. Bugbot is set up for automated code reviews on this repo. Configure here.}

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!