refactor(transcript)!: write Jolt proofs as spongefish NARG argument strings

.github/workflows/fs-soundness.yml

@@ -58,13 +58,12 @@ jobs:
           cargo nextest run
           -p jolt-verifier
           --test fs_obligations
-          --features fs-audit
           --cargo-quiet
       - name: Probe Akita ZK support
         shell: bash
         run: |
           set -euo pipefail
-          if cargo check -p jolt-verifier --lib --features akita,fs-audit,zk 2>akita-zk.log; then
+          if cargo check -p jolt-verifier --lib --features akita,zk 2>akita-zk.log; then
             echo "Akita+ZK now builds; add it to the Fiat-Shamir fixture matrix."
             exit 1
           fi
@@ -78,11 +77,11 @@ jobs:
       matrix:
         include:
           - instance: dory-clear
-            features: fs-audit,prover-fixtures
+            features: logging,prover-fixtures
           - instance: dory-zk
-            features: fs-audit,prover-fixtures,zk
+            features: logging,prover-fixtures,zk
           - instance: akita-clear
-            features: akita,fs-audit,prover-fixtures
+            features: akita,logging,prover-fixtures
     steps:
       - uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1
       - uses: actions-rust-lang/setup-rust-toolchain@ecabd13d1c56bd1345c230e542e9144811ad706f # v2

.github/workflows/rust.yml

@@ -73,6 +73,8 @@ jobs:
         run: scripts/check-shared-field-identity.sh
       - name: Keep Metal out of the verifier
         run: scripts/check-metal-isolation.sh
+      - name: Keep spongefish's sponge state private (no yolocrypto)
+        run: scripts/check-no-yolocrypto.sh
       - name: Check no backend
         run: cargo check -p jolt-field --no-default-features
       - name: Check BN254 backend
@@ -104,18 +106,19 @@ jobs:
       # jolt-verifier's prover-fixtures feature gates live prover artifact
       # generation for verifier tests. It is not enabled by the workspace-wide
       # invocations above, so build it explicitly in both modes.
-      - name: cargo clippy -p jolt-verifier --features prover-fixtures
-        run: cargo clippy -p jolt-verifier --all-targets --features prover-fixtures
-      - name: cargo clippy -p jolt-verifier --features prover-fixtures,zk
-        run: cargo clippy -p jolt-verifier --all-targets --features prover-fixtures,zk
+      - name: cargo clippy -p jolt-verifier --features prover-fixtures,logging
+        run: cargo clippy -p jolt-verifier --all-targets --features prover-fixtures,logging
+      - name: cargo clippy -p jolt-verifier --features prover-fixtures,zk,logging
+        run: cargo clippy -p jolt-verifier --all-targets --features prover-fixtures,zk,logging
       # The akita feature selects the lattice (Akita) PIOP; it is not enabled
       # by the workspace-wide invocations above.
       - name: cargo clippy -p jolt-verifier --features akita
         run: cargo clippy -p jolt-verifier --all-targets --features akita
       # The akita fixture-driven tamper suite compiles under akita,prover-fixtures
-      # (the real Akita prover generates its fixtures). Lint it explicitly.
-      - name: cargo clippy -p jolt-verifier --features akita,prover-fixtures
-        run: cargo clippy -p jolt-verifier --all-targets --features akita,prover-fixtures
+      # (the real Akita prover generates its fixtures) with `logging`, whose
+      # transcript event log locates each rejection. Lint it explicitly.
+      - name: cargo clippy -p jolt-verifier --features akita,prover-fixtures,logging
+        run: cargo clippy -p jolt-verifier --all-targets --features akita,prover-fixtures,logging
       # The modular prover's Akita path: lint alone and with
       # prover-fixtures so the acceptance suites keep compiling.
       - name: cargo clippy -p jolt-prover --features akita
@@ -180,14 +183,14 @@ jobs:
         run: cargo clippy -p jolt-prover --all-targets --features prover-fixtures,field-inline
       - name: cargo clippy -p jolt-prover --features prover-fixtures,field-inline,zk
         run: cargo clippy -p jolt-prover --all-targets --features prover-fixtures,field-inline,zk
-      - name: cargo clippy -p jolt-verifier --features prover-fixtures,field-inline
-        run: cargo clippy -p jolt-verifier --all-targets --features prover-fixtures,field-inline
+      - name: cargo clippy -p jolt-verifier --features prover-fixtures,field-inline,logging
+        run: cargo clippy -p jolt-verifier --all-targets --features prover-fixtures,field-inline,logging
       # The Akita field-inline combination: the full-width increment group rides the
       # dense-group heterogeneous batch beside advice.
       - name: cargo clippy -p jolt-verifier --features field-inline,akita
         run: cargo clippy -p jolt-verifier --all-targets --features field-inline,akita
