The shared-estate cycle is two npm scripts and sasjs test, but the seed in npm run server is load-bearing: without it testsetup 404s settings.sas and 59 of the 64 test programs fail to complete, which reads like a broken deployment. Record the targets, the token-pair credentials, the ADMIN group the estate actually uses, how to read the results, and the frontend passphrase steps as a repo-local skill, and point the testing doc at it.