Update read_log to handle any log name

[DavidCockerill]

No description provided.

[claude]

1. Traversal guard uses && where || is needed — Windows backslash test will fail

File: validation/readLogValidator.js:45

What: && only blocks when both POSIX and Win32 agree the value is not a plain basename. For '..\\sensitive.log':

• path.posix.basename('..\\sensitive.log') → unchanged (backslash is a regular char on POSIX) → POSIX condition is false
• path.win32.basename('..\\sensitive.log') → 'sensitive.log' → Win32 condition is true
• false && true = false → traversal is not blocked

The value falls through to fs.existsSync, which returns false for a non-existent file, so the validator returns "does not exist." — directly failing the test added on line 130–140 of unitTests/validation/readLogValidator.test.js that expects "is invalid.".

Suggested fix: Change && to || on line 45. All plain filenames (hdb.log, clustering_connector) return identical values from both basename calls, so there are no false positives for valid inputs.

if (path.posix.basename(value) !== value || path.win32.basename(value) !== value) {

[kriszyp]

Great!

[cb1kenobi]

LGTM