Commitment and Commitment State for Linear Code PCS are private

[beekayg15]

Summary of Bug

The data structures of poly-commit/src/linear_codes have restricted visibility. Specifically, the LinCodePCCommitment and LinCodePCCommitmentState data structures required to store the commitments are currently private.

Version

0.5.0

Steps to Reproduce

https://github.com/arkworks-rs/poly-commit/blob/a05ec99d0d3e46c8ba0d6d3592980777bc2847e8/poly-commit/src/linear_codes/mod.rs#L37C9-L37C24

We could just change it to

pub use data_structures::*;

if not to

pub use data_structures::{
    BrakedownPCParams, LigeroPCParams, 
    LinCodePCProof, LinCodePCCommitment,
    LinCodePCCommitmentState
};

[klize]

here suffers from the same thing.
those need to be public

[peter941221]

The linear_codes module already has the right starting point for an in-repo baseline: Brakedown, Ligero, and existing multilinear benches. What is still missing is a shared experimental surface.

1. Scope

1.1 Expose the minimum commitment/state surface needed for controlled linear-code PCS experiments.

1.2 Add one shared benchmark harness for MultilinearBrakedown and MultilinearLigero.

2. Why this is useful

2.1 It gives the repository one apples-to-apples baseline across the current linear-code PCS implementations.

2.2 It makes follow-up work in the same part of the codebase easier to evaluate, discuss, and extend.

3. Benchmark shape

3.1 Report commit time, open time, verify time, proof size, and commitment size.

3.2 Use one shared workload matrix across number of variables, encoded size, security parameter, code-rate-related parameters, and query count.

If this direction makes sense, I can prepare a scoped PR around the minimal interface exposure and the shared Brakedown/Ligero benchmark path.