[EmergentMonk]

Summary

Prepares the merged additive GLUBALL Lean formalization for archival release as RSH v4.1.0.

This PR is release/metadata hardening only. It does not alter the GLUBALL theorem statements, the existing RSH-FORMAL-V1 theorem surface, the geometry model, tissue contract, governance contracts, numerical research contracts, or implementation authority hierarchy.

Frozen boundaries

• RSH v4.0.0: 79b8481639fb4187c41035de4e707545db93f59a
• merged RSH-GLUBALL-FORMAL-V1: 124af8283dd69f78031d3a92249fdd7ea4a60508
• GLUBALL v1.0.0: 80941183d14531093117e122da0fc32c13d2464b

Release metadata

• bumps Python package metadata to 4.1.0;
• bumps the Rust workspace and local lockfile package versions to 4.1.0 without changing third-party dependency identities;
• updates CITATION.cff;
• updates .zenodo.json to describe the additive GLUBALL formalization and its explicit nonclaims;
• updates README and FORMALIZATION.md release/theorem-surface status;
• adds RELEASE_NOTES_v4.1.0.md;
• adds release/manifest-v4.1.0.json with exact source pins and tag-target rule.

Release preflight

Adds tests/test_release_v4_1_0.py as a discoverable unittest.TestCase. It fails closed if package/workspace/citation/Zenodo/README versions drift, if the RSH/GLUBALL provenance pins change, or if the preserved/additive theorem surfaces disappear from archival metadata.

The historical tests/test_v4_release_contract.py now freezes the v4.0.0 manifest and scientific/formal boundaries instead of incorrectly requiring all future software releases to stay at 4.0.0.

Codex review fixes

• Legacy v4 version assertion: fixed by keeping the v4.0.0 manifest historically frozen while allowing the current software/archive release to advance to 4.1.0.
• Release-preflight discovery: converted the new checks to unittest.TestCase; all four preflight methods execute under the normal Python 3.10/3.12/3.14 CI matrix.

Both Codex threads are resolved.

Exact-head validation

Validated at:

903b1f2f726217cd0e9344865bec17ea0458a7c1

Green workflows on that exact head:

• CI
• RSH Lean 4 formal verification
• Agent guides and UI boundaries
• Mobile PWA

The CI matrix includes Python 3.10/3.12/3.14, Rust native, compiled WASM, C++/FFI, Pages source, and provenance-boundary checks. The Lean workflow reruns the existing no-sorry / no-project-axiom theorem audit for both advertised theorem surfaces.

Tag rule

After this PR is merged, v4.1.0 should point to the resulting PR #31 merge commit containing the release manifest. Do not move the existing v4.0.0 tag, and do not tag the branch head or the earlier formalization merge commit.

Scientific boundary

RSH-GLUBALL-FORMAL-V1 remains an additive mathematical theorem surface. This release does not claim global thick-tube embeddedness, cross-runtime floating-point identity, browser/GPU/Android correctness outside declared conformance surfaces, or empirical physical/biological/consciousness validation.

[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

Prepares the RSH v4.1.0 GLUBALL additive formalization release by synchronizing versioning and archival metadata, documenting the new theorem surface and its scientific boundaries, adding a machine-readable release manifest, and enforcing these invariants via a dedicated preflight test.

Flow diagram for v4.1.0 release preflight invariants

flowchart TD
  start[[Start CI for v4.1.0]]
  run_test["Run tests/test_release_v4_1_0.py"]
  check_versions["Check Python/Rust versions and README/CITATION/Zenodo metadata"]
  check_pins["Verify RSH/GLUBALL provenance pins match manifest-v4.1.0.json"]
  check_surfaces["Confirm RSH-FORMAL-V1 and RSH-GLUBALL-FORMAL-V1 are present in archival metadata"]
  decision{All invariants satisfied?}
  pass[[Release ready for tagging v4.1.0]]
  fail[[CI fails closed; release blocked]]

  start --> run_test
  run_test --> check_versions
  check_versions --> check_pins
  check_pins --> check_surfaces
  check_surfaces --> decision
  decision -->|yes| pass
  decision -->|no| fail

Loading

File-Level Changes

Change	Details	Files
Update README to describe v4.1.0, additive GLUBALL theorem surface, and integration boundaries.	Bump displayed release from 4.0.0 to 4.1.0. Describe Lean theorem surfaces as preserved RSH-FORMAL-V1 plus additive RSH-GLUBALL-FORMAL-V1. Add a GLUBALL integration section describing pins to GLUBALL v1.0.0 and the additive nature of the theorem surface. Extend high-level feature list to state GLUBALL integration implemented in v4.1.0. Add GLUBALL theorem module path to project layout map.	README.md
Bump Python package metadata to release 4.1.0 and reflect GLUBALL formalization in description and keywords.	Update package version field from 4.0.0 to 4.1.0. Amend project description to mention additive Lean 4 formal verification including RSH-GLUBALL-FORMAL-V1. Extend keywords to include GLUBALL- and torus-curve-related terms.	pyproject.toml
Advance Rust workspace package version to 4.1.0 and keep lockfile local crates in sync without altering dependency graph.	Update workspace.package version from 4.0.0 to 4.1.0 in the Rust workspace manifest. Adjust local crate versions in Cargo.lock so all rsh-* packages are at 4.1.0 while leaving third-party dependency identities unchanged.	Cargo.toml Cargo.lock
Refresh citation and archival metadata to describe the additive GLUBALL theorem surface and version 4.1.0.	Update CITATION.cff version and text to include both preserved and additive theorem surfaces. Update .zenodo.json version, description, and keywords to mention RSH-GLUBALL-FORMAL-V1 and explicitly document nonclaims and provenance pins.	CITATION.cff .zenodo.json
Introduce dedicated release notes for v4.1.0 documenting GLUBALL formalization scope, machine-checked results, and governance boundaries.	Create RELEASE_NOTES_v4.1.0.md summarizing the additive theorem surface, pinned source commits, and Lean/Mathlib versions. Document the specific GLUBALL torus-curve contract and the list of machine-checked properties. Describe audit provenance hardening, preserved contracts and authority boundaries, and explicit scientific nonclaims. Record release and archival metadata expectations and tag rule for v4.1.0. Note authorship and AI contributor role.	RELEASE_NOTES_v4.1.0.md
Add machine-readable release manifest for v4.1.0 capturing frozen boundaries and theorem-surface roles.	Create release/manifest-v4.1.0.json with release version, tag, status, and base RSH v4.0.0 commit. Record the GLUBALL v1.0.0 source commit and merged formalization commit. Encode theorem surfaces as preserved vs additive and list preserved geometry and governance contract identifiers.	release/manifest-v4.1.0.json
Add preflight tests to enforce synchronized release metadata and GLUBALL formalization exposure across project files.	Add tests/test_release_v4_1_0.py to assert that pyproject, Cargo workspace, CITATION, README, and Cargo.lock versions all match 4.1.0. Verify .zenodo.json and CITATION.cff mention RSH-GLUBALL-FORMAL-V1 and that both theorem surfaces are present in citation metadata. Check release/manifest-v4.1.0.json fields for frozen boundary commits, theorem surface roles, and preserved contract identifiers. Ensure README and release notes expose the additive GLUBALL surface, the merge commit, and GLUBALL integration section.	tests/test_release_v4_1_0.py

---

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.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 3ac4addf77

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".