Spike: what if app circuit outputs different #read-requests vs what the RPC client gets from the simulator?

[dbanks12]

Does it matter if i use readRequests.length or readRequestsMembershipWitnesses.length in kernel prover?
Do I need to assert that they are the same?
Do I need separate length constants for app circuit and kernel? (smaller length for app circuit outputs, larger length for kernel which accumulates read requests across iterations)

In private_execution.ts's getNotes2, if preimages length is > rrcIndices length, we are either relying on the app circuit to remove fake preimages, or on the kernel to handle the length diff.

[dbanks12]

This is still a conversation we should dig into.... It has changed a bit now, but how can we be certain that app circuit read requests align perfectly with readRequstPartialWitnesses constructed in ClientTxExecutionContext?