consensus-deployment-guard

This package is coherent with its stated purpose as a local pre-deployment guard, but review these before installing: - Provide Node >=18 and tsx from your environment (do not rely on the skill to supply the Node runtime). The metadata claim about 'creating binaries: node, tsx' appears to be a documentation/metadata error. - Set CONSENSUS_STATE_ROOT/CONSENSUS_STATE_FILE to a dedicated, non-privileged directory (do NOT point it at /etc, home, or any secrets volume). Follow the SECURITY-ASSURANCE.md recommendations (non-root user, scoped writable mount, deny-by-default egress). - Inspect and pin the transitive dependency 'consensus-guard-core' before running in production — the package delegates state/aggregation to that dependency and the maintainer note calls it part of the trust boundary. - Note run.js will also write a ./out/deployment-<timestamp>.json file in the current working directory; in automated environments set the working directory or container mount so that this write is acceptable. - Run npm test in an isolated environment and verify behavior on representative inputs; prefer running in a container or VM with limited egress and a scoped filesystem mount. If you need higher assurance, request evidence that consensus-guard-core has been audited/pinned and consider running the package inside a sandbox with a minimal environment allowlist.