Repository navigation
NOTICE.extra.yml: attribution for the Köthe disproof import - #409
Conversation
Imports tadamcz/koethe at a94a72aec957cb28d76aa30fb97a01d440990d7f (Apache-2.0): a machine-checked counterexample to Krempa's matrix form of Köthe's 1930 conjecture, found autonomously by GPT-6 Astra in Epoch AI's LeanOpenProblems harness and written up in arXiv:2609.07996. The single upstream file is split into modules along its own part boundaries, the broad `import Mathlib` is replaced by minimal imports, the per-part `set_option autoImplicit false` lines are dropped, the pencil field `constant` is renamed `scalar`, and the Mathlib API drift from v4.28.0 to v4.34.0-rc1 is repaired (structure-based `MvPolynomial`, antidiagonal and height lemma renames, `Fintype` sums over structure fields). No statement is weakened; three auxiliary lemmas are generalized from `Fintype` to `Finite` index types. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
…wski / Epoch AI) Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
… import The Köthe project (#408) is Apache-2.0 with a NOTICE file naming Tom Adamczewski / Epoch AI, the vendored Formal Conjectures statement, and the LeanOpenProblems harness. Apache-2.0 §4(d) asks that this attribution be carried along; NOTICE itself is regenerated by the metadata workflow once the project card lands. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
ef982da to
e8c9a5a
Compare
|
Advisory cross-file review against Lean Pool's supervisory rubric. This is not by itself a significance, source-verification, or merge verdict. The PR appears safe to merge because no blocking failure remains. Summary
Reviews (10) · Last reviewed commit: "ci: also run Documentation preflight on ..." |
|
LLM review skipped: PR touches no |
|
Auto-rebase stopped: this PR conflicts with |
Automation disposition: needs-maintainer (reviewed and correct; required checks cannot run on a NOTICE-only diff)Reviewed exact head Why it is not merged. Branch protection requires Decision for the maintainer (one of): (a) admin-merge this PR; (b) add |
Branch protection requires Build project and Documentation preflight, but neither workflow triggered on attribution-only diffs, so a NOTICE.extra.yml PR could never be merged without an admin bypass. Add the file to both pull_request path filters; the push filters are unchanged. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
|
Maintainer decision received: merge. An admin bypass is not something this automation performs, so the other route from the 2026-09-11 02:25 UTC comment was taken instead: commit |
|
LLM review skipped: PR touches no |
…anges PR #412 changes only lean_action_ci.yml and scripts/ci/plan-build-shards.py, so docs.yml never triggered and the required Documentation preflight check could not be created. List those paths as well. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
|
LLM review skipped: PR touches no |
Reproduces the upstream NOTICE of tadamcz/erdos548 (Apache License, Version 2.0, Section 4(d)) under LeanPool/Erdos548 and regenerates NOTICE, following the Köthe precedent in #409. Co-authored-by: Vilin97 automation <automation@lean-pool.local> Co-authored-by: Claude Fable 5.1 <noreply@anthropic.com>
Non-content companion to #408, stacked on that branch (base:
claude/daily-import-koethe-2026-09-10) and kept as a draft until #408 merges.Adds the
Koethe:attribution block toNOTICE.extra.yml, reproducing the upstream repository's NOTICE (Apache License 2.0, §4(d)): copyright Tom Adamczewski / Epoch AI, the vendored Formal Conjectures statement (© The Formal Conjectures Authors, Apache-2.0), and the LeanOpenProblems harness (MIT), and regeneratesNOTICEwithpython -m lean_pool.notice --repo ..(13 notice tests pass on this branch).Why stacked: the NOTICE generator (and
tests/test_notice.py) rejects notes for projects that are not registered inLeanPool/projects.yml, so this entry cannot land onmainbefore the project card does, and the content-PR guard forbids bundling it with #408. Once #408 is squash-merged, retarget this PR tomain, refresh the branch, rerun the generator (the metadata workflow will have regeneratedNOTICEwithout the attribution in between), and merge.🤖 Generated with Claude Code