Publish v1.0.0 and archive CDT-plusplus

[acgetchell]

Summary

Publish CDT++ v1.0.0, verify the citable release, close the final tracker, and archive the repository.

This is the last issue in the dependency graph. It starts only after the release-readiness approval in #90 is closed. No implementation, test design, documentation authoring, dependency modernization, or new feature work belongs here.

Preconditions

• Approve CDT++ v1.0.0 release readiness #90 is closed with the release commit and validation evidence identified.
• No other issue or pull request remains open unless it is explicitly being preserved as historical and will be closed before archival.
• The release commit, version/date metadata, release notes, successor links, and Zenodo deposition metadata are final.
• The documented clean-checkout validation matrix is green.

Final execution sequence

1. Reconfirm the release commit and required GitHub Actions results.
2. Create and push the annotated v1.0.0 tag.
3. Publish the GitHub release with final notes, limitations, validation evidence, and the causal-triangulations successor link.
4. Verify GitHub source archives and every additional release artifact.
5. Publish or finalize the Zenodo record and verify its DOI, metadata, files, and links.
6. Update the repository description/homepage and confirm README/release links remain usable.
7. Close or disposition every remaining issue and pull request.
8. Close Publish v1.0.0 and archive CDT-plusplus #97 as the final repository issue mutation.
9. Immediately archive the repository and verify externally that it is public, readable, and read-only.

Acceptance criteria before closing #97

• The v1.0.0 tag and GitHub release are visible and internally consistent.
• The release commit is reproducibly buildable under the published matrix.
• Release artifacts and the Zenodo DOI record are verified.
• Repository metadata points to causal-triangulations.
• No other open issue or pull request remains.
• The repository's archival setting and the exact post-close archive action are prepared.
• No active-development claim remains.

Post-close action

Archive the repository immediately after closing #97. Because an archived repository is read-only, no issue may remain that requires a later state, body, label, milestone, or dependency change.