Results 11 issues of duc-nx

Summary: Add Benchmark.md up to 13-th Fibonacci number.

### What is the problem? At the moment, in SDK, the host will have to add postcard in #276 . When user modify/update the `postcard` crate, it is not guarantee...

Summary: Test Plan: --- [//]: # (BEGIN SAPLING FOOTER) Stack created with [Sapling](https://sapling-scm.com). Best reviewed with [ReviewStack](https://reviewstack.dev/nexus-xyz/nexus-zkvm/pull/267). * #270 * __->__ #267 * #266 * #265

benchmark

Summary: This PR add continous profiling benchmark to CI, so we can track the performanc regression overtime. Test Plan:

### What is the problem? Improve system call interface. System call interface is a layer where guest can communicate to host via: - Precompile - Profile - Benchmark - .......

### What is the problem? Can't compile Jolt. Reproduce commands: ``` cargo build --release --package cargo-nexus --bin cargo-nexus cd examples; ../target/release/cargo-nexus nexus prove --impl jolt --bin galeshapley ``` Error: ```...

Summary: Test Plan:

## Analytics Error Visibility Based on RUST_LOG ### With RUST_LOG=debug: - Analytics errors are returned as ProverError::Analytics - Classified at LogLevel::Debug by ErrorClassifier - Displayed in UI because debug level...

# Task Fetching: Original vs New ## Original fetch_prover_tasks (Time-Based) ```rust // OLD APPROACH - Time-driven polling loop { tokio::select! { // Every 100ms: Get ONE new task _ =...