You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Aug 12, 2026. It is now read-only.
- validate complete reference packages before publishing generated artifacts
- bound initializer optimization commands and report actionable failures
- add pinned Markdown validation to local and CI workflows
- reconcile archival guidance, API contracts, and successor issue routing
Copy file name to clipboardExpand all lines: .github/CODE_OF_CONDUCT.md
+19-7Lines changed: 19 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,7 +2,9 @@
2
2
3
3
## Our Pledge
4
4
5
-
In the interest of fostering an open and welcoming environment, we as contributors and maintainers pledge to making participation in our project and our community a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, gender identity and expression, level of experience, nationality, personal appearance, race, religion, or sexual identity and orientation.
5
+
In the interest of fostering an open and welcoming environment, we as contributors and maintainers pledge to make participation in our project and
6
+
our community a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, gender identity and expression, level
7
+
of experience, nationality, personal appearance, race, religion, or sexual identity and orientation.
6
8
7
9
## Our Standards
8
10
@@ -24,23 +26,33 @@ Examples of unacceptable behavior by participants include:
24
26
25
27
## Our Responsibilities
26
28
27
-
Project maintainers are responsible for clarifying the standards of acceptable behavior and are expected to take appropriate and fair corrective action in response to any instances of unacceptable behavior.
29
+
Project maintainers are responsible for clarifying the standards of acceptable behavior and are expected to take appropriate and fair corrective
30
+
action in response to any instances of unacceptable behavior.
28
31
29
-
Project maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, or to ban temporarily or permanently any contributor for other behaviors that they deem inappropriate, threatening, offensive, or harmful.
32
+
Project maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions
33
+
that are not aligned to this Code of Conduct, or to ban temporarily or permanently any contributor for other behaviors that they deem inappropriate,
34
+
threatening, offensive, or harmful.
30
35
31
36
## Scope
32
37
33
-
This Code of Conduct applies both within project spaces and in public spaces when an individual is representing the project or its community. Examples of representing a project or community include using an official project e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event. Representation of a project may be further defined and clarified by project maintainers.
38
+
This Code of Conduct applies both within project spaces and in public spaces when an individual is representing the project or its community.
39
+
Examples include using an official project email address, posting via an official social media account, or acting as an appointed representative at
40
+
an online or offline event. Project maintainers may further define and clarify representation of the project or community.
34
41
35
42
## Enforcement
36
43
37
-
Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team at adam@adamgetchell.org. The project team will review and investigate all complaints, and will respond in a way that it deems appropriate to the circumstances. The project team is obligated to maintain confidentiality with regard to the reporter of an incident. Further details of specific enforcement policies may be posted separately.
44
+
Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team at
45
+
[adam@adamgetchell.org](mailto:adam@adamgetchell.org). The project team will review and investigate all complaints and respond as appropriate to the
46
+
circumstances. The project team is obligated to maintain confidentiality about the reporter of an incident. Further details of specific enforcement
47
+
policies may be posted separately.
38
48
39
-
Project maintainers who do not follow or enforce the Code of Conduct in good faith may face temporary or permanent repercussions as determined by other members of the project's leadership.
49
+
Project maintainers who do not follow or enforce the Code of Conduct in good faith may face temporary or permanent repercussions as determined by
50
+
other members of the project's leadership.
40
51
41
52
## Attribution
42
53
43
-
This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4, available at [http://contributor-covenant.org/version/1/4][version]
54
+
This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4, available at
Copy file name to clipboardExpand all lines: CHANGELOG.md
+13-1Lines changed: 13 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -14,7 +14,7 @@ CDT++ 1.0.0 is the final planned feature release of the C++23 spherical 2+1-dime
14
14
-**Compatibility:** The supported source boundary is C++23 with the published GCC, Clang, AppleClang, and MSVC matrix. The project does not promise a stable binary ABI or package-registry distribution.
15
15
-**Scientific corrections:** The release completes and independently validates all five 2+1D moves, Metropolis-Hastings proposal ratios and atomic transitions, exact-predicate geometry boundaries, run-owned RNG streams, and causal persistence metadata.
16
16
-**Supported surface:** The default build is headless; CGAL/oneTBB bulk Delaunay operations and the macOS Qt viewer are explicit opt-ins. Historical toroidal and higher-dimensional prototypes are excluded from the supported API.
17
-
-**Limitations:** Seeds replay stochastic inputs, not necessarily fresh cospherical CGAL topology. Checkpoints are validated snapshots rather than resumable simulations, and parallelism does not extend to Pachner moves or concurrent manifold access.
17
+
-**Limitations:** Seeds replay stochastic inputs, not necessarily fresh cospherical CGAL topology. Resumable checkpoints continue the identical Markov chain only on the recorded producer toolchain; they are restart artifacts rather than portable interchange files. Parallelism does not extend to Pachner moves or concurrent manifold access.
18
18
-**Migration:** Active development and new work move to [causal-triangulations](https://github.com/acgetchell/causal-triangulations). After the v1.0.0 GitHub and Zenodo handoff, CDT++ enters a maintenance-only stabilization window and becomes read-only only when the owner completes the archival gate.
19
19
20
20
### Added
@@ -27,6 +27,8 @@ CDT++ 1.0.0 is the final planned feature release of the C++23 spherical 2+1-dime
Copy file name to clipboardExpand all lines: cliff.toml
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -23,7 +23,7 @@ body = """
23
23
- **Compatibility:** The supported source boundary is C++23 with the published GCC, Clang, AppleClang, and MSVC matrix. The project does not promise a stable binary ABI or package-registry distribution.
24
24
- **Scientific corrections:** The release completes and independently validates all five 2+1D moves, Metropolis-Hastings proposal ratios and atomic transitions, exact-predicate geometry boundaries, run-owned RNG streams, and causal persistence metadata.
25
25
- **Supported surface:** The default build is headless; CGAL/oneTBB bulk Delaunay operations and the macOS Qt viewer are explicit opt-ins. Historical toroidal and higher-dimensional prototypes are excluded from the supported API.
26
-
- **Limitations:** Seeds replay stochastic inputs, not necessarily fresh cospherical CGAL topology. Checkpoints are validated snapshots rather than resumable simulations, and parallelism does not extend to Pachner moves or concurrent manifold access.
26
+
- **Limitations:** Seeds replay stochastic inputs, not necessarily fresh cospherical CGAL topology. Resumable checkpoints continue the identical Markov chain only on the recorded producer toolchain; they are restart artifacts rather than portable interchange files. Parallelism does not extend to Pachner moves or concurrent manifold access.
27
27
- **Migration:** Active development and new work move to [causal-triangulations](https://github.com/acgetchell/causal-triangulations). After the v1.0.0 GitHub and Zenodo handoff, CDT++ enters a maintenance-only stabilization window and becomes read-only only when the owner completes the archival gate.
28
28
{% endif %}
29
29
{% for group, commits in commits | group_by(attribute="group") %}
0 commit comments