Registry: maintain cross-venue submission readiness contracts

[edithatogo]

Parent roadmap: #296

Conductor track: research_software_registry_readiness_20260721.

Objective

Maintain the fail-closed contract in specs/submission-readiness/targets.json for every current and potential registry, archive, identifier, journal, community review, and sustainability affiliation.

Ordered repository-controlled closure plan

1. Keep official criteria URLs, review dates, evidence paths, action authority, and acceptance evidence current for all 22 targets. Date-stamped refresh evidence and validator coverage recorded on 2026-07-27.
2. Reconcile specialised arXiv, JOSS, language-registry, release, and binding evidence into the cross-venue contract after each relevant release or evidence refresh.
3. Verify that every required target belongs to a GitHub-backed execution lane; the local validator and CI gate enforce this.
4. Close Python community-review evidence through Community review: prepare pyOpenSci readiness #616.
5. Close R installation/API/statistical-software evidence through Community review: mature voiageR for possible rOpenSci review #615.
6. Close locally testable HPC package-recipe evidence through child issue Packaging: prepare reproducible HPC recipes for future Spack and EasyBuild review #622.
7. Record a non-duplication decision for JSS, NumFOCUS, and Zenodo through Publication strategy: assess distinct post-JOSS community routes #617 before creating venue-specific material.

Explicit boundaries

The paper lane (#299, #312, #471) maintains repository artefacts only. Author attestations, category/licence choices, human research-use evidence, uploads, inquiries, submissions, review, curation, acceptance, publication, and indexing are not repository-completion tasks. Conda-forge, CRAN, Yggdrasil, Julia General, RRID, and all other external outcomes remain separately evidenced external gates.

This issue does not authorize an inquiry, submission, upload, registration, or affiliation application. External action requires a separate explicit maintainer or author decision.

[edithatogo]

Cross-venue readiness reconciliation after merged HPC delivery:

• Child Packaging: prepare reproducible HPC recipes for future Spack and EasyBuild review #622 is complete and closed via PR feat(hpc): add reproducible source-native packaging recipes #887 (1405f1cf9e98885f24f8e6b923493136ce62c43b); Conductor and cross-reference projections are synchronized by merged PR docs(conductor): record merged HPC packaging handoff #987 (b9db7aca71e2b3317bdaa79187a50ddd36893279).
• Remaining Registry: maintain cross-venue submission readiness contracts #614 items are the specialised evidence refreshes and external/community decisions listed in the issue (Community review: mature voiageR for possible rOpenSci review #615, Community review: prepare pyOpenSci readiness #616, Publication strategy: assess distinct post-JOSS community routes #617 and external registry/review outcomes). No submission, inquiry, or acceptance is inferred.

[edithatogo]

Post-release v2.1.0 registry reconciliation is repository-complete.

• conda-forge staged-recipes PR #34308 is open at exact candidate head 331e3d9b509c7938ed298b79d2c37153f984f4b1; linter, aggregate Azure build 1571876, and Linux/macOS/Windows jobs are green.
• Yggdrasil PR #14292 is open at exact candidate head db38b5200cc4ed741c5cfc682a8465395f687b41; Buildkite 31960 is green across seven declared platforms.
• Voiage PR Bind v2.1.0 external registry candidate evidence #998 merged the immutable candidate receipt and cross-venue contract update after 32 successful exact-head checks, three governed skips, one neutral observation, and no failures or pending checks.

This completes repository-owned candidate preparation/reconciliation only. External maintainer merge, feedstock/JLL generation, downstream indexing, and registry/publication acceptance remain open external gates; M22-M31 remain experimental.

[edithatogo]

Cross-venue registry contract update (exact evidence only):

• The maximum-coverage work is tracked in Voiage PR chore: maximize Yggdrasil platform coverage #999 and Conductor track yggdrasil_maximum_platform_coverage_20260821.
• Voiage: new package at 2.1.0 JuliaPackaging/Yggdrasil#14292 is open at exact head 2528e2efb90e4197924d45c98873ca5cdb1a9d42.
• Buildkite 31972 passed all 15 included targets after three narrow, evidence-backed exclusions.
• Product integrity is verified for all 15 archives; runtime/ABI evidence is intentionally limited to the two locally executable macOS artifacts.

The append-only registry handoff will retain Yggdrasil merge, JLL generation, clean-depot JLL smoke, Julia General acceptance, and indexing as separate external gates. No publication or registry acceptance is inferred, and #614 remains open.

[edithatogo]

Maximum-coverage reconciliation is complete in merged PR #999: exact head 4bd6cfb739c9a9e786598d43eead3989c0eb0697, 36 terminal-allowed hosted results with no failure or pending state, squash merge 58550d0674fad1fbecc2a61d82122c3a3ebccf2c. Buildkite 31972 remains the exact 15-of-15 external recipe matrix. This receipt does not claim Yggdrasil merge, JLL generation, clean-depot JLL execution, Julia General acceptance, or indexing.