ci: bump the gasp conformance pin to the lenient checker

[yuanhao]

The pin sat at 08a60a2 — before today's fix — so this job was still certifying yoagent against the 0.4-era strict fold, where one dangling op aborts check 2 and the run reports a failure without saying which op, or how many others would have folded fine.

795bb93 folds leniently (gasp#3) and names what it skipped on the certificate. It also drops the build.rs (gasp#4) whose Cargo.lock parsing printed unknown for exactly the kind of build CI does.

Verified before bumping, not after

Ran this job's own sequence locally against the new SHA — emit, clone, check:

conformance-check 0.1.0 — folding with yoagent-state 0.5.2
[PASS] check 1 — envelope round-trip
[PASS] check 2 — replay
       note: no snapshots/ — skipped seed check
[PASS] check 3 — vocabulary
[PASS] check 4 — append-only in git
[PASS] check 5 — causation integrity
[PASS] check 6 — restore
[PASS] check 7 — domain↔ops consistency
conformant: all checks passed

7/7 with no skip notes — yoagent's emitted repo has no dangling ops. The lenient fold changes what happens when one appears; it does not lower the bar for a clean store. (The real yoyo-gasp store, 8.8K events, does have one, and now reports it as a note rather than a hard failure.)

The comment now records what makes a bump safe, since the old one said only "pin".

🤖 Generated with Claude Code