Jenner compatibility tests for 3 SAS service(s)

[lwsinclair]

Jenneranalytics.com provides an API that runs SAS code, with support for more than 200 SAS procedures. You can also use it with Anthropic Claude Code AI in a collaborative workspace. It's available for Mac on the Apple App Store, and by license for Windows and Linux. The SAS services in this seed app run on it directly — this PR adds a few self-contained bundles so you can watch your own service code execute end to end.

jenner-check/
├── run_jenner.sh / .bat / .sas   # one runner, pick your platform
├── t001_serviceinit_springs/     # serviceinit.sas builds mydb.springs (1587 rows) + a PROC SQL roll-up
├── t002_appinit_distinct_areas/  # appinit.sas — SELECT DISTINCT area
└── t003_getdata_filter_by_area/  # getdata.sas — WHERE area IN (subquery) filter

Each directory holds the adapted script.sas, an autoexec.sas, and an expected/ snapshot of the captured run. Run them with cd jenner-check && ./run_jenner.sh --all, post a single script.sas with curl, or paste one into the hosted workspace. The %webout calls belong to the @sasjs/adapter runtime rather than Base SAS, so each bundle surfaces its result with a PROC PRINT in their place; the service SQL is unchanged.

One thing that stood out: shipping the full springs reference dataset inline as DATALINES4 in serviceinit.sas lets the seed app bootstrap with zero external data, and the three-service split — init builds the data, appinit lists the areas, getdata filters by selection — is a clean separation that maps neatly onto the frontend flow.

No response needed — merge, close, or ignore as you see fit. To opt out of future PRs like this, comment no-more-prs or open an issue titled jenner-check: opt out.