-
Notifications
You must be signed in to change notification settings - Fork 73
platform verification
Use this checklist to validate portability and path-handling behavior after changes.
-
Run core Node tests:
node skills/clawsec-suite/test/path_resolution.test.mjs node skills/clawsec-suite/test/guarded_install.test.mjs node skills/clawsec-suite/test/advisory_suppression.test.mjs node skills/openclaw-audit-watchdog/test/suppression_config.test.mjs
Expected: all tests pass.
-
Verify no literal
$HOMEpath acceptance:CLAWSEC_LOCAL_FEED='\$HOME/advisories/feed.json' \ node skills/clawsec-suite/scripts/guarded_skill_install.mjs --skill test-skill --dry-runExpected: exits non-zero with
Unexpanded home tokenerror. -
Verify
$HOMEexpansion works:HOME=/tmp/clawsec-home node skills/clawsec-suite/test/path_resolution.test.mjs
Expected:
$HOMEexpansion tests pass.
- Run the same Node test suite as Linux.
- Confirm OpenSSL tooling path assumptions are documented:
- If using LibreSSL/OpenSSL variations, ensure checks use tested command forms from docs.
- Verify tilde expansion in config path:
Expected: path resolves correctly (or clear file-not-found error at expanded location).
OPENCLAW_AUDIT_CONFIG=~/.openclaw/security-audit.json \ node skills/openclaw-audit-watchdog/scripts/load_suppression_config.mjs --enable-suppressions
-
Run Node tests:
node skills/clawsec-suite/test/path_resolution.test.mjs node skills/clawsec-suite/test/guarded_install.test.mjs node skills/clawsec-suite/test/advisory_suppression.test.mjs
Expected: all pass.
-
Verify PowerShell env path expansion behavior:
$env:CLAWSEC_LOCAL_FEED = '$env:USERPROFILE\advisories\feed.json' node skills/clawsec-suite/scripts/guarded_skill_install.mjs --skill test-skill --dry-run
Expected: path token is expanded/normalized or fails with a clear error if target files are missing.
-
Verify escaped literal token rejection:
$env:CLAWSEC_LOCAL_FEED = '\$HOME\advisories\feed.json' node skills/clawsec-suite/scripts/guarded_skill_install.mjs --skill test-skill --dry-run
Expected:
Unexpanded home tokenerror; no directory creation with literal$HOME.
-
Confirm LF policy is present:
test -f .gitattributes && grep -n "eol=lf" .gitattributes
Expected: script/config file patterns enforce LF.
-
After a CRLF-prone checkout, verify scripts still parse:
bash -n scripts/populate-local-feed.sh bash -n scripts/populate-local-skills.sh
Expected: no
^Mshebang/parse errors.
- Configure a path with a literal/escaped token.
- Run setup/install command.
- Verify command fails early with token error.
- Confirm no
$HOMEsegment directory was created under working directories.
Expected outcome: no directories containing literal $HOME are created by supported setup scripts.
- .gitattributes
- scripts/populate-local-feed.sh
- scripts/populate-local-skills.sh
- skills/clawsec-suite/test/path_resolution.test.mjs
- skills/clawsec-suite/test/guarded_install.test.mjs
- skills/clawsec-suite/test/advisory_suppression.test.mjs
- skills/clawsec-suite/scripts/guarded_skill_install.mjs
- skills/openclaw-audit-watchdog/scripts/load_suppression_config.mjs
- skills/openclaw-audit-watchdog/test/suppression_config.test.mjs