Skip to content

docs: close v1.2.9 erratum boundary - #41

Merged
papasop merged 1 commit into
mainfrom
codex/close-v1.2.9-erratum-boundary
Aug 11, 2026
Merged

docs: close v1.2.9 erratum boundary#41
papasop merged 1 commit into
mainfrom
codex/close-v1.2.9-erratum-boundary

Conversation

@papasop

@papasop papasop commented Aug 11, 2026

Copy link
Copy Markdown
Owner

Complete the repository-level boundary record for the frozen v1.2.9 manuscript clarification.

  • link the official manuscript erratum from the published-paper boundary
  • record the erratum SHA-256 in manuscript provenance
  • state explicitly that the PDF and source archive remain unchanged
  • update repository checksums

This is a documentation-only provenance closure. It does not modify any manuscript artifact, theorem-bearing source, input, protocol, certificate, JSON record, atlas, numerical enclosure, or gate threshold.

No Arb rerun is required, and GLOBAL_FLOW_CLAIMED remains false.

This commit does not create, move, or delete any tag, GitHub Release, or Zenodo record.

Complete the repository-level boundary record for the frozen v1.2.9
manuscript clarification.

- link the official manuscript erratum from the published-paper boundary
- record the erratum SHA-256 in manuscript provenance
- state explicitly that the PDF and source archive remain unchanged
- update repository checksums

This is a documentation-only provenance closure. It does not modify any
manuscript artifact, theorem-bearing source, input, protocol, certificate,
JSON record, atlas, numerical enclosure, or gate threshold.

No Arb rerun is required, and GLOBAL_FLOW_CLAIMED remains false.

This commit does not create, move, or delete any tag, GitHub Release, or
Zenodo record.
@papasop
papasop merged commit 3f4fe4f into main Aug 11, 2026
2 checks passed
@papasop
papasop deleted the codex/close-v1.2.9-erratum-boundary branch August 11, 2026 20:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant