cwp content status

cwp content status [env] [flags]

Acts on the local site unless an environment is named.

Argument	What it is	Default
[env]	environment to compare (omit for the local site)

Plus the shared flags --json, --verbose and --dry-run.

What it does

Says what differs between the committed tree and a site, in both directions, writing nothing.

The same drift calculation cwp status --drift reports per artifact, here reported per page. Three states matter and are told apart:

• the tree has a page the site does not;
• the site has a page the tree does not;
• both have it and they differ — and, if they do, whether the tree moved or the site did, which is what _cwp_sync records.

That last distinction is what makes push able to refuse a page an editor changed on the target rather than overwriting it.

Example

cwp content status          # against the local site
cwp content status dev
cwp content status --json

What it does not do

It writes nothing to the site and nothing to the tree — not even a uid adoption. It is safe against production, and safe on a protected environment, because there is nothing for a guard to stop.