-      - name: cargo clippy -p jolt-verifier --features prover-fixtures,field-inline,akita
-        run: cargo clippy -p jolt-verifier --all-targets --features prover-fixtures,field-inline,akita
+      - name: cargo clippy -p jolt-verifier --features prover-fixtures,field-inline,akita,logging
+        run: cargo clippy -p jolt-verifier --all-targets --features prover-fixtures,field-inline,akita,logging
       - name: cargo clippy -p jolt-prover --features prover-fixtures,field-inline,akita
         run: cargo clippy -p jolt-prover --all-targets --features prover-fixtures,field-inline,akita
       - name: cargo clippy -p jolt-sdk --features host,field-inline
@@ -383,7 +386,7 @@ jobs:
       # step existed they were clippy-only, so the golden BlindFold shape pins
       # in completeness/zk.rs could go stale without any lane noticing.
       - name: Run jolt-verifier fixtures with zk feature
-        run: cargo nextest run --cargo-profile ci -p jolt-verifier --features prover-fixtures,zk --test-threads 1 --cargo-quiet
+        run: cargo nextest run --cargo-profile ci -p jolt-verifier --features prover-fixtures,zk,logging --test-threads 1 --cargo-quiet
       # The jolt-kernels unit suite in its zk flavor.
       - name: Run jolt-kernels tests with zk feature
         run: cargo nextest run --cargo-profile ci -p jolt-kernels --features zk
@@ -536,7 +539,7 @@ jobs:
         run: >-
           cargo nextest run --cargo-profile ci -p jolt-akita --features field-inline
       - name: Run jolt-verifier with prover-fixtures,field-inline,akita
-        run: cargo nextest run --cargo-profile ci -p jolt-verifier --features prover-fixtures,field-inline,akita --test-threads 1
+        run: cargo nextest run --cargo-profile ci -p jolt-verifier --features prover-fixtures,field-inline,akita,logging --test-threads 1
 
   test-verifier-field-inline-fixtures:
     runs-on: ubuntu-latest
@@ -571,11 +574,11 @@ jobs:
         with:
           tool: nextest
       # The fixture-driven field-inline suites: valid-fixture acceptance
-      # (completeness/field_inline.rs) and the typed field-inline clear-claim tamper
-      # sweep (tampering/field_inline.rs), backed by fixtures the modular
-      # prover generates at test time.
+      # (completeness/field_inline.rs) and the argument-string tamper sweep
+      # (soundness/dory.rs, `logging` for its event log), backed by fixtures
+      # the modular prover generates at test time.
       - name: Run jolt-verifier field-inline fixture and tamper suites
-        run: cargo nextest run --cargo-profile ci -p jolt-verifier --features prover-fixtures,field-inline --test-threads 1
+        run: cargo nextest run --cargo-profile ci -p jolt-verifier --features prover-fixtures,field-inline,logging --test-threads 1
 
   test-verifier-akita-fixtures:
     runs-on: ubuntu-latest
@@ -610,11 +613,12 @@ jobs:
         with:
           tool: nextest
       # The fixture-driven akita suites: valid-fixture acceptance
-      # (completeness/akita.rs) and the typed clear-claim, commitment-byte,
-      # proof-shape, and presence tamper sweeps (tampering/akita.rs), backed
-      # by fixtures the real Akita prover generates at test time.
+      # (completeness/akita.rs) and the argument-string message, structural,
+      # and statement tamper sweeps (soundness/akita.rs, `logging` for their
+      # event log), backed by fixtures the real Akita prover generates at
+      # test time.
       - name: Run jolt-verifier akita fixture and tamper suites
-        run: cargo nextest run --cargo-profile ci -p jolt-verifier --features akita,prover-fixtures --test-threads 1
+        run: cargo nextest run --cargo-profile ci -p jolt-verifier --features akita,prover-fixtures,logging --test-threads 1
 
   typos:
     runs-on: ubuntu-latest
@@ -850,7 +854,7 @@ jobs:
         with:
           tool: nextest
       - name: Run verifier fixtures
-        run: cargo nextest run --cargo-profile ci -p jolt-verifier --features prover-fixtures --test-threads 1 --cargo-quiet
+        run: cargo nextest run --cargo-profile ci -p jolt-verifier --features prover-fixtures,logging --test-threads 1 --cargo-quiet
 
   test-inlines:
     name: Test inlines

CLAUDE.md

@@ -122,12 +122,14 @@ The SDK's `host` feature enables native build/prove APIs. On `jolt-prover`, `aki
 ### Key Type Parameters
 
 The staged prover and verifier are generic over the PCS, vector commitment,
-and transcript. Dory uses `Fr`; the `akita` build uses `AkitaField`.
+and the transcript's sponge. Dory uses `Fr`; the `akita` build uses
+`AkitaField`. Proofs are argument strings written through
+`jolt_transcript::ProverTranscript<H>` and read through `VerifierTranscript<'_, H>`.
 
 ```
 PCS: CommitmentScheme
 VC: VectorCommitment<Field = PCS::Field>
-T: Transcript<Challenge = PCS::Field>
+H: Sponge
 ```
 
 ### Prover Pipeline