sard_stats_t_test.sas runs unmodified on Jenner — test bundle

[jenner-analytics]

sard_stats_t_test.sas from this package runs unmodified on Jenner, a SAS-compatible engine we develop. This PR adds an optional jenner-check/ directory: a byte-identical copy of the macro, a small caller with a mock ADSL built inline, the captured log and listing, and a runner. Nothing outside it is touched, and nothing runs on merge.

What caught my eye is how the macro reshapes PROC TTEST's ODS tables into a tidy long-format ARD — one row per stat_name (statistic, p.value, method, and so on), close to what R's broom::tidy() yields but built straight from SAS. The %if %upcase(&Welch)=Y switch that flips the WHERE between the Satterthwaite and Pooled rows, and the fmt_fun code-and-label pairing, are a nice touch.

The layout:

jenner-check/
├── run_jenner.sh
├── README.md
└── t001_macro_sard_stats_t_test/
    ├── script.sas        # macro + inline mock ADSL + README caller
    ├── autoexec.sas
    ├── expected.json     # fields pinned from the run
    └── expected/         # captured log + listing

To run the same script against the hosted API, from the repo root on this branch:

gh pr checkout 1
curl -sS --data-binary @jenner-check/t001_macro_sard_stats_t_test/script.sas https://api.jenneranalytics.com/v1/quick

Or cd jenner-check && ./run_jenner.sh --all re-runs the bundle and checks the pinned fields — free to try, no signup; reference in the docs.

On what leaves your machine: the runner sends only the script's SAS source text (plus a two-line autoexec) to api.jenneranalytics.com and returns the log and listing — no data files, so anything sitting next to a script stays local, and nothing is sent unless you run a command yourself.

Where this came from: we check Jenner against public SAS code, and this bundle is the test we wrote for your package, shared in case it's useful. It was assembled with AI assistance and reviewed by a person before sending, and the account is run by the Jenner project, which stands behind what it files. Merge, close, or ignore it — no reply is expected, and we won't open another PR here. To opt out, leave no-more-prs in any comment or open an issue titled jenner-check: opt out.