qsd-doctor

To validate planning artifacts in long-running sessions, run a health-check via the qsd CLI to audit checkpoints, LATEST.json, and intel manifests, returning zero on success and non-zero on failure.

A deployment health-check includes eight distinct checks covering checkpoints validity, LATEST.json presence, settings.hooks consistency, no-symlink constraint, hook-log tail monitoring, intel-manifest availability, and policy-drift detection.

Yes, you need node installed because the doctor check runs via the qsd CLI, which requires a node environment to execute its eight validation checks across branches and installations.

You should run a deployment health-check for pre-session health validation and post-change regression checks to ensure the integrity of runtime configurations and planning artifacts across different branches.

To detect policy-drift and settings.hooks inconsistency, execute the doctor command via the qsd CLI, which performs targeted sanity checks on your runtime configurations and emits a non-zero code upon detecting drift.

The best way to monitor hook-log tails and checkpoint prune warnings is by running the doctor validation, which audits these specific runtime configurations and planning artifacts to verify overall installation health.