Prepare SASAbs for JOSS submission review

[D-sudoasd]

Summary

• rebuild the GitHub homepage as a professional research-software landing page
• refine the JOSS manuscript, bibliography, figures, and evidence boundaries
• align version, citation, repository, Zenodo, package, and release metadata
• strengthen Workbench provenance checks and add regression coverage
• add contributor templates, API documentation, distribution checks, and a fail-closed submission-readiness gate
• remove obsolete audit ledgers and superseded SoftwareX/JAC submission drafts from version control

Validation

• 696 passed on the source checkout
• 696 passed from the rebuilt source distribution
• Ruff passed
• isolated wheel install and pip check passed
• CLI version and normalization smoke passed
• minimal 2D synthetic example wrote CSV, TSV, XML, and HDF5
• Twine and CFF validation passed
• Inara TeX/JATS and the five-page review PDF passed visual inspection
• mechanical JOSS preflight passes for 2026-08-26 with author placeholders explicitly allowed
• final head 017af509d04764829afb0bc0cfa01bc1faadeecb passed 26/26 checks in both the push run and Draft-PR run, covering Ubuntu, Windows, and macOS with Python 3.10–3.13 plus the paper build

Important submission blockers

This PR is intentionally draft and must not be treated as authorization to submit to JOSS. Before submission, the author must still provide:

1. a verifiable real research-use case;
2. final author order, corresponding author/email, affiliations, ORCIDs, and contribution roles;
3. exact recoverable AI product/model/version details and human-review confirmation;
4. funding, sponsor-role, acknowledgement, and competing-interest statements;
5. confirmation that the public repository history exceeds six months on the actual submission date.

The v2.0.0 tag, GitHub Release, and exact Zenodo version DOI are deferred until the reviewed revision is ready, following the JOSS review workflow.