Approve CDT++ v1.0.0 release readiness

[acgetchell]

Summary

Approve CDT++ v1.0.0 as ready for the final publish-and-archive operation.

This is the release-readiness umbrella. It starts after #96 and must close before #97. Issue #97 alone owns creating the final tag and release, verifying the DOI and artifacts, closing the last tracker, and archiving the repository.

Current release contract

• Preserve the supported 2+1-dimensional spherical CDT implementation as an independent C++23 reference for causal-triangulations.
• Preserve the complete supported 3D ergodic move set audited in Audit and independently validate all 3D CDT ergodic moves #106.
• Keep deterministic single-threaded fixtures as the canonical step-by-step oracle.
• Retain only the explicitly supported CGAL/oneTBB parallel boundary from Restore and validate multithreaded C++ support #88; no concurrent MCMC mutation is implied.
• Publish the compact versioned fixtures, schemas, raw results, named tolerances, explicit transition cases, and manifests from Publish deterministic C++ reference fixtures for Rust comparison #94.
• Provide the lightweight local/offline C++/Rust comparison harness from Build a local, offline C++/Rust comparison harness #104 without ML, hosted-service, credential, or network requirements.
• Preserve the opt-in CGAL/Qt viewer and reproducible repository-owned hero artifact from Restore the Qt viewer and reproducible artifact generation #98.
• Require one clean-checkout build/test contract, enforced release gates, a validated generated documentation site, synchronized metadata, and a complete archival handoff.
• Add no scientific capability beyond the completed supported 2+1-dimensional move set.

Remaining readiness path

Follow the native GitHub dependency graph:

1. Finish Restore and validate multithreaded C++ support #88.
2. Publish the bounded reference fixtures and manifests in Publish deterministic C++ reference fixtures for Rust comparison #94.
3. Complete Restore the Qt viewer and reproducible artifact generation #98 and Build a local, offline C++/Rust comparison harness #104.
4. Finalize the archival documentation site in Validate and finalize the archival documentation site #114.
5. Audit and enforce release gates in Audit and enforce the v1.0.0 build and CI release gates #95.
6. Finalize documentation and metadata in Prepare v1.0.0 documentation, metadata, and archival handoff #96.
7. Approve readiness here.
8. Execute publication and archival in Publish v1.0.0 and archive CDT-plusplus #97.

Acceptance criteria

• Every open v1.0.0 implementation, verification, tooling, and documentation issue other than Publish v1.0.0 and archive CDT-plusplus #97 is closed.
• The supported C++23 platform/compiler matrix and all required checks are green at the proposed release commit.
• The complete supported move set and scientific invariants are backed by Audit and independently validate all 3D CDT ergodic moves #106 and the deterministic cross-language contract in Publish deterministic C++ reference fixtures for Rust comparison #94.
• Exact combinatorial fields, named numerical tolerances, explicit deterministic transitions, one bounded end-to-end reference run, and complete provenance are versioned and reproducible.
• Randomized CGAL results and heuristic estimators are documented without presenting random topology counts as exact scientific oracles.
• The Restore and validate multithreaded C++ support #88 concurrency boundary, deterministic single-thread behavior, and existing scaling evidence are documented without overstating trajectory reproducibility.
• The local Python harness reproduces stored comparison summaries offline and contains no ML or hosted experiment requirement.
• The Qt workflow regenerates the committed hero artifact from repository-owned inputs while the default build remains headless.
• Release notes, README, API documentation, CITATION.cff, REFERENCES.md, version metadata, limitations, security/support boundary, successor link, and archival instructions agree.
• Publish v1.0.0 and archive CDT-plusplus #97 has a complete final sequence for tag, release, DOI/artifact verification, final issue closure, and repository archival.
• No 3+1-dimensional work, broad architecture rewrite, comprehensive new stochastic study, unrelated performance program, or other out-of-scope feature is included.

Lifecycle

Close #90 only as the readiness approval for #97. Do not tag, publish, or archive from this issue.