feat(agents): persist unresolved proof obligations

[FluffyAIcode]

Summary

• add a private persistent Proof Obligation Ledger with stable IDs and parent relationships
• inject the ledger through dedicated Generator and Critic protocol sections, never Terminal input
• require one ISSUE_RESPONSE per pending ID from Generator
• require one structured ISSUE_VERDICT per pending ID from Critic
• keep missing, malformed, weakly evidenced, or lemma-dependent verdicts UNRESOLVED
• close only structurally valid PROVED or DISPROVED verdicts
• carry unresolved obligations automatically into every subsequent auto-loop turn
• log ledger load, Generator coverage, Critic verdicts, carried/closed events, and versioned checkpoints
• expose ledger ID/version/coverage/unresolved counts in benchmark metadata

Seed obligations

The private runtime ledger is seeded with RH-C1..RH-C5 covering logarithmic-derivative circularity, Dirichlet-polynomial zero convergence, GUE non-equivalence, BM assumptions, and exact off-line-zero exclusion.

Non-interruption

The currently running inference remains untouched. Deployment handoff occurs only after its complete checkpoint and before the next run starts.

Tests

• private atomic ledger persistence
• Generator issue coverage
• valid closure and unresolved carry-forward
• rejection of weak or missing closure evidence
• existing state-machine, checkpoint, and inbox behavior
• targeted suite — 23 passed
• full platform-neutral suite — 884 passed, 1 skipped
• Python compile and diff checks pass

Made with Cursor

[cursor]

Bugbot is not enabled for your account, so this pull request was not reviewed.

Enable Bugbot in the Cursor dashboard to get automatic reviews on future PRs.