5 Commits

Include renames

Author	SHA1	Message	Date
dc	5eb8492742	fix(deploy): gate the browse actions on the settings file	2026-11-03 12:22:16 +00:00
dc	205d042bbe	docs(deploy): the window has no admin gate, and why ... Replaces the risk-register framing with the assessment: there is no admin group until makedata creates it, the caller is the administrator doing the deployment, the configurator in the same window is more powerful than these two actions, and a successful run deletes the service anyway. Filed as deploy-window-authorization.md so the next review finds the reasoning instead of re-raising the finding.	2026-11-03 11:59:24 +00:00
dc	e84cfaaabd	fix(deploy): ACTION cannot seed by default, and the probe stops overwriting ... Five defects from review, all mine. ACTION is no longer defaulted. `%let action=MAKEDATA;` meant a caller with no input table at all ran the seeding body - so a URL that never mentioned ACTION would create the control library. The default is MISSING, which is refused, and a URL parameter is whitelisted through the same check with symget() so it is never resolved as macro text. The write probe no longer has a predictable name. fopen with 'O' truncates, so a probe called .dcprobe_<pid> destroyed any pre-existing file of that name in the folder being tested. It now carries the pid and a random suffix, checks fileexist before use, and gives up rather than reuse a name. DIRLIST returns folders and locked entries only. The old filter dropped 'file' and passed every other value - blanks and unknown types - to the picker as a folder. The filter is now an explicit whitelist, and the header describes what is actually emitted. A request with no input table is refused, covered by a test: that is the case the default used to swallow. ngOnDestroy is gone from the client component - it reset a flag on a component being torn down. The deploy-window exposure is recorded in .agents/docs/, with why the admin group cannot be checked there: %mpeinit() reads &mpeadmins from the control library that makedata creates, so before it runs there is no group to check - which is also why the previous dirlist could never serve this screen.	2026-11-03 11:59:24 +00:00
dc	ad061946c3	docs(skills): add the estate deploy-and-test procedure ... 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.	2026-10-28 22:03:34 +00:00
hermes	f7db8719f5	fix: agent skills and nextviya deploys	2026-08-19 17:17:30 +01:00