Point the arXiv kit at v1.2.0, and make the release gate say what it does

[Silentpartnercoding]

Two things: your auto-publish decision recorded, and the arXiv kit brought up to date.

Owner decision recorded

Auto-publication stays on. Creating a GitHub release here publishes a Zenodo DOI immediately and irreversibly. The gate is therefore the release itself, and there is no later one.

The documentation is corrected to match the mechanism, rather than the mechanism changed to match the documentation. The consequence is stated where a reader will hit it:

Every check must pass before gh release create, because nothing after it can be undone.

arXiv kit updated

It still pointed at the v1.1.0 PDF and the v1.1.0 version DOI. Now: the v1.2.0 PDF, the concept DOI in the endorsement-request template so the link stays valid across versions, and the abstract synced with canonical metadata.

Endorsement, checked against the source

From info.arxiv.org/help/endorsement.html, not from memory:

• endorsement is per endorsement domain, not per paper;
• the author sends an endorser a six-character code arXiv issues;
• an eligible endorser must have submitted in that domain between three months and five years ago, and hold a positive endorsement themselves;
• it is explicitly not peer review — the endorser checks subject-area fit, not correctness;
• one positive endorsement suffices.

Flagged as unverified: arXiv auto-endorses submitters at recognised academic institutions, so a personal-domain address likely triggers the endorsement requirement rather than bypassing it. Recorded as a planning risk, not a fact.

paper-check passes; 426 passed, 8 skipped.

🤖 Generated with Claude Code