[EmergentMonk]

Summary

Pins the reserved Zenodo version DOI 10.5281/zenodo.21959297 into the already-merged RSH v4.1.0 archival metadata before the final v4.1.0 tag is created.

This is a post-release-prep archival identity patch only. It does not alter theorem statements, geometry, governance, numerical contracts, runtime behavior, or implementation authority.

Provenance chain

• RSH v4.0.0: 79b8481639fb4187c41035de4e707545db93f59a
• merged RSH-GLUBALL-FORMAL-V1: 124af8283dd69f78031d3a92249fdd7ea4a60508
• v4.1.0 release-prep merge (RSH v4.1.0 — GLUBALL formalization release prep #31): f6fc36fe0dd19af6bc6247d4e9f4a19f2500573e
• GLUBALL v1.0.0: 80941183d14531093117e122da0fc32c13d2464b
• reserved Zenodo version DOI: 10.5281/zenodo.21959297

Changes

• adds the DOI to CITATION.cff;
• binds the DOI and RSH v4.1.0 — GLUBALL formalization release prep #31 merge commit in release/manifest-v4.1.0.json;
• records the DOI and release-prep merge in RELEASE_NOTES_v4.1.0.md;
• extends tests/test_release_v4_1_0.py so CI fails if the DOI or archival pins drift.

.zenodo.json is intentionally left as deposition metadata rather than adding the record's own DOI as a self-referential related identifier.

Tag rule

v4.1.0 does not exist yet. After this PR is reviewed, green, and merged, the tag should point to the resulting merge commit containing the DOI pin. Do not tag the #31 merge commit or this branch head.

Scientific boundary

The DOI is archival identity metadata only. It changes no theorem proposition and creates no new empirical or scientific claim.

Summary by Sourcery

Pin the reserved Zenodo version DOI into the RSH v4.1.0 archival metadata and ensure the release tag references the merge commit containing this DOI binding.

Enhancements:

• Bind the reserved Zenodo version DOI and release-prep merge commit in the machine-readable v4.1.0 release manifest.
• Record the Zenodo version DOI and release-prep merge commit in the v4.1.0 release notes and citation metadata as archival identity information.

Documentation:

• Update v4.1.0 release notes to document the reserved Zenodo version DOI, its archival role, and the tag resolution rule.

Tests:

• Extend v4.1.0 release tests to assert the presence and consistency of the Zenodo DOI and release-prep merge pins across citation, manifest, and release notes.

[sourcery-ai]

Sorry @EmergentMonk, you have reached your weekly rate limit of 500000 diff characters.

Please try again later or upgrade to continue using Sourcery

[sourcery-ai]

Reviewer's Guide

Pins the reserved Zenodo version DOI into the v4.1.0 archival metadata and release documentation, and extends the release test to enforce the DOI and provenance metadata as frozen boundaries before tagging.

Flow diagram for v4.1.0 DOI pin and archival metadata bindings

flowchart LR
    Zenodo_record[Zenodo_record 10.5281/zenodo.21959297]
    Commit_f6fc36fe0dd19af6bc6247d4e9f4a19f2500573e[release_prep_merge_commit]
    Release_manifest_v4_1_0[release/manifest-v4.1.0.json]
    CITATION_cff[CITATION.cff]
    Release_notes_v4_1_0[RELEASE_NOTES_v4.1.0.md]
    Test_release_v4_1_0[tests/test_release_v4_1_0.py]
    Tag_v4_1_0[v4.1.0_git_tag]

    Zenodo_record --> Release_manifest_v4_1_0
    Zenodo_record --> CITATION_cff
    Zenodo_record --> Release_notes_v4_1_0

    Commit_f6fc36fe0dd19af6bc6247d4e9f4a19f2500573e --> Release_manifest_v4_1_0

    Release_manifest_v4_1_0 --> Tag_v4_1_0

    Test_release_v4_1_0 --> Release_manifest_v4_1_0
    Test_release_v4_1_0 --> CITATION_cff
    Test_release_v4_1_0 --> Release_notes_v4_1_0
    Test_release_v4_1_0 --> Zenodo_record

Loading

File-Level Changes

Change	Details	Files
Extend the v4.1.0 release test to validate the pinned Zenodo DOI and release-prep merge commit in archival metadata and notes.	Add constants for the release-prep merge commit and Zenodo version DOI to the release test module. Assert that CITATION.cff contains the Zenodo DOI string. Assert that the release manifest includes the release-prep merge commit, Zenodo DOI fields, and a flag indicating the DOI was reserved before tagging. Assert that the archive metadata section of the manifest repeats the Zenodo DOI. Assert that the release notes include the release-prep merge commit and Zenodo DOI, while README continues to expose the GLUBALL integration surface.	tests/test_release_v4_1_0.py
Update release notes to record the release-prep merge commit and Zenodo version DOI, and clarify the tag rule in terms of the DOI-pinned merge.	Add bullets documenting the v4.1.0 release-prep merge commit and Zenodo version DOI in the pinned boundaries list. Introduce a dedicated section that prints the reserved Zenodo DOI and explains its archival identity role. Refine the v4.1.0 tag rule to require that the tag resolve to the merge commit containing both the release manifest and DOI pin after CI and theorem audit are green.	RELEASE_NOTES_v4.1.0.md
Bind the reserved Zenodo version DOI into citation and machine-readable release manifest metadata for v4.1.0.	Add the Zenodo version DOI to the citation metadata in CITATION.cff. Add fields in the release manifest to record the release-prep merge commit, bind the Zenodo DOI in both release and archive_metadata sections, and mark that the DOI was reserved before the tag is created.	CITATION.cff release/manifest-v4.1.0.json

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.