Safe Command Guide

This guide lists default-safe commands for public documentation and website

work.

Public Docs And Site

Use:

make public-docs-milestone-0-check
make public-docs-milestone-1-check
make public-docs-milestone-2-check
make public-docs-milestone-3-check
make public-docs-milestone-4-check
make public-site-link-check
make public-site-build-check

These checks are bounded metadata, Markdown, and file checks. They do not run

compiler sweeps or mutate remote servers.

Package Metadata

Use:

make package-check

Heavy Or Opt-In Commands

These commands can be valid repository checks, but they are not default public

docs migration commands:

• make docs-check;
• make selfhost-guard;
• make memory-check;
• make libs-standalone-check;
• make libs-compile;
• release builds;
• browser, deployment, cluster, or remote publish checks.

Run heavy checks only when the host has enough resources and the work requires

that level of verification.

Remote Commands

Remote inventory must be read-only until deployment milestones produce dry-run,

checksum, rollback, and smoke evidence.