LeanEval integration: intake, catalog and package-policy questions

Updated 11 September 2026. This issue tracks possible downstream adoption, not a dependency of the FC toolkit release.

LeanEval's [current completion plan](https://github.com/leanprover/lean-eval/blob/6b4b87b672f5301f24983a12fda65dac608453ce/docs/overhaul-completion-plan.md#41-formal-conjectures-and-disproofs) excludes an FC importer, FC100 integration, synchronization and an FC-owned content lane. Its open-problems group is provider-neutral and may be empty. The earlier arrangements in lean-eval#536 are design history where superseded by that amendment.

| Question for LeanEval maintainers | FC can provide |
| --- | --- |
| Whether and how an FC declaration enters the catalog | Exact repository/module/declaration/revision and source references |
| Accepted toolchain and dependency policy | Pinned native workspaces from #5337 and the shared generator |
| Supported submission contract and allowed assumptions | Qualified verification records from #5387, with typed outcomes |
| Retention, licensing and public/private intake rules | Explicit evidence exports and references; no automatic catalog submission |

A successful FC export or Comparator result does not establish LeanEval catalog admission. FC will propose downstream changes here only after maintainers confirm a concrete intake contract. No duplicate catalog or submission server is planned.

**FC implementation:** #5337 replaces the older #4951 exporter. Generator #7 owns the shared structured contract; Comparator #87 owns typed outcomes. #4394 is the FC roadmap.

**Historical audit:** the earlier link survey used FC `9f5ee77` and partially built 204 declarations from 20 of 143 checkouts. Those observations retain their original scope; they do not establish current corpus-wide cleanliness or an accepted downstream policy.

Remain open for those policy decisions. No current LeanEval implementation or activation is authorized by this issue alone.

Start by reviewing the linked LeanEval completion plan and the referenced FC issues #5337 and #5387 to understand the proposed exports and verification records. The issue is done only when LeanEval maintainers confirm a concrete intake, toolchain, submission, and retention contract; it authorizes no implementation on its own.

Written by the indexing model from the issue text.