Validate an exported job schedule against local operating hours, holidays, deadlines, and required upstream jobs. It reads local documents, expands bounded real UTC minutes through an explicit IANA time zone, and never starts or changes a job.
This walkthrough uses the tool's public README and checked-in example files. Run the command from a repository checkout with Node.js 22+; inspect the source before using it on your own files.
Run the checked-in example
node bin/schedule-window-validator.mjs --root examples --schedule passing.json --policy policy.json
node bin/schedule-window-validator.mjs --root examples --schedule failing.json --policy policy.json --human
npm run checkRead the result
--root declares the evidence directory. --schedule and --policy are relative paths within it. Optional --out report.json writes a copy of stdout inside that root after alias and symlink checks. JSON always goes to stdout; --human adds a brief summary to stderr. --help lists options.
Where this check stops
This local walkthrough does not establish the state of a live production system or replace the limits documented in the repository.
Before adapting the command to your own workflow, review the accepted inputs, exit codes and safety boundaries in the README.
Compiled with AI assistance from checked-in public documentation and example scripts. Run the example and review the repository's current documentation before relying on its result.