@loopress/cli 0.29.0 → 0.31.0

package/README.md

@@ -21,7 +21,7 @@ $ npm install -g @loopress/cli
 $ lps COMMAND
 running command...
 $ lps (--version)
-@loopress/cli/0.29.0 linux-x64 node-v24.21.0
+@loopress/cli/0.31.0 linux-x64 node-v24.21.0
 $ lps --help [COMMAND]
 USAGE
   $ lps COMMAND
@@ -67,6 +67,14 @@ report.
 * [`lps composer init`](#lps-composer-init)
 * [`lps composer pull`](#lps-composer-pull)
 * [`lps composer push`](#lps-composer-push)
+* [`lps content copy FROM`](#lps-content-copy-from)
+* [`lps cpt diff [PATH]`](#lps-cpt-diff-path)
+* [`lps cpt list`](#lps-cpt-list)
+* [`lps cpt pull [PATH]`](#lps-cpt-pull-path)
+* [`lps cpt push [PATH]`](#lps-cpt-push-path)
+* [`lps cpt remove SLUG`](#lps-cpt-remove-slug)
+* [`lps cpt rm SLUG`](#lps-cpt-rm-slug)
+* [`lps cpt rollback [PATH]`](#lps-cpt-rollback-path)
 * [`lps dev`](#lps-dev)
 * [`lps diff`](#lps-diff)
 * [`lps doctor`](#lps-doctor)
@@ -91,6 +99,13 @@ report.
 * [`lps menu pull [PATH]`](#lps-menu-pull-path)
 * [`lps menu push [PATH]`](#lps-menu-push-path)
 * [`lps menu rollback [PATH]`](#lps-menu-rollback-path)
+* [`lps meta diff [PATH]`](#lps-meta-diff-path)
+* [`lps meta list`](#lps-meta-list)
+* [`lps meta pull [PATH]`](#lps-meta-pull-path)
+* [`lps meta push [PATH]`](#lps-meta-push-path)
+* [`lps meta remove SLUG`](#lps-meta-remove-slug)
+* [`lps meta rm SLUG`](#lps-meta-rm-slug)
+* [`lps meta rollback [PATH]`](#lps-meta-rollback-path)
 * [`lps option add NAME`](#lps-option-add-name)
 * [`lps option diff [PATH]`](#lps-option-diff-path)
 * [`lps option list`](#lps-option-list)
@@ -101,6 +116,13 @@ report.
 * [`lps page diff [PATH]`](#lps-page-diff-path)
 * [`lps page list`](#lps-page-list)
 * [`lps page push [SLUG]`](#lps-page-push-slug)
+* [`lps pattern diff [PATH]`](#lps-pattern-diff-path)
+* [`lps pattern list`](#lps-pattern-list)
+* [`lps pattern pull [PATH]`](#lps-pattern-pull-path)
+* [`lps pattern push [PATH]`](#lps-pattern-push-path)
+* [`lps pattern remove SLUG`](#lps-pattern-remove-slug)
+* [`lps pattern rm SLUG`](#lps-pattern-rm-slug)
+* [`lps pattern rollback [PATH]`](#lps-pattern-rollback-path)
 * [`lps plugin add SLUG`](#lps-plugin-add-slug)
 * [`lps plugin audit`](#lps-plugin-audit)
 * [`lps plugin pull`](#lps-plugin-pull)
@@ -116,11 +138,13 @@ report.
 * [`lps promote FROM TO`](#lps-promote-from-to)
 * [`lps pull`](#lps-pull)
 * [`lps push`](#lps-push)
-* [`lps seo diff [PATH]`](#lps-seo-diff-path)
-* [`lps seo list`](#lps-seo-list)
-* [`lps seo pull [PATH]`](#lps-seo-pull-path)
-* [`lps seo push [PATH]`](#lps-seo-push-path)
-* [`lps seo rollback [PATH]`](#lps-seo-rollback-path)
+* [`lps role diff [PATH]`](#lps-role-diff-path)
+* [`lps role list`](#lps-role-list)
+* [`lps role pull [PATH]`](#lps-role-pull-path)
+* [`lps role push [PATH]`](#lps-role-push-path)
+* [`lps role remove SLUG`](#lps-role-remove-slug)
+* [`lps role rm SLUG`](#lps-role-rm-slug)
+* [`lps role rollback [PATH]`](#lps-role-rollback-path)
 * [`lps snippet diff [PATH]`](#lps-snippet-diff-path)
 * [`lps snippet list`](#lps-snippet-list)
 * [`lps snippet publish [PATH]`](#lps-snippet-publish-path)
@@ -128,6 +152,13 @@ report.
 * [`lps snippet push [PATH]`](#lps-snippet-push-path)
 * [`lps snippet rollback [PATH]`](#lps-snippet-rollback-path)
 * [`lps status`](#lps-status)
+* [`lps taxonomy diff [PATH]`](#lps-taxonomy-diff-path)
+* [`lps taxonomy list`](#lps-taxonomy-list)
+* [`lps taxonomy pull [PATH]`](#lps-taxonomy-pull-path)
+* [`lps taxonomy push [PATH]`](#lps-taxonomy-push-path)
+* [`lps taxonomy remove SLUG`](#lps-taxonomy-remove-slug)
+* [`lps taxonomy rm SLUG`](#lps-taxonomy-rm-slug)
+* [`lps taxonomy rollback [PATH]`](#lps-taxonomy-rollback-path)
 * [`lps telemetry disable`](#lps-telemetry-disable)
 * [`lps telemetry enable`](#lps-telemetry-enable)
 * [`lps theme add SLUG`](#lps-theme-add-slug)
@@ -158,7 +189,7 @@ ARGUMENTS
 
 FLAGS
   --against=<value>  Compare the primary environment against this second environment instead of against local files
-  --env=<value>      Target environment by name, overriding the globally active one (lps project switch)
+  --env=<value>      Target environment by name (default: "local", or the project's only environment)
 
 GLOBAL FLAGS
   --json  Format output as json.
@@ -175,7 +206,7 @@ EXAMPLES
   $ lps acf diff --env staging --against production
 ```
 
-_See code: [src/commands/acf/diff.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.29.0/cli/src/commands/acf/diff.ts)_
+_See code: [src/commands/acf/diff.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.31.0/cli/src/commands/acf/diff.ts)_
 
 ## `lps acf list`
 
@@ -186,7 +217,7 @@ USAGE
   $ lps acf list [--json] [--env <value>] [--type field-groups|post-types|taxonomies|options-pages...]
 
 FLAGS
-  --env=<value>       Target environment by name, overriding the globally active one (lps project switch)
+  --env=<value>       Target environment by name (default: "local", or the project's only environment)
   --type=<option>...  Limit to specific ACF object types
                       <options: field-groups|post-types|taxonomies|options-pages>
 
@@ -202,7 +233,7 @@ EXAMPLES
   $ lps acf list --type field-groups
 ```
 
-_See code: [src/commands/acf/list.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.29.0/cli/src/commands/acf/list.ts)_
+_See code: [src/commands/acf/list.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.31.0/cli/src/commands/acf/list.ts)_
 
 ## `lps acf pull [PATH]`
 
@@ -219,7 +250,7 @@ ARGUMENTS
 FLAGS
   -d, --dry-run           Show what would change without making changes
   -y, --yes               Answer yes to confirmation prompts
-      --env=<value>       Target environment by name, overriding the globally active one (lps project switch)
+      --env=<value>       Target environment by name (default: "local", or the project's only environment)
       --type=<option>...  Limit to specific ACF object types
                           <options: field-groups|post-types|taxonomies|options-pages>
 
@@ -235,7 +266,7 @@ EXAMPLES
   $ lps acf pull --type field-groups
 ```
 
-_See code: [src/commands/acf/pull.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.29.0/cli/src/commands/acf/pull.ts)_
+_See code: [src/commands/acf/pull.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.31.0/cli/src/commands/acf/pull.ts)_
 
 ## `lps acf push [PATH]`
 
@@ -243,7 +274,7 @@ Push ACF field groups, post types, taxonomies, and options pages to WordPress
 
 ```
 USAGE
-  $ lps acf push [PATH] [--json] [--env <value>] [-d] [-y] [--type
+  $ lps acf push [PATH] [--json] [--env <value>] [--overwrite] [-d] [-y] [--type
     field-groups|post-types|taxonomies|options-pages...]
 
 ARGUMENTS
@@ -252,7 +283,8 @@ ARGUMENTS
 FLAGS
   -d, --dry-run           Show what would change without making changes
   -y, --yes               Answer yes to confirmation prompts
-      --env=<value>       Target environment by name, overriding the globally active one (lps project switch)
+      --env=<value>       Target environment by name (default: "local", or the project's only environment)
+      --overwrite         Push even over changes made on the site outside Loopress since your last push
       --type=<option>...  Limit to specific ACF object types
                           <options: field-groups|post-types|taxonomies|options-pages>
 
@@ -268,7 +300,7 @@ EXAMPLES
   $ lps acf push --type field-groups
 ```
 
-_See code: [src/commands/acf/push.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.29.0/cli/src/commands/acf/push.ts)_
+_See code: [src/commands/acf/push.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.31.0/cli/src/commands/acf/push.ts)_
 
 ## `lps acf rollback [PATH]`
 
@@ -284,7 +316,7 @@ ARGUMENTS
 FLAGS
   -d, --dry-run      Show what would change without making changes
   -y, --yes          Answer yes to confirmation prompts
-      --env=<value>  Target environment by name, overriding the globally active one (lps project switch)
+      --env=<value>  Target environment by name (default: "local", or the project's only environment)
       --list         List available snapshots instead of rolling back
       --to=<value>   Roll back to this snapshot id instead of the most recent one
 
@@ -305,7 +337,7 @@ EXAMPLES
   $ lps acf rollback --dry-run
 ```
 
-_See code: [src/commands/acf/rollback.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.29.0/cli/src/commands/acf/rollback.ts)_
+_See code: [src/commands/acf/rollback.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.31.0/cli/src/commands/acf/rollback.ts)_
 
 ## `lps api diff [PATH]`
 
@@ -320,7 +352,7 @@ ARGUMENTS
 
 FLAGS
   --against=<value>  Compare the primary environment against this second environment instead of against local files
-  --env=<value>      Target environment by name, overriding the globally active one (lps project switch)
+  --env=<value>      Target environment by name (default: "local", or the project's only environment)
 
 GLOBAL FLAGS
   --json  Format output as json.
@@ -337,7 +369,7 @@ EXAMPLES
   $ lps api diff --env staging --against production
 ```
 
-_See code: [src/commands/api/diff.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.29.0/cli/src/commands/api/diff.ts)_
+_See code: [src/commands/api/diff.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.31.0/cli/src/commands/api/diff.ts)_
 
 ## `lps api list`
 
@@ -348,7 +380,7 @@ USAGE
   $ lps api list [--json] [--env <value>]
 
 FLAGS
-  --env=<value>  Target environment by name, overriding the globally active one (lps project switch)
+  --env=<value>  Target environment by name (default: "local", or the project's only environment)
 
 GLOBAL FLAGS
   --json  Format output as json.
@@ -360,7 +392,7 @@ EXAMPLES
   $ lps api list
 ```
 
-_See code: [src/commands/api/list.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.29.0/cli/src/commands/api/list.ts)_
+_See code: [src/commands/api/list.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.31.0/cli/src/commands/api/list.ts)_
 
 ## `lps api publish [PATH]`
 
@@ -383,7 +415,7 @@ EXAMPLES
   $ lps api publish ./api
 ```
 
-_See code: [src/commands/api/publish.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.29.0/cli/src/commands/api/publish.ts)_
+_See code: [src/commands/api/publish.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.31.0/cli/src/commands/api/publish.ts)_
 
 ## `lps api pull [PATH]`
 
@@ -399,7 +431,7 @@ ARGUMENTS
 FLAGS
   -d, --dry-run      Show what would change without making changes
   -y, --yes          Answer yes to confirmation prompts
-      --env=<value>  Target environment by name, overriding the globally active one (lps project switch)
+      --env=<value>  Target environment by name (default: "local", or the project's only environment)
 
 GLOBAL FLAGS
   --json  Format output as json.
@@ -413,7 +445,7 @@ EXAMPLES
   $ lps api pull --path ./api
 ```
 
-_See code: [src/commands/api/pull.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.29.0/cli/src/commands/api/pull.ts)_
+_See code: [src/commands/api/pull.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.31.0/cli/src/commands/api/pull.ts)_
 
 ## `lps api push [PATH]`
 
@@ -421,7 +453,7 @@ Push custom API route files to WordPress
 
 ```
 USAGE
-  $ lps api push [PATH] [--json] [--env <value>] [-d] [-y] [--prune]
+  $ lps api push [PATH] [--json] [--env <value>] [--overwrite] [-d] [-y] [--prune]
 
 ARGUMENTS
   [PATH]  Path to api directory (overrides project config)
@@ -429,7 +461,8 @@ ARGUMENTS
 FLAGS
   -d, --dry-run      Show what would change without making changes
   -y, --yes          Answer yes to confirmation prompts
-      --env=<value>  Target environment by name, overriding the globally active one (lps project switch)
+      --env=<value>  Target environment by name (default: "local", or the project's only environment)
+      --overwrite    Push even over changes made on the site outside Loopress since your last push
       --prune        Delete server-side route files not present locally after pushing
 
 GLOBAL FLAGS
@@ -446,7 +479,7 @@ EXAMPLES
   $ lps api push --prune
 ```
 
-_See code: [src/commands/api/push.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.29.0/cli/src/commands/api/push.ts)_
+_See code: [src/commands/api/push.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.31.0/cli/src/commands/api/push.ts)_
 
 ## `lps api remove FILENAME`
 
@@ -462,7 +495,7 @@ ARGUMENTS
 FLAGS
   -d, --dry-run      Show what would change without making changes
   -y, --yes          Answer yes to confirmation prompts
-      --env=<value>  Target environment by name, overriding the globally active one (lps project switch)
+      --env=<value>  Target environment by name (default: "local", or the project's only environment)
 
 GLOBAL FLAGS
   --json  Format output as json.
@@ -493,7 +526,7 @@ ARGUMENTS
 FLAGS
   -d, --dry-run      Show what would change without making changes
   -y, --yes          Answer yes to confirmation prompts
-      --env=<value>  Target environment by name, overriding the globally active one (lps project switch)
+      --env=<value>  Target environment by name (default: "local", or the project's only environment)
 
 GLOBAL FLAGS
   --json  Format output as json.
@@ -510,7 +543,7 @@ EXAMPLES
   $ lps api remove hello --yes
 ```
 
-_See code: [src/commands/api/rm.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.29.0/cli/src/commands/api/rm.ts)_
+_See code: [src/commands/api/rm.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.31.0/cli/src/commands/api/rm.ts)_
 
 ## `lps api rollback [PATH]`
 
@@ -526,7 +559,7 @@ ARGUMENTS
 FLAGS
   -d, --dry-run      Show what would change without making changes
   -y, --yes          Answer yes to confirmation prompts
-      --env=<value>  Target environment by name, overriding the globally active one (lps project switch)
+      --env=<value>  Target environment by name (default: "local", or the project's only environment)
       --list         List available snapshots instead of rolling back
       --to=<value>   Roll back to this snapshot id instead of the most recent one
 
@@ -546,7 +579,7 @@ EXAMPLES
   $ lps api rollback --dry-run
 ```
 
-_See code: [src/commands/api/rollback.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.29.0/cli/src/commands/api/rollback.ts)_
+_See code: [src/commands/api/rollback.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.31.0/cli/src/commands/api/rollback.ts)_
 
 ## `lps app list`
 
@@ -557,7 +590,7 @@ USAGE
   $ lps app list [--json] [--env <value>]
 
 FLAGS
-  --env=<value>  Target environment by name, overriding the globally active one (lps project switch)
+  --env=<value>  Target environment by name (default: "local", or the project's only environment)
 
 GLOBAL FLAGS
   --json  Format output as json.
@@ -569,7 +602,7 @@ EXAMPLES
   $ lps app list
 ```
 
-_See code: [src/commands/app/list.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.29.0/cli/src/commands/app/list.ts)_
+_See code: [src/commands/app/list.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.31.0/cli/src/commands/app/list.ts)_
 
 ## `lps app pull [PATH]`
 
@@ -585,7 +618,7 @@ ARGUMENTS
 FLAGS
   -d, --dry-run      Show what would change without making changes
   -y, --yes          Answer yes to confirmation prompts
-      --env=<value>  Target environment by name, overriding the globally active one (lps project switch)
+      --env=<value>  Target environment by name (default: "local", or the project's only environment)
 
 GLOBAL FLAGS
   --json  Format output as json.
@@ -597,7 +630,7 @@ EXAMPLES
   $ lps app pull
 ```
 
-_See code: [src/commands/app/pull.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.29.0/cli/src/commands/app/pull.ts)_
+_See code: [src/commands/app/pull.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.31.0/cli/src/commands/app/pull.ts)_
 
 ## `lps app push [NAME]`
 
@@ -605,7 +638,7 @@ Build and push single-page app bundles to WordPress. Each app is an `apps/<name>
 
 ```
 USAGE
-  $ lps app push [NAME] [--json] [--env <value>] [--build] [-d] [-y]
+  $ lps app push [NAME] [--json] [--env <value>] [--overwrite] [--build] [-d] [-y]
 
 ARGUMENTS
   [NAME]  Push only this app (defaults to every app in the directory)
@@ -614,7 +647,8 @@ FLAGS
   -d, --dry-run      Show what would change without making changes
   -y, --yes          Answer yes to confirmation prompts
       --[no-]build   Run the app's package.json build script before pushing
-      --env=<value>  Target environment by name, overriding the globally active one (lps project switch)
+      --env=<value>  Target environment by name (default: "local", or the project's only environment)
+      --overwrite    Push even over changes made on the site outside Loopress since your last push
 
 GLOBAL FLAGS
   --json  Format output as json.
@@ -632,7 +666,7 @@ EXAMPLES
   $ lps app push --no-build
 ```
 
-_See code: [src/commands/app/push.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.29.0/cli/src/commands/app/push.ts)_
+_See code: [src/commands/app/push.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.31.0/cli/src/commands/app/push.ts)_
 
 ## `lps app remove NAME`
 
@@ -648,7 +682,7 @@ ARGUMENTS
 FLAGS
   -d, --dry-run      Show what would change without making changes
   -y, --yes          Answer yes to confirmation prompts
-      --env=<value>  Target environment by name, overriding the globally active one (lps project switch)
+      --env=<value>  Target environment by name (default: "local", or the project's only environment)
 
 GLOBAL FLAGS
   --json  Format output as json.
@@ -661,7 +695,7 @@ EXAMPLES
   $ lps app remove search
 ```
 
-_See code: [src/commands/app/remove.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.29.0/cli/src/commands/app/remove.ts)_
+_See code: [src/commands/app/remove.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.31.0/cli/src/commands/app/remove.ts)_
 
 ## `lps composer init`
 
@@ -673,7 +707,7 @@ USAGE
 
 FLAGS
   -d, --dry-run      Show what would change without making changes
-      --env=<value>  Target environment by name, overriding the globally active one (lps project switch)
+      --env=<value>  Target environment by name (default: "local", or the project's only environment)
 
 DESCRIPTION
   Create a composer.json wired to WPackagist for installing WordPress.org plugins and themes
@@ -684,7 +718,7 @@ EXAMPLES
   $ lps composer init --dry-run
 ```
 
-_See code: [src/commands/composer/init.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.29.0/cli/src/commands/composer/init.ts)_
+_See code: [src/commands/composer/init.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.31.0/cli/src/commands/composer/init.ts)_
 
 ## `lps composer pull`
 
@@ -696,7 +730,7 @@ USAGE
 
 FLAGS
   -d, --dry-run      Show what would change without making changes
-      --env=<value>  Target environment by name, overriding the globally active one (lps project switch)
+      --env=<value>  Target environment by name (default: "local", or the project's only environment)
 
 GLOBAL FLAGS
   --json  Format output as json.
@@ -710,7 +744,7 @@ EXAMPLES
   $ lps composer pull --dry-run
 ```
 
-_See code: [src/commands/composer/pull.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.29.0/cli/src/commands/composer/pull.ts)_
+_See code: [src/commands/composer/pull.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.31.0/cli/src/commands/composer/pull.ts)_
 
 ## `lps composer push`
 
@@ -718,13 +752,14 @@ Push composer.json to WordPress and run Composer to resolve and install dependen
 
 ```
 USAGE
-  $ lps composer push [--json] [--env <value>] [-d] [-y] [--force]
+  $ lps composer push [--json] [--env <value>] [--overwrite] [-d] [-y] [--force]
 
 FLAGS
   -d, --dry-run      Show what would change without making changes
   -y, --yes          Answer yes to confirmation prompts
-      --env=<value>  Target environment by name, overriding the globally active one (lps project switch)
+      --env=<value>  Target environment by name (default: "local", or the project's only environment)
       --force        Allow downgrades and take over plugins/themes installed outside Loopress
+      --overwrite    Push even over changes made on the site outside Loopress since your last push
 
 GLOBAL FLAGS
   --json  Format output as json.
@@ -738,7 +773,255 @@ EXAMPLES
   $ lps composer push --dry-run
 ```
 
-_See code: [src/commands/composer/push.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.29.0/cli/src/commands/composer/push.ts)_
+_See code: [src/commands/composer/push.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.31.0/cli/src/commands/composer/push.ts)_
+
+## `lps content copy FROM`
+
+Replace the local site's content (posts, pages, public custom post types, terms) with the content of <from>, then push the project to the local site so tracked configuration wins. Media stay served by <from>, users, comments and orders are never copied.
+
+```
+USAGE
+  $ lps content copy FROM [--json] [-d] [-y]
+
+ARGUMENTS
+  FROM  Environment to copy the content from
+
+FLAGS
+  -d, --dry-run  Show what would change without making changes
+  -y, --yes      Answer yes to confirmation prompts
+
+GLOBAL FLAGS
+  --json  Format output as json.
+
+DESCRIPTION
+  Replace the local site's content (posts, pages, public custom post types, terms) with the content of <from>, then push
+  the project to the local site so tracked configuration wins. Media stay served by <from>, users, comments and orders
+  are never copied.
+
+EXAMPLES
+  $ lps content copy production
+
+  $ lps content copy staging --dry-run
+```
+
+_See code: [src/commands/content/copy.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.31.0/cli/src/commands/content/copy.ts)_
+
+## `lps cpt diff [PATH]`
+
+Show what differs in custom post types between your local cpt/ files and a WordPress environment, or between two environments
+
+```
+USAGE
+  $ lps cpt diff [PATH] [--json] [--env <value>] [--against <value>]
+
+ARGUMENTS
+  [PATH]  Path to cpt directory (overrides project config)
+
+FLAGS
+  --against=<value>  Compare the primary environment against this second environment instead of against local files
+  --env=<value>      Target environment by name (default: "local", or the project's only environment)
+
+GLOBAL FLAGS
+  --json  Format output as json.
+
+DESCRIPTION
+  Show what differs in custom post types between your local cpt/ files and a WordPress environment, or between two
+  environments
+
+EXAMPLES
+  $ lps cpt diff
+
+  $ lps cpt diff --env staging
+
+  $ lps cpt diff --env staging --against production
+```
+
+_See code: [src/commands/cpt/diff.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.31.0/cli/src/commands/cpt/diff.ts)_
+
+## `lps cpt list`
+
+List the post types registered on WordPress and where each comes from (Loopress, WordPress, ACF, CPT UI, a theme or plugin). Only Loopress ones are pulled and pushed.
+
+```
+USAGE
+  $ lps cpt list [--json] [--env <value>]
+
+FLAGS
+  --env=<value>  Target environment by name (default: "local", or the project's only environment)
+
+GLOBAL FLAGS
+  --json  Format output as json.
+
+DESCRIPTION
+  List the post types registered on WordPress and where each comes from (Loopress, WordPress, ACF, CPT UI, a theme or
+  plugin). Only Loopress ones are pulled and pushed.
+
+EXAMPLES
+  $ lps cpt list
+```
+
+_See code: [src/commands/cpt/list.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.31.0/cli/src/commands/cpt/list.ts)_
+
+## `lps cpt pull [PATH]`
+
+Pull the custom post types Loopress manages on WordPress into cpt/<slug>.json files. Post types registered by a theme or another plugin are never pulled, see `lps cpt list`.
+
+```
+USAGE
+  $ lps cpt pull [PATH] [--json] [--env <value>] [-d] [-y]
+
+ARGUMENTS
+  [PATH]  Path to the cpt directory (overrides project config)
+
+FLAGS
+  -d, --dry-run      Show what would change without making changes
+  -y, --yes          Answer yes to confirmation prompts
+      --env=<value>  Target environment by name (default: "local", or the project's only environment)
+
+GLOBAL FLAGS
+  --json  Format output as json.
+
+DESCRIPTION
+  Pull the custom post types Loopress manages on WordPress into cpt/<slug>.json files. Post types registered by a theme
+  or another plugin are never pulled, see `lps cpt list`.
+
+EXAMPLES
+  $ lps cpt pull
+```
+
+_See code: [src/commands/cpt/pull.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.31.0/cli/src/commands/cpt/pull.ts)_
+
+## `lps cpt push [PATH]`
+
+Push local custom post types (cpt/<slug>.json, register_post_type() arguments) to WordPress. Create or update only, never deletes a post type: use `lps cpt rm` for that.
+
+```
+USAGE
+  $ lps cpt push [PATH] [--json] [--env <value>] [--overwrite] [-d] [-y]
+
+ARGUMENTS
+  [PATH]  Path to the cpt directory (overrides project config)
+
+FLAGS
+  -d, --dry-run      Show what would change without making changes
+  -y, --yes          Answer yes to confirmation prompts
+      --env=<value>  Target environment by name (default: "local", or the project's only environment)
+      --overwrite    Push even over changes made on the site outside Loopress since your last push
+
+GLOBAL FLAGS
+  --json  Format output as json.
+
+DESCRIPTION
+  Push local custom post types (cpt/<slug>.json, register_post_type() arguments) to WordPress. Create or update only,
+  never deletes a post type: use `lps cpt rm` for that.
+
+EXAMPLES
+  $ lps cpt push
+```
+
+_See code: [src/commands/cpt/push.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.31.0/cli/src/commands/cpt/push.ts)_
+
+## `lps cpt remove SLUG`
+
+Stop registering a Loopress custom post type on WordPress. Its posts are kept in the database, hidden until the post type is pushed again.
+
+```
+USAGE
+  $ lps cpt remove SLUG [--json] [--env <value>] [-d] [-y]
+
+ARGUMENTS
+  SLUG  The post type slug, its cpt/ file name without .json
+
+FLAGS
+  -d, --dry-run      Show what would change without making changes
+  -y, --yes          Answer yes to confirmation prompts
+      --env=<value>  Target environment by name (default: "local", or the project's only environment)
+
+GLOBAL FLAGS
+  --json  Format output as json.
+
+DESCRIPTION
+  Stop registering a Loopress custom post type on WordPress. Its posts are kept in the database, hidden until the post
+  type is pushed again.
+
+ALIASES
+  $ lps cpt remove
+
+EXAMPLES
+  $ lps cpt rm <slug>
+
+  $ lps cpt remove <slug> --yes
+```
+
+## `lps cpt rm SLUG`
+
+Stop registering a Loopress custom post type on WordPress. Its posts are kept in the database, hidden until the post type is pushed again.
+
+```
+USAGE
+  $ lps cpt rm SLUG [--json] [--env <value>] [-d] [-y]
+
+ARGUMENTS
+  SLUG  The post type slug, its cpt/ file name without .json
+
+FLAGS
+  -d, --dry-run      Show what would change without making changes
+  -y, --yes          Answer yes to confirmation prompts
+      --env=<value>  Target environment by name (default: "local", or the project's only environment)
+
+GLOBAL FLAGS
+  --json  Format output as json.
+
+DESCRIPTION
+  Stop registering a Loopress custom post type on WordPress. Its posts are kept in the database, hidden until the post
+  type is pushed again.
+
+ALIASES
+  $ lps cpt remove
+
+EXAMPLES
+  $ lps cpt rm <slug>
+
+  $ lps cpt remove <slug> --yes
+```
+
+_See code: [src/commands/cpt/rm.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.31.0/cli/src/commands/cpt/rm.ts)_
+
+## `lps cpt rollback [PATH]`
+
+Restore custom post types to a snapshot taken automatically before an earlier `lps cpt push`
+
+```
+USAGE
+  $ lps cpt rollback [PATH] [--json] [--env <value>] [-d] [-y] [--list] [--to <value>]
+
+ARGUMENTS
+  [PATH]  Path to cpt directory (overrides project config)
+
+FLAGS
+  -d, --dry-run      Show what would change without making changes
+  -y, --yes          Answer yes to confirmation prompts
+      --env=<value>  Target environment by name (default: "local", or the project's only environment)
+      --list         List available snapshots instead of rolling back
+      --to=<value>   Roll back to this snapshot id instead of the most recent one
+
+GLOBAL FLAGS
+  --json  Format output as json.
+
+DESCRIPTION
+  Restore custom post types to a snapshot taken automatically before an earlier `lps cpt push`
+
+EXAMPLES
+  $ lps cpt rollback
+
+  $ lps cpt rollback --list
+
+  $ lps cpt rollback --to 1732000000000
+
+  $ lps cpt rollback --dry-run
+```
+
+_See code: [src/commands/cpt/rollback.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.31.0/cli/src/commands/cpt/rollback.ts)_
 
 ## `lps dev`
 
@@ -749,9 +1032,10 @@ USAGE
   $ lps dev [--only <value>] [--skip <value>]
 
 FLAGS
-  --only=<value>  Only watch these resource types (comma-separated): snippets, templates, parts, pages, api, hooks,
-                  plugins
-  --skip=<value>  Skip these resource types (comma-separated): snippets, templates, parts, pages, api, hooks, plugins
+  --only=<value>  Only watch these resource types (comma-separated): snippets, templates, parts, css, blocks, pages,
+                  api, hooks, plugins
+  --skip=<value>  Skip these resource types (comma-separated): snippets, templates, parts, css, blocks, pages, api,
+                  hooks, plugins
 
 DESCRIPTION
   Watch project files and push changes to the local WordPress instance as they happen. Always targets the "local"
@@ -765,34 +1049,37 @@ EXAMPLES
   $ lps dev --skip=plugins
 ```
 
-_See code: [src/commands/dev.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.29.0/cli/src/commands/dev.ts)_
+_See code: [src/commands/dev.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.31.0/cli/src/commands/dev.ts)_
 
 ## `lps diff`
 
-Show what differs between your local tracked files and a WordPress environment, or between two environments. Covers snippets, forms, ACF, API routes, Hooks, templates, template parts, pages, SEO, Options, Menus, Theme styles, and Composer. Plugins and themes have their own `lps plugin status` / `lps theme status`. Exit code: 0 in sync, 1 on drift, 2 when a resource could not be compared, so it doubles as a CI drift gate.
+Show what differs between your local tracked files and a WordPress environment, or between two environments. Covers snippets, forms, ACF, API routes, Hooks, templates, template parts, pages, Options, Menus, Theme styles, and Composer. Plugins and themes have their own `lps plugin status` / `lps theme status`. Exit code: 0 in sync, 1 on drift, 2 when a resource could not be compared, so it doubles as a CI drift gate.
 
 ```
 USAGE
   $ lps diff [--json] [--env <value>] [--against <value>] [--only
-    snippet|form|acf|api|hook|template|part|page|seo|menu|option|theme-styles|composer...] [--skip
-    snippet|form|acf|api|hook|template|part|page|seo|menu|option|theme-styles|composer...]
+    snippet|form|acf|api|hook|template|part|page|menu|cpt|taxonomy|meta|role|pattern|option|theme-styles|composer...]
+    [--skip
+    snippet|form|acf|api|hook|template|part|page|menu|cpt|taxonomy|meta|role|pattern|option|theme-styles|composer...]
 
 FLAGS
   --against=<value>   Compare the primary environment against this second environment instead of against local files
-  --env=<value>       Target environment by name, overriding the globally active one (lps project switch)
+  --env=<value>       Target environment by name (default: "local", or the project's only environment)
   --only=<option>...  Only compare these resources
-                      <options: snippet|form|acf|api|hook|template|part|page|seo|menu|option|theme-styles|composer>
+                      <options: snippet|form|acf|api|hook|template|part|page|menu|cpt|taxonomy|meta|role|pattern|option|
+                      theme-styles|composer>
   --skip=<option>...  Compare every resource except these
-                      <options: snippet|form|acf|api|hook|template|part|page|seo|menu|option|theme-styles|composer>
+                      <options: snippet|form|acf|api|hook|template|part|page|menu|cpt|taxonomy|meta|role|pattern|option|
+                      theme-styles|composer>
 
 GLOBAL FLAGS
   --json  Format output as json.
 
 DESCRIPTION
   Show what differs between your local tracked files and a WordPress environment, or between two environments. Covers
-  snippets, forms, ACF, API routes, Hooks, templates, template parts, pages, SEO, Options, Menus, Theme styles, and
-  Composer. Plugins and themes have their own `lps plugin status` / `lps theme status`. Exit code: 0 in sync, 1 on
-  drift, 2 when a resource could not be compared, so it doubles as a CI drift gate.
+  snippets, forms, ACF, API routes, Hooks, templates, template parts, pages, Options, Menus, Theme styles, and Composer.
+  Plugins and themes have their own `lps plugin status` / `lps theme status`. Exit code: 0 in sync, 1 on drift, 2 when a
+  resource could not be compared, so it doubles as a CI drift gate.
 
 EXAMPLES
   $ lps diff
@@ -806,7 +1093,7 @@ EXAMPLES
   $ lps diff --skip composer
 ```
 
-_See code: [src/commands/diff.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.29.0/cli/src/commands/diff.ts)_
+_See code: [src/commands/diff.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.31.0/cli/src/commands/diff.ts)_
 
 ## `lps doctor`
 
@@ -817,7 +1104,7 @@ USAGE
   $ lps doctor [--json] [--env <value>]
 
 FLAGS
-  --env=<value>  Target environment by name, overriding the globally active one (lps project switch)
+  --env=<value>  Target environment by name (default: "local", or the project's only environment)
 
 GLOBAL FLAGS
   --json  Format output as json.
@@ -831,7 +1118,7 @@ EXAMPLES
   $ lps doctor --env production
 ```
 
-_See code: [src/commands/doctor.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.29.0/cli/src/commands/doctor.ts)_
+_See code: [src/commands/doctor.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.31.0/cli/src/commands/doctor.ts)_
 
 ## `lps form diff [PATH]`
 
@@ -846,7 +1133,7 @@ ARGUMENTS
 
 FLAGS
   --against=<value>  Compare the primary environment against this second environment instead of against local files
-  --env=<value>      Target environment by name, overriding the globally active one (lps project switch)
+  --env=<value>      Target environment by name (default: "local", or the project's only environment)
 
 GLOBAL FLAGS
   --json  Format output as json.
@@ -862,7 +1149,7 @@ EXAMPLES
   $ lps form diff --env staging --against production
 ```
 
-_See code: [src/commands/form/diff.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.29.0/cli/src/commands/form/diff.ts)_
+_See code: [src/commands/form/diff.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.31.0/cli/src/commands/form/diff.ts)_
 
 ## `lps form list`
 
@@ -873,7 +1160,7 @@ USAGE
   $ lps form list [--json] [--env <value>]
 
 FLAGS
-  --env=<value>  Target environment by name, overriding the globally active one (lps project switch)
+  --env=<value>  Target environment by name (default: "local", or the project's only environment)
 
 GLOBAL FLAGS
   --json  Format output as json.
@@ -885,7 +1172,7 @@ EXAMPLES
   $ lps form list
 ```
 
-_See code: [src/commands/form/list.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.29.0/cli/src/commands/form/list.ts)_
+_See code: [src/commands/form/list.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.31.0/cli/src/commands/form/list.ts)_
 
 ## `lps form pull [PATH]`
 
@@ -901,7 +1188,7 @@ ARGUMENTS
 FLAGS
   -d, --dry-run      Show what would change without making changes
   -y, --yes          Answer yes to confirmation prompts
-      --env=<value>  Target environment by name, overriding the globally active one (lps project switch)
+      --env=<value>  Target environment by name (default: "local", or the project's only environment)
 
 GLOBAL FLAGS
   --json  Format output as json.
@@ -913,7 +1200,7 @@ EXAMPLES
   $ lps form pull
 ```
 
-_See code: [src/commands/form/pull.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.29.0/cli/src/commands/form/pull.ts)_
+_See code: [src/commands/form/pull.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.31.0/cli/src/commands/form/pull.ts)_
 
 ## `lps form push [PATH]`
 
@@ -921,7 +1208,7 @@ Push forms to WordPress. Local files created or updated remotely are renamed on
 
 ```
 USAGE
-  $ lps form push [PATH] [--json] [--env <value>] [-d] [-y] [--allow-notifications]
+  $ lps form push [PATH] [--json] [--env <value>] [--overwrite] [-d] [-y] [--allow-notifications]
 
 ARGUMENTS
   [PATH]  Path to forms directory (overrides project config)
@@ -932,7 +1219,8 @@ FLAGS
       --allow-notifications  Also push each form's notification and confirmation settings (recipients, sender,
                              messages). Off by default: the server keeps its own so a stray push can't redirect
                              submissions.
-      --env=<value>          Target environment by name, overriding the globally active one (lps project switch)
+      --env=<value>          Target environment by name (default: "local", or the project's only environment)
+      --overwrite            Push even over changes made on the site outside Loopress since your last push
 
 GLOBAL FLAGS
   --json  Format output as json.
@@ -947,7 +1235,7 @@ EXAMPLES
   $ lps form push --allow-notifications
 ```
 
-_See code: [src/commands/form/push.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.29.0/cli/src/commands/form/push.ts)_
+_See code: [src/commands/form/push.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.31.0/cli/src/commands/form/push.ts)_
 
 ## `lps form rollback [PATH]`
 
@@ -963,7 +1251,7 @@ ARGUMENTS
 FLAGS
   -d, --dry-run      Show what would change without making changes
   -y, --yes          Answer yes to confirmation prompts
-      --env=<value>  Target environment by name, overriding the globally active one (lps project switch)
+      --env=<value>  Target environment by name (default: "local", or the project's only environment)
       --list         List available snapshots instead of rolling back
       --to=<value>   Roll back to this snapshot id instead of the most recent one
 
@@ -983,7 +1271,7 @@ EXAMPLES
   $ lps form rollback --dry-run
 ```
 
-_See code: [src/commands/form/rollback.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.29.0/cli/src/commands/form/rollback.ts)_
+_See code: [src/commands/form/rollback.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.31.0/cli/src/commands/form/rollback.ts)_
 
 ## `lps help [COMMAND]`
 
@@ -1003,7 +1291,7 @@ DESCRIPTION
   Display help for lps.
 ```
 
-_See code: [@oclif/plugin-help](https://github.com/oclif/plugin-help/blob/7.0.2/src/commands/help.ts)_
+_See code: [@oclif/plugin-help](https://github.com/oclif/plugin-help/blob/7.0.4/src/commands/help.ts)_
 
 ## `lps hook diff [PATH]`
 
@@ -1018,7 +1306,7 @@ ARGUMENTS
 
 FLAGS
   --against=<value>  Compare the primary environment against this second environment instead of against local files
-  --env=<value>      Target environment by name, overriding the globally active one (lps project switch)
+  --env=<value>      Target environment by name (default: "local", or the project's only environment)
 
 GLOBAL FLAGS
   --json  Format output as json.
@@ -1034,7 +1322,7 @@ EXAMPLES
   $ lps hook diff --env staging --against production
 ```
 
-_See code: [src/commands/hook/diff.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.29.0/cli/src/commands/hook/diff.ts)_
+_See code: [src/commands/hook/diff.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.31.0/cli/src/commands/hook/diff.ts)_
 
 ## `lps hook list`
 
@@ -1045,7 +1333,7 @@ USAGE
   $ lps hook list [--json] [--env <value>]
 
 FLAGS
-  --env=<value>  Target environment by name, overriding the globally active one (lps project switch)
+  --env=<value>  Target environment by name (default: "local", or the project's only environment)
 
 GLOBAL FLAGS
   --json  Format output as json.
@@ -1057,7 +1345,7 @@ EXAMPLES
   $ lps hook list
 ```
 
-_See code: [src/commands/hook/list.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.29.0/cli/src/commands/hook/list.ts)_
+_See code: [src/commands/hook/list.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.31.0/cli/src/commands/hook/list.ts)_
 
 ## `lps hook pull [PATH]`
 
@@ -1073,7 +1361,7 @@ ARGUMENTS
 FLAGS
   -d, --dry-run      Show what would change without making changes
   -y, --yes          Answer yes to confirmation prompts
-      --env=<value>  Target environment by name, overriding the globally active one (lps project switch)
+      --env=<value>  Target environment by name (default: "local", or the project's only environment)
 
 GLOBAL FLAGS
   --json  Format output as json.
@@ -1087,7 +1375,7 @@ EXAMPLES
   $ lps hook pull --path ./hooks
 ```
 
-_See code: [src/commands/hook/pull.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.29.0/cli/src/commands/hook/pull.ts)_
+_See code: [src/commands/hook/pull.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.31.0/cli/src/commands/hook/pull.ts)_
 
 ## `lps hook push [PATH]`
 
@@ -1095,7 +1383,7 @@ Push hook files (actions, filters, cron) to WordPress
 
 ```
 USAGE
-  $ lps hook push [PATH] [--json] [--env <value>] [-d] [-y] [--prune]
+  $ lps hook push [PATH] [--json] [--env <value>] [--overwrite] [-d] [-y] [--prune]
 
 ARGUMENTS
   [PATH]  Path to hooks directory (overrides project config)
@@ -1103,7 +1391,8 @@ ARGUMENTS
 FLAGS
   -d, --dry-run      Show what would change without making changes
   -y, --yes          Answer yes to confirmation prompts
-      --env=<value>  Target environment by name, overriding the globally active one (lps project switch)
+      --env=<value>  Target environment by name (default: "local", or the project's only environment)
+      --overwrite    Push even over changes made on the site outside Loopress since your last push
       --prune        Delete server-side hook files not present locally after pushing
 
 GLOBAL FLAGS
@@ -1120,7 +1409,7 @@ EXAMPLES
   $ lps hook push --prune
 ```
 
-_See code: [src/commands/hook/push.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.29.0/cli/src/commands/hook/push.ts)_
+_See code: [src/commands/hook/push.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.31.0/cli/src/commands/hook/push.ts)_
 
 ## `lps hook remove FILENAME`
 
@@ -1136,7 +1425,7 @@ ARGUMENTS
 FLAGS
   -d, --dry-run      Show what would change without making changes
   -y, --yes          Answer yes to confirmation prompts
-      --env=<value>  Target environment by name, overriding the globally active one (lps project switch)
+      --env=<value>  Target environment by name (default: "local", or the project's only environment)
 
 GLOBAL FLAGS
   --json  Format output as json.
@@ -1167,7 +1456,7 @@ ARGUMENTS
 FLAGS
   -d, --dry-run      Show what would change without making changes
   -y, --yes          Answer yes to confirmation prompts
-      --env=<value>  Target environment by name, overriding the globally active one (lps project switch)
+      --env=<value>  Target environment by name (default: "local", or the project's only environment)
 
 GLOBAL FLAGS
   --json  Format output as json.
@@ -1184,7 +1473,7 @@ EXAMPLES
   $ lps hook remove hello --yes
 ```
 
-_See code: [src/commands/hook/rm.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.29.0/cli/src/commands/hook/rm.ts)_
+_See code: [src/commands/hook/rm.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.31.0/cli/src/commands/hook/rm.ts)_
 
 ## `lps hook rollback [PATH]`
 
@@ -1200,7 +1489,7 @@ ARGUMENTS
 FLAGS
   -d, --dry-run      Show what would change without making changes
   -y, --yes          Answer yes to confirmation prompts
-      --env=<value>  Target environment by name, overriding the globally active one (lps project switch)
+      --env=<value>  Target environment by name (default: "local", or the project's only environment)
       --list         List available snapshots instead of rolling back
       --to=<value>   Roll back to this snapshot id instead of the most recent one
 
@@ -1220,7 +1509,7 @@ EXAMPLES
   $ lps hook rollback --dry-run
 ```
 
-_See code: [src/commands/hook/rollback.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.29.0/cli/src/commands/hook/rollback.ts)_
+_See code: [src/commands/hook/rollback.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.31.0/cli/src/commands/hook/rollback.ts)_
 
 ## `lps init`
 
@@ -1237,7 +1526,7 @@ EXAMPLES
   $ lps init
 ```
 
-_See code: [src/commands/init.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.29.0/cli/src/commands/init.ts)_
+_See code: [src/commands/init.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.31.0/cli/src/commands/init.ts)_
 
 ## `lps login`
 
@@ -1254,7 +1543,7 @@ EXAMPLES
   $ lps login
 ```
 
-_See code: [src/commands/login.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.29.0/cli/src/commands/login.ts)_
+_See code: [src/commands/login.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.31.0/cli/src/commands/login.ts)_
 
 ## `lps logout`
 
@@ -1271,7 +1560,7 @@ EXAMPLES
   $ lps logout
 ```
 
-_See code: [src/commands/logout.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.29.0/cli/src/commands/logout.ts)_
+_See code: [src/commands/logout.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.31.0/cli/src/commands/logout.ts)_
 
 ## `lps menu diff [PATH]`
 
@@ -1286,7 +1575,7 @@ ARGUMENTS
 
 FLAGS
   --against=<value>  Compare the primary environment against this second environment instead of against local files
-  --env=<value>      Target environment by name, overriding the globally active one (lps project switch)
+  --env=<value>      Target environment by name (default: "local", or the project's only environment)
 
 GLOBAL FLAGS
   --json  Format output as json.
@@ -1303,7 +1592,7 @@ EXAMPLES
   $ lps menu diff --env staging --against production
 ```
 
-_See code: [src/commands/menu/diff.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.29.0/cli/src/commands/menu/diff.ts)_
+_See code: [src/commands/menu/diff.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.31.0/cli/src/commands/menu/diff.ts)_
 
 ## `lps menu list`
 
@@ -1314,7 +1603,7 @@ USAGE
   $ lps menu list [--json] [--env <value>]
 
 FLAGS
-  --env=<value>  Target environment by name, overriding the globally active one (lps project switch)
+  --env=<value>  Target environment by name (default: "local", or the project's only environment)
 
 GLOBAL FLAGS
   --json  Format output as json.
@@ -1326,7 +1615,7 @@ EXAMPLES
   $ lps menu list
 ```
 
-_See code: [src/commands/menu/list.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.29.0/cli/src/commands/menu/list.ts)_
+_See code: [src/commands/menu/list.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.31.0/cli/src/commands/menu/list.ts)_
 
 ## `lps menu pull [PATH]`
 
@@ -1342,7 +1631,7 @@ ARGUMENTS
 FLAGS
   -d, --dry-run      Show what would change without making changes
   -y, --yes          Answer yes to confirmation prompts
-      --env=<value>  Target environment by name, overriding the globally active one (lps project switch)
+      --env=<value>  Target environment by name (default: "local", or the project's only environment)
 
 GLOBAL FLAGS
   --json  Format output as json.
@@ -1354,7 +1643,7 @@ EXAMPLES
   $ lps menu pull
 ```
 
-_See code: [src/commands/menu/pull.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.29.0/cli/src/commands/menu/pull.ts)_
+_See code: [src/commands/menu/pull.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.31.0/cli/src/commands/menu/pull.ts)_
 
 ## `lps menu push [PATH]`
 
@@ -1362,7 +1651,7 @@ Push local nav menus and the active theme menu locations to WordPress. Each menu
 
 ```
 USAGE
-  $ lps menu push [PATH] [--json] [--env <value>] [-d] [-y]
+  $ lps menu push [PATH] [--json] [--env <value>] [--overwrite] [-d] [-y]
 
 ARGUMENTS
   [PATH]  Path to menus directory (overrides project config)
@@ -1370,7 +1659,8 @@ ARGUMENTS
 FLAGS
   -d, --dry-run      Show what would change without making changes
   -y, --yes          Answer yes to confirmation prompts
-      --env=<value>  Target environment by name, overriding the globally active one (lps project switch)
+      --env=<value>  Target environment by name (default: "local", or the project's only environment)
+      --overwrite    Push even over changes made on the site outside Loopress since your last push
 
 GLOBAL FLAGS
   --json  Format output as json.
@@ -1384,7 +1674,7 @@ EXAMPLES
   $ lps menu push
 ```
 
-_See code: [src/commands/menu/push.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.29.0/cli/src/commands/menu/push.ts)_
+_See code: [src/commands/menu/push.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.31.0/cli/src/commands/menu/push.ts)_
 
 ## `lps menu rollback [PATH]`
 
@@ -1400,7 +1690,7 @@ ARGUMENTS
 FLAGS
   -d, --dry-run      Show what would change without making changes
   -y, --yes          Answer yes to confirmation prompts
-      --env=<value>  Target environment by name, overriding the globally active one (lps project switch)
+      --env=<value>  Target environment by name (default: "local", or the project's only environment)
       --list         List available snapshots instead of rolling back
       --to=<value>   Roll back to this snapshot id instead of the most recent one
 
@@ -1420,207 +1710,204 @@ EXAMPLES
   $ lps menu rollback --dry-run
 ```
 
-_See code: [src/commands/menu/rollback.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.29.0/cli/src/commands/menu/rollback.ts)_
+_See code: [src/commands/menu/rollback.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.31.0/cli/src/commands/menu/rollback.ts)_
 
-## `lps option add NAME`
+## `lps meta diff [PATH]`
 
-Fetch a WordPress option by name and start tracking it locally. Run `lps option list` first to find the name: this copies a raw value across environments, verify it does not embed post/user IDs before pushing it elsewhere.
+Show what differs in post meta keys between your local meta/ files and a WordPress environment, or between two environments
 
 ```
 USAGE
-  $ lps option add NAME [--json] [--env <value>] [-d] [--path <value>]
+  $ lps meta diff [PATH] [--json] [--env <value>] [--against <value>]
 
 ARGUMENTS
-  NAME  Option name to start tracking (see `lps option list`)
+  [PATH]  Path to meta directory (overrides project config)
 
 FLAGS
-  -d, --dry-run       Show what would change without making changes
-      --env=<value>   Target environment by name, overriding the globally active one (lps project switch)
-      --path=<value>  Path to options directory (overrides project config)
+  --against=<value>  Compare the primary environment against this second environment instead of against local files
+  --env=<value>      Target environment by name (default: "local", or the project's only environment)
 
 GLOBAL FLAGS
   --json  Format output as json.
 
 DESCRIPTION
-  Fetch a WordPress option by name and start tracking it locally. Run `lps option list` first to find the name: this
-  copies a raw value across environments, verify it does not embed post/user IDs before pushing it elsewhere.
+  Show what differs in post meta keys between your local meta/ files and a WordPress environment, or between two
+  environments
 
 EXAMPLES
-  $ lps option add wpseo_titles
+  $ lps meta diff
 
-  $ lps option add siteurl
+  $ lps meta diff --env staging
+
+  $ lps meta diff --env staging --against production
 ```
 
-_See code: [src/commands/option/add.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.29.0/cli/src/commands/option/add.ts)_
+_See code: [src/commands/meta/diff.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.31.0/cli/src/commands/meta/diff.ts)_
 
-## `lps option diff [PATH]`
+## `lps meta list`
 
-Show what differs, for locally tracked options, between your local files and a WordPress environment, or between two environments
+List the meta keys registered for each post type on WordPress (with register_post_meta()), and whether Loopress declares them. Only Loopress ones are pulled and pushed.
 
 ```
 USAGE
-  $ lps option diff [PATH] [--json] [--env <value>] [--against <value>]
-
-ARGUMENTS
-  [PATH]  Path to options directory (overrides project config)
+  $ lps meta list [--json] [--env <value>]
 
 FLAGS
-  --against=<value>  Compare the primary environment against this second environment instead of against local files
-  --env=<value>      Target environment by name, overriding the globally active one (lps project switch)
+  --env=<value>  Target environment by name (default: "local", or the project's only environment)
 
 GLOBAL FLAGS
   --json  Format output as json.
 
 DESCRIPTION
-  Show what differs, for locally tracked options, between your local files and a WordPress environment, or between two
-  environments
+  List the meta keys registered for each post type on WordPress (with register_post_meta()), and whether Loopress
+  declares them. Only Loopress ones are pulled and pushed.
 
 EXAMPLES
-  $ lps option diff
-
-  $ lps option diff --env staging
-
-  $ lps option diff --env staging --against production
+  $ lps meta list
 ```
 
-_See code: [src/commands/option/diff.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.29.0/cli/src/commands/option/diff.ts)_
+_See code: [src/commands/meta/list.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.31.0/cli/src/commands/meta/list.ts)_
 
-## `lps option list`
+## `lps meta pull [PATH]`
 
-List WordPress option names currently on the site (names and autoload only, never values). CORE flags a WordPress-native default (certain); SOURCE? is a best-effort guessed plugin slug, found by name or by scanning active plugins' own PHP source (uncertain unless confirmed, occasionally wrong or blank, never trust it over CORE); PLUGIN is that slug's own declared display name, a label only, no confidence of its own. Use this to find the name of the option you want, then `lps option add <name>` to track it.
+Pull the post meta keys Loopress manages on WordPress into meta/<post-type>.json files, never their values. Keys registered by a theme or another plugin are never pulled, see `lps meta list`.
 
 ```
 USAGE
-  $ lps option list [--json] [--env <value>] [--no-core]
+  $ lps meta pull [PATH] [--json] [--env <value>] [-d] [-y]
+
+ARGUMENTS
+  [PATH]  Path to the meta directory (overrides project config)
 
 FLAGS
-  --env=<value>  Target environment by name, overriding the globally active one (lps project switch)
-  --no-core      Exclude WordPress-native default options and the CORE column from the output, including --json
+  -d, --dry-run      Show what would change without making changes
+  -y, --yes          Answer yes to confirmation prompts
+      --env=<value>  Target environment by name (default: "local", or the project's only environment)
 
 GLOBAL FLAGS
   --json  Format output as json.
 
 DESCRIPTION
-  List WordPress option names currently on the site (names and autoload only, never values). CORE flags a
-  WordPress-native default (certain); SOURCE? is a best-effort guessed plugin slug, found by name or by scanning active
-  plugins' own PHP source (uncertain unless confirmed, occasionally wrong or blank, never trust it over CORE); PLUGIN is
-  that slug's own declared display name, a label only, no confidence of its own. Use this to find the name of the option
-  you want, then `lps option add <name>` to track it.
+  Pull the post meta keys Loopress manages on WordPress into meta/<post-type>.json files, never their values. Keys
+  registered by a theme or another plugin are never pulled, see `lps meta list`.
 
 EXAMPLES
-  $ lps option list
-
-  $ lps option list --no-core
+  $ lps meta pull
 ```
 
-_See code: [src/commands/option/list.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.29.0/cli/src/commands/option/list.ts)_
+_See code: [src/commands/meta/pull.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.31.0/cli/src/commands/meta/pull.ts)_
 
-## `lps option pull [PATH]`
+## `lps meta push [PATH]`
 
-Refresh locally tracked options from WordPress. Options not yet tracked are never pulled, run `lps option add <name>` for those first.
+Push local post meta keys (meta/<post-type>.json, each key mapped to its register_post_meta() arguments) to WordPress. Create or update only, never deletes (use `lps meta rm`), never touches meta values.
 
 ```
 USAGE
-  $ lps option pull [PATH] [--json] [--env <value>] [-d] [-y]
+  $ lps meta push [PATH] [--json] [--env <value>] [--overwrite] [-d] [-y]
 
 ARGUMENTS
-  [PATH]  Path to options directory (overrides project config)
+  [PATH]  Path to the meta directory (overrides project config)
 
 FLAGS
   -d, --dry-run      Show what would change without making changes
   -y, --yes          Answer yes to confirmation prompts
-      --env=<value>  Target environment by name, overriding the globally active one (lps project switch)
+      --env=<value>  Target environment by name (default: "local", or the project's only environment)
+      --overwrite    Push even over changes made on the site outside Loopress since your last push
 
 GLOBAL FLAGS
   --json  Format output as json.
 
 DESCRIPTION
-  Refresh locally tracked options from WordPress. Options not yet tracked are never pulled, run `lps option add <name>`
-  for those first.
+  Push local post meta keys (meta/<post-type>.json, each key mapped to its register_post_meta() arguments) to WordPress.
+  Create or update only, never deletes (use `lps meta rm`), never touches meta values.
 
 EXAMPLES
-  $ lps option pull
+  $ lps meta push
 ```
 
-_See code: [src/commands/option/pull.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.29.0/cli/src/commands/option/pull.ts)_
+_See code: [src/commands/meta/push.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.31.0/cli/src/commands/meta/push.ts)_
 
-## `lps option push [PATH]`
+## `lps meta remove SLUG`
 
-Push locally tracked, non-readonly options to WordPress (upsert only, never deletes an untracked option). Options marked "readonly": true in their local file are skipped, edit the file to override.
+Stop registering the Loopress meta keys of one post type (its meta/<post-type>.json file) on WordPress. Their values are kept in the database.
 
 ```
 USAGE
-  $ lps option push [PATH] [--json] [--env <value>] [-d] [-y]
+  $ lps meta remove SLUG [--json] [--env <value>] [-d] [-y]
 
 ARGUMENTS
-  [PATH]  Path to options directory (overrides project config)
+  SLUG  The post meta slug, its meta/ file name without .json
 
 FLAGS
   -d, --dry-run      Show what would change without making changes
   -y, --yes          Answer yes to confirmation prompts
-      --env=<value>  Target environment by name, overriding the globally active one (lps project switch)
+      --env=<value>  Target environment by name (default: "local", or the project's only environment)
 
 GLOBAL FLAGS
   --json  Format output as json.
 
 DESCRIPTION
-  Push locally tracked, non-readonly options to WordPress (upsert only, never deletes an untracked option). Options
-  marked "readonly": true in their local file are skipped, edit the file to override.
+  Stop registering the Loopress meta keys of one post type (its meta/<post-type>.json file) on WordPress. Their values
+  are kept in the database.
+
+ALIASES
+  $ lps meta remove
 
 EXAMPLES
-  $ lps option push
-```
+  $ lps meta rm <slug>
 
-_See code: [src/commands/option/push.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.29.0/cli/src/commands/option/push.ts)_
+  $ lps meta remove <slug> --yes
+```
 
-## `lps option remove NAME`
+## `lps meta rm SLUG`
 
-Stop tracking an option locally and delete it from WordPress. Local untracking always happens (git-reversible); pass --local-only to skip the WordPress delete and only stop tracking.
+Stop registering the Loopress meta keys of one post type (its meta/<post-type>.json file) on WordPress. Their values are kept in the database.
 
 ```
 USAGE
-  $ lps option remove NAME [--json] [--env <value>] [-d] [-y] [--local-only] [--path <value>]
+  $ lps meta rm SLUG [--json] [--env <value>] [-d] [-y]
 
 ARGUMENTS
-  NAME  Option name to stop tracking
+  SLUG  The post meta slug, its meta/ file name without .json
 
 FLAGS
-  -d, --dry-run       Show what would change without making changes
-  -y, --yes           Answer yes to confirmation prompts
-      --env=<value>   Target environment by name, overriding the globally active one (lps project switch)
-      --local-only    Untrack locally without deleting the option on WordPress
-      --path=<value>  Path to options directory (overrides project config)
+  -d, --dry-run      Show what would change without making changes
+  -y, --yes          Answer yes to confirmation prompts
+      --env=<value>  Target environment by name (default: "local", or the project's only environment)
 
 GLOBAL FLAGS
   --json  Format output as json.
 
 DESCRIPTION
-  Stop tracking an option locally and delete it from WordPress. Local untracking always happens (git-reversible); pass
-  --local-only to skip the WordPress delete and only stop tracking.
+  Stop registering the Loopress meta keys of one post type (its meta/<post-type>.json file) on WordPress. Their values
+  are kept in the database.
+
+ALIASES
+  $ lps meta remove
 
 EXAMPLES
-  $ lps option remove wpseo_titles
+  $ lps meta rm <slug>
 
-  $ lps option remove wpseo_titles --local-only
+  $ lps meta remove <slug> --yes
 ```
 
-_See code: [src/commands/option/remove.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.29.0/cli/src/commands/option/remove.ts)_
+_See code: [src/commands/meta/rm.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.31.0/cli/src/commands/meta/rm.ts)_
 
-## `lps option rollback [PATH]`
+## `lps meta rollback [PATH]`
 
-Restore tracked options to a snapshot taken automatically before an earlier `lps option push`
+Restore post meta keys to a snapshot taken automatically before an earlier `lps meta push`
 
 ```
 USAGE
-  $ lps option rollback [PATH] [--json] [--env <value>] [-d] [-y] [--list] [--to <value>]
+  $ lps meta rollback [PATH] [--json] [--env <value>] [-d] [-y] [--list] [--to <value>]
 
 ARGUMENTS
-  [PATH]  Path to options directory (overrides project config)
+  [PATH]  Path to meta directory (overrides project config)
 
 FLAGS
   -d, --dry-run      Show what would change without making changes
   -y, --yes          Answer yes to confirmation prompts
-      --env=<value>  Target environment by name, overriding the globally active one (lps project switch)
+      --env=<value>  Target environment by name (default: "local", or the project's only environment)
       --list         List available snapshots instead of rolling back
       --to=<value>   Roll back to this snapshot id instead of the most recent one
 
@@ -1628,106 +1915,545 @@ GLOBAL FLAGS
   --json  Format output as json.
 
 DESCRIPTION
-  Restore tracked options to a snapshot taken automatically before an earlier `lps option push`
+  Restore post meta keys to a snapshot taken automatically before an earlier `lps meta push`
 
 EXAMPLES
-  $ lps option rollback
+  $ lps meta rollback
 
-  $ lps option rollback --list
+  $ lps meta rollback --list
 
-  $ lps option rollback --to 1732000000000
+  $ lps meta rollback --to 1732000000000
 
-  $ lps option rollback --dry-run
+  $ lps meta rollback --dry-run
 ```
 
-_See code: [src/commands/option/rollback.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.29.0/cli/src/commands/option/rollback.ts)_
+_See code: [src/commands/meta/rollback.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.31.0/cli/src/commands/meta/rollback.ts)_
 
-## `lps page diff [PATH]`
+## `lps option add NAME`
+
+Fetch a WordPress option by name and start tracking it locally. Run `lps option list` first to find the name: this copies a raw value across environments, verify it does not embed post/user IDs before pushing it elsewhere.
+
+```
+USAGE
+  $ lps option add NAME [--json] [--env <value>] [-d] [--path <value>]
+
+ARGUMENTS
+  NAME  Option name to start tracking (see `lps option list`)
+
+FLAGS
+  -d, --dry-run       Show what would change without making changes
+      --env=<value>   Target environment by name (default: "local", or the project's only environment)
+      --path=<value>  Path to options directory (overrides project config)
+
+GLOBAL FLAGS
+  --json  Format output as json.
+
+DESCRIPTION
+  Fetch a WordPress option by name and start tracking it locally. Run `lps option list` first to find the name: this
+  copies a raw value across environments, verify it does not embed post/user IDs before pushing it elsewhere.
+
+EXAMPLES
+  $ lps option add wpseo_titles
+
+  $ lps option add siteurl
+```
+
+_See code: [src/commands/option/add.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.31.0/cli/src/commands/option/add.ts)_
+
+## `lps option diff [PATH]`
+
+Show what differs, for locally tracked options, between your local files and a WordPress environment, or between two environments
+
+```
+USAGE
+  $ lps option diff [PATH] [--json] [--env <value>] [--against <value>]
+
+ARGUMENTS
+  [PATH]  Path to options directory (overrides project config)
+
+FLAGS
+  --against=<value>  Compare the primary environment against this second environment instead of against local files
+  --env=<value>      Target environment by name (default: "local", or the project's only environment)
+
+GLOBAL FLAGS
+  --json  Format output as json.
+
+DESCRIPTION
+  Show what differs, for locally tracked options, between your local files and a WordPress environment, or between two
+  environments
+
+EXAMPLES
+  $ lps option diff
+
+  $ lps option diff --env staging
+
+  $ lps option diff --env staging --against production
+```
+
+_See code: [src/commands/option/diff.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.31.0/cli/src/commands/option/diff.ts)_
+
+## `lps option list`
+
+List WordPress option names currently on the site (names and autoload only, never values). CORE flags a WordPress-native default (certain); SOURCE? is a best-effort guessed plugin slug, found by name or by scanning active plugins' own PHP source (uncertain unless confirmed, occasionally wrong or blank, never trust it over CORE); PLUGIN is that slug's own declared display name, a label only, no confidence of its own. Use this to find the name of the option you want, then `lps option add <name>` to track it.
+
+```
+USAGE
+  $ lps option list [--json] [--env <value>] [--no-core]
+
+FLAGS
+  --env=<value>  Target environment by name (default: "local", or the project's only environment)
+  --no-core      Exclude WordPress-native default options and the CORE column from the output, including --json
+
+GLOBAL FLAGS
+  --json  Format output as json.
+
+DESCRIPTION
+  List WordPress option names currently on the site (names and autoload only, never values). CORE flags a
+  WordPress-native default (certain); SOURCE? is a best-effort guessed plugin slug, found by name or by scanning active
+  plugins' own PHP source (uncertain unless confirmed, occasionally wrong or blank, never trust it over CORE); PLUGIN is
+  that slug's own declared display name, a label only, no confidence of its own. Use this to find the name of the option
+  you want, then `lps option add <name>` to track it.
+
+EXAMPLES
+  $ lps option list
+
+  $ lps option list --no-core
+```
+
+_See code: [src/commands/option/list.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.31.0/cli/src/commands/option/list.ts)_
+
+## `lps option pull [PATH]`
+
+Refresh locally tracked options from WordPress. Options not yet tracked are never pulled, run `lps option add <name>` for those first.
+
+```
+USAGE
+  $ lps option pull [PATH] [--json] [--env <value>] [-d] [-y]
+
+ARGUMENTS
+  [PATH]  Path to options directory (overrides project config)
+
+FLAGS
+  -d, --dry-run      Show what would change without making changes
+  -y, --yes          Answer yes to confirmation prompts
+      --env=<value>  Target environment by name (default: "local", or the project's only environment)
+
+GLOBAL FLAGS
+  --json  Format output as json.
+
+DESCRIPTION
+  Refresh locally tracked options from WordPress. Options not yet tracked are never pulled, run `lps option add <name>`
+  for those first.
+
+EXAMPLES
+  $ lps option pull
+```
+
+_See code: [src/commands/option/pull.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.31.0/cli/src/commands/option/pull.ts)_
+
+## `lps option push [PATH]`
+
+Push locally tracked, non-readonly options to WordPress (upsert only, never deletes an untracked option). Options marked "readonly": true in their local file are skipped, edit the file to override.
+
+```
+USAGE
+  $ lps option push [PATH] [--json] [--env <value>] [--overwrite] [-d] [-y]
+
+ARGUMENTS
+  [PATH]  Path to options directory (overrides project config)
+
+FLAGS
+  -d, --dry-run      Show what would change without making changes
+  -y, --yes          Answer yes to confirmation prompts
+      --env=<value>  Target environment by name (default: "local", or the project's only environment)
+      --overwrite    Push even over changes made on the site outside Loopress since your last push
+
+GLOBAL FLAGS
+  --json  Format output as json.
+
+DESCRIPTION
+  Push locally tracked, non-readonly options to WordPress (upsert only, never deletes an untracked option). Options
+  marked "readonly": true in their local file are skipped, edit the file to override.
+
+EXAMPLES
+  $ lps option push
+```
+
+_See code: [src/commands/option/push.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.31.0/cli/src/commands/option/push.ts)_
+
+## `lps option remove NAME`
+
+Stop tracking an option locally and delete it from WordPress. Local untracking always happens (git-reversible); pass --local-only to skip the WordPress delete and only stop tracking.
+
+```
+USAGE
+  $ lps option remove NAME [--json] [--env <value>] [-d] [-y] [--local-only] [--path <value>]
+
+ARGUMENTS
+  NAME  Option name to stop tracking
+
+FLAGS
+  -d, --dry-run       Show what would change without making changes
+  -y, --yes           Answer yes to confirmation prompts
+      --env=<value>   Target environment by name (default: "local", or the project's only environment)
+      --local-only    Untrack locally without deleting the option on WordPress
+      --path=<value>  Path to options directory (overrides project config)
+
+GLOBAL FLAGS
+  --json  Format output as json.
+
+DESCRIPTION
+  Stop tracking an option locally and delete it from WordPress. Local untracking always happens (git-reversible); pass
+  --local-only to skip the WordPress delete and only stop tracking.
+
+EXAMPLES
+  $ lps option remove wpseo_titles
+
+  $ lps option remove wpseo_titles --local-only
+```
+
+_See code: [src/commands/option/remove.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.31.0/cli/src/commands/option/remove.ts)_
+
+## `lps option rollback [PATH]`
+
+Restore tracked options to a snapshot taken automatically before an earlier `lps option push`
+
+```
+USAGE
+  $ lps option rollback [PATH] [--json] [--env <value>] [-d] [-y] [--list] [--to <value>]
+
+ARGUMENTS
+  [PATH]  Path to options directory (overrides project config)
+
+FLAGS
+  -d, --dry-run      Show what would change without making changes
+  -y, --yes          Answer yes to confirmation prompts
+      --env=<value>  Target environment by name (default: "local", or the project's only environment)
+      --list         List available snapshots instead of rolling back
+      --to=<value>   Roll back to this snapshot id instead of the most recent one
+
+GLOBAL FLAGS
+  --json  Format output as json.
+
+DESCRIPTION
+  Restore tracked options to a snapshot taken automatically before an earlier `lps option push`
+
+EXAMPLES
+  $ lps option rollback
+
+  $ lps option rollback --list
+
+  $ lps option rollback --to 1732000000000
+
+  $ lps option rollback --dry-run
+```
+
+_See code: [src/commands/option/rollback.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.31.0/cli/src/commands/option/rollback.ts)_
+
+## `lps page diff [PATH]`
 
 Show what differs in static pages between your local files and a WordPress environment, or between two environments
 
 ```
 USAGE
-  $ lps page diff [PATH] [--json] [--env <value>] [--against <value>]
+  $ lps page diff [PATH] [--json] [--env <value>] [--against <value>]
+
+ARGUMENTS
+  [PATH]  Path to pages directory (overrides project config)
+
+FLAGS
+  --against=<value>  Compare the primary environment against this second environment instead of against local files
+  --env=<value>      Target environment by name (default: "local", or the project's only environment)
+
+GLOBAL FLAGS
+  --json  Format output as json.
+
+DESCRIPTION
+  Show what differs in static pages between your local files and a WordPress environment, or between two environments
+
+EXAMPLES
+  $ lps page diff
+
+  $ lps page diff --env staging
+
+  $ lps page diff --env staging --against production
+```
+
+_See code: [src/commands/page/diff.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.31.0/cli/src/commands/page/diff.ts)_
+
+## `lps page list`
+
+List the static pages managed by Loopress on WordPress
+
+```
+USAGE
+  $ lps page list [--json] [--env <value>]
+
+FLAGS
+  --env=<value>  Target environment by name (default: "local", or the project's only environment)
+
+GLOBAL FLAGS
+  --json  Format output as json.
+
+DESCRIPTION
+  List the static pages managed by Loopress on WordPress
+
+EXAMPLES
+  $ lps page list
+```
+
+_See code: [src/commands/page/list.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.31.0/cli/src/commands/page/list.ts)_
+
+## `lps page push [SLUG]`
+
+Push static HTML pages (pages/<slug>.html) to WordPress. The `status` header (draft or publish, draft by default) is applied on every push.
+
+```
+USAGE
+  $ lps page push [SLUG] [--json] [--env <value>] [--overwrite] [-d] [-y]
+
+ARGUMENTS
+  [SLUG]  Push only this page (its file name without .html). Pushes every page when omitted.
+
+FLAGS
+  -d, --dry-run      Show what would change without making changes
+  -y, --yes          Answer yes to confirmation prompts
+      --env=<value>  Target environment by name (default: "local", or the project's only environment)
+      --overwrite    Push even over changes made on the site outside Loopress since your last push
+
+GLOBAL FLAGS
+  --json  Format output as json.
+
+DESCRIPTION
+  Push static HTML pages (pages/<slug>.html) to WordPress. The `status` header (draft or publish, draft by default) is
+  applied on every push.
+
+EXAMPLES
+  $ lps page push
+
+  $ lps page push legal-notice
+
+  $ lps page push --dry-run
+```
+
+_See code: [src/commands/page/push.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.31.0/cli/src/commands/page/push.ts)_
+
+## `lps pattern diff [PATH]`
+
+Show what differs in block patterns between your local patterns/ files and a WordPress environment, or between two environments
+
+```
+USAGE
+  $ lps pattern diff [PATH] [--json] [--env <value>] [--against <value>]
+
+ARGUMENTS
+  [PATH]  Path to patterns directory (overrides project config)
+
+FLAGS
+  --against=<value>  Compare the primary environment against this second environment instead of against local files
+  --env=<value>      Target environment by name (default: "local", or the project's only environment)
+
+GLOBAL FLAGS
+  --json  Format output as json.
+
+DESCRIPTION
+  Show what differs in block patterns between your local patterns/ files and a WordPress environment, or between two
+  environments
+
+EXAMPLES
+  $ lps pattern diff
+
+  $ lps pattern diff --env staging
+
+  $ lps pattern diff --env staging --against production
+```
+
+_See code: [src/commands/pattern/diff.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.31.0/cli/src/commands/pattern/diff.ts)_
+
+## `lps pattern list`
+
+List the block patterns registered on WordPress by Loopress, the theme and plugins (not WordPress core). Only Loopress ones are pulled and pushed.
+
+```
+USAGE
+  $ lps pattern list [--json] [--env <value>]
+
+FLAGS
+  --env=<value>  Target environment by name (default: "local", or the project's only environment)
+
+GLOBAL FLAGS
+  --json  Format output as json.
+
+DESCRIPTION
+  List the block patterns registered on WordPress by Loopress, the theme and plugins (not WordPress core). Only Loopress
+  ones are pulled and pushed.
+
+EXAMPLES
+  $ lps pattern list
+```
+
+_See code: [src/commands/pattern/list.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.31.0/cli/src/commands/pattern/list.ts)_
+
+## `lps pattern pull [PATH]`
+
+Pull the block patterns Loopress manages on WordPress into patterns/<slug>.html files. Patterns registered by the theme or a plugin are never pulled, see `lps pattern list`.
+
+```
+USAGE
+  $ lps pattern pull [PATH] [--json] [--env <value>] [-d] [-y]
+
+ARGUMENTS
+  [PATH]  Path to the patterns directory (overrides project config)
+
+FLAGS
+  -d, --dry-run      Show what would change without making changes
+  -y, --yes          Answer yes to confirmation prompts
+      --env=<value>  Target environment by name (default: "local", or the project's only environment)
+
+GLOBAL FLAGS
+  --json  Format output as json.
+
+DESCRIPTION
+  Pull the block patterns Loopress manages on WordPress into patterns/<slug>.html files. Patterns registered by the
+  theme or a plugin are never pulled, see `lps pattern list`.
+
+EXAMPLES
+  $ lps pattern pull
+```
+
+_See code: [src/commands/pattern/pull.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.31.0/cli/src/commands/pattern/pull.ts)_
+
+## `lps pattern push [PATH]`
+
+Push local block patterns (patterns/<slug>.html, block markup under a title/categories header) to WordPress, registered as loopress/<slug>. Create or update only, never deletes a pattern (use `lps pattern rm`).
+
+```
+USAGE
+  $ lps pattern push [PATH] [--json] [--env <value>] [--overwrite] [-d] [-y]
 
 ARGUMENTS
-  [PATH]  Path to pages directory (overrides project config)
+  [PATH]  Path to the patterns directory (overrides project config)
 
 FLAGS
-  --against=<value>  Compare the primary environment against this second environment instead of against local files
-  --env=<value>      Target environment by name, overriding the globally active one (lps project switch)
+  -d, --dry-run      Show what would change without making changes
+  -y, --yes          Answer yes to confirmation prompts
+      --env=<value>  Target environment by name (default: "local", or the project's only environment)
+      --overwrite    Push even over changes made on the site outside Loopress since your last push
 
 GLOBAL FLAGS
   --json  Format output as json.
 
 DESCRIPTION
-  Show what differs in static pages between your local files and a WordPress environment, or between two environments
+  Push local block patterns (patterns/<slug>.html, block markup under a title/categories header) to WordPress,
+  registered as loopress/<slug>. Create or update only, never deletes a pattern (use `lps pattern rm`).
 
 EXAMPLES
-  $ lps page diff
+  $ lps pattern push
+```
 
-  $ lps page diff --env staging
+_See code: [src/commands/pattern/push.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.31.0/cli/src/commands/pattern/push.ts)_
+
+## `lps pattern remove SLUG`
+
+Stop registering a Loopress block pattern on WordPress. A wp:pattern reference to it renders nothing, copies already inserted in posts stay.
 
-  $ lps page diff --env staging --against production
 ```
+USAGE
+  $ lps pattern remove SLUG [--json] [--env <value>] [-d] [-y]
 
-_See code: [src/commands/page/diff.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.29.0/cli/src/commands/page/diff.ts)_
+ARGUMENTS
+  SLUG  The pattern slug, its patterns/ file name without .html
 
-## `lps page list`
+FLAGS
+  -d, --dry-run      Show what would change without making changes
+  -y, --yes          Answer yes to confirmation prompts
+      --env=<value>  Target environment by name (default: "local", or the project's only environment)
 
-List the static pages managed by Loopress on WordPress
+GLOBAL FLAGS
+  --json  Format output as json.
+
+DESCRIPTION
+  Stop registering a Loopress block pattern on WordPress. A wp:pattern reference to it renders nothing, copies already
+  inserted in posts stay.
+
+ALIASES
+  $ lps pattern remove
+
+EXAMPLES
+  $ lps pattern rm <slug>
+
+  $ lps pattern remove <slug> --yes
+```
+
+## `lps pattern rm SLUG`
+
+Stop registering a Loopress block pattern on WordPress. A wp:pattern reference to it renders nothing, copies already inserted in posts stay.
 
 ```
 USAGE
-  $ lps page list [--json] [--env <value>]
+  $ lps pattern rm SLUG [--json] [--env <value>] [-d] [-y]
+
+ARGUMENTS
+  SLUG  The pattern slug, its patterns/ file name without .html
 
 FLAGS
-  --env=<value>  Target environment by name, overriding the globally active one (lps project switch)
+  -d, --dry-run      Show what would change without making changes
+  -y, --yes          Answer yes to confirmation prompts
+      --env=<value>  Target environment by name (default: "local", or the project's only environment)
 
 GLOBAL FLAGS
   --json  Format output as json.
 
 DESCRIPTION
-  List the static pages managed by Loopress on WordPress
+  Stop registering a Loopress block pattern on WordPress. A wp:pattern reference to it renders nothing, copies already
+  inserted in posts stay.
+
+ALIASES
+  $ lps pattern remove
 
 EXAMPLES
-  $ lps page list
+  $ lps pattern rm <slug>
+
+  $ lps pattern remove <slug> --yes
 ```
 
-_See code: [src/commands/page/list.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.29.0/cli/src/commands/page/list.ts)_
+_See code: [src/commands/pattern/rm.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.31.0/cli/src/commands/pattern/rm.ts)_
 
-## `lps page push [SLUG]`
+## `lps pattern rollback [PATH]`
 
-Push static HTML pages (pages/<slug>.html) to WordPress. The `status` header (draft or publish, draft by default) is applied on every push.
+Restore block patterns to a snapshot taken automatically before an earlier `lps pattern push`
 
 ```
 USAGE
-  $ lps page push [SLUG] [--json] [--env <value>] [-d] [-y]
+  $ lps pattern rollback [PATH] [--json] [--env <value>] [-d] [-y] [--list] [--to <value>]
 
 ARGUMENTS
-  [SLUG]  Push only this page (its file name without .html). Pushes every page when omitted.
+  [PATH]  Path to patterns directory (overrides project config)
 
 FLAGS
   -d, --dry-run      Show what would change without making changes
   -y, --yes          Answer yes to confirmation prompts
-      --env=<value>  Target environment by name, overriding the globally active one (lps project switch)
+      --env=<value>  Target environment by name (default: "local", or the project's only environment)
+      --list         List available snapshots instead of rolling back
+      --to=<value>   Roll back to this snapshot id instead of the most recent one
 
 GLOBAL FLAGS
   --json  Format output as json.
 
 DESCRIPTION
-  Push static HTML pages (pages/<slug>.html) to WordPress. The `status` header (draft or publish, draft by default) is
-  applied on every push.
+  Restore block patterns to a snapshot taken automatically before an earlier `lps pattern push`
 
 EXAMPLES
-  $ lps page push
+  $ lps pattern rollback
 
-  $ lps page push legal-notice
+  $ lps pattern rollback --list
 
-  $ lps page push --dry-run
+  $ lps pattern rollback --to 1732000000000
+
+  $ lps pattern rollback --dry-run
 ```
 
-_See code: [src/commands/page/push.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.29.0/cli/src/commands/page/push.ts)_
+_See code: [src/commands/pattern/rollback.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.31.0/cli/src/commands/pattern/rollback.ts)_
 
 ## `lps plugin add SLUG`
 
@@ -1742,7 +2468,7 @@ ARGUMENTS
 
 FLAGS
   -d, --dry-run          Show what would change without making changes
-      --env=<value>      Target environment by name, overriding the globally active one (lps project switch)
+      --env=<value>      Target environment by name (default: "local", or the project's only environment)
       --version=<value>  Exact version to pin (default: "latest", tracked on every push)
 
 GLOBAL FLAGS
@@ -1759,7 +2485,7 @@ EXAMPLES
   $ lps plugin add contact-form-7 --dry-run
 ```
 
-_See code: [src/commands/plugin/add.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.29.0/cli/src/commands/plugin/add.ts)_
+_See code: [src/commands/plugin/add.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.31.0/cli/src/commands/plugin/add.ts)_
 
 ## `lps plugin audit`
 
@@ -1770,7 +2496,7 @@ USAGE
   $ lps plugin audit [--json] [--env <value>]
 
 FLAGS
-  --env=<value>  Target environment by name, overriding the globally active one (lps project switch)
+  --env=<value>  Target environment by name (default: "local", or the project's only environment)
 
 GLOBAL FLAGS
   --json  Format output as json.
@@ -1782,7 +2508,7 @@ EXAMPLES
   $ lps plugin audit
 ```
 
-_See code: [src/commands/plugin/audit.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.29.0/cli/src/commands/plugin/audit.ts)_
+_See code: [src/commands/plugin/audit.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.31.0/cli/src/commands/plugin/audit.ts)_
 
 ## `lps plugin pull`
 
@@ -1795,7 +2521,7 @@ USAGE
 FLAGS
   -d, --dry-run            Show what would change without making changes
   -y, --yes                Answer yes to confirmation prompts
-      --env=<value>        Target environment by name, overriding the globally active one (lps project switch)
+      --env=<value>        Target environment by name (default: "local", or the project's only environment)
       --plugin=<value>...  Start tracking this installed plugin too, without asking (repeatable)
 
 GLOBAL FLAGS
@@ -1812,7 +2538,7 @@ EXAMPLES
   $ lps plugin pull --env production --plugin query-monitor
 ```
 
-_See code: [src/commands/plugin/pull.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.29.0/cli/src/commands/plugin/pull.ts)_
+_See code: [src/commands/plugin/pull.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.31.0/cli/src/commands/plugin/pull.ts)_
 
 ## `lps plugin push`
 
@@ -1820,15 +2546,16 @@ Install plugins on WordPress to match loopress.json (or composer.json), via Comp
 
 ```
 USAGE
-  $ lps plugin push [--json] [--env <value>] [-d] [-y] [--activate] [--force] [--prune]
+  $ lps plugin push [--json] [--env <value>] [--overwrite] [-d] [-y] [--activate] [--force] [--prune]
 
 FLAGS
   -d, --dry-run      Show what would change without making changes
   -y, --yes          Answer yes to confirmation prompts
       --activate     composer.json projects only: activate every plugin it declares. Without it, plugins keep their
                      current state and new ones stay inactive
-      --env=<value>  Target environment by name, overriding the globally active one (lps project switch)
+      --env=<value>  Target environment by name (default: "local", or the project's only environment)
       --force        Allow downgrades and let Loopress take over plugins installed outside it (replaces their files)
+      --overwrite    Push even over changes made on the site outside Loopress since your last push
       --prune        Deactivate plugins that are active on the site but absent from loopress.json (or composer.json)
 
 GLOBAL FLAGS
@@ -1845,7 +2572,7 @@ EXAMPLES
   $ lps plugin push --force --prune
 ```
 
-_See code: [src/commands/plugin/push.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.29.0/cli/src/commands/plugin/push.ts)_
+_See code: [src/commands/plugin/push.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.31.0/cli/src/commands/plugin/push.ts)_
 
 ## `lps plugin status`
 
@@ -1856,7 +2583,7 @@ USAGE
   $ lps plugin status [--json] [--env <value>]
 
 FLAGS
-  --env=<value>  Target environment by name, overriding the globally active one (lps project switch)
+  --env=<value>  Target environment by name (default: "local", or the project's only environment)
 
 GLOBAL FLAGS
   --json  Format output as json.
@@ -1868,7 +2595,7 @@ EXAMPLES
   $ lps plugin status
 ```
 
-_See code: [src/commands/plugin/status.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.29.0/cli/src/commands/plugin/status.ts)_
+_See code: [src/commands/plugin/status.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.31.0/cli/src/commands/plugin/status.ts)_
 
 ## `lps project config`
 
@@ -1886,7 +2613,7 @@ EXAMPLES
   $ lps project config
 ```
 
-_See code: [src/commands/project/config.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.29.0/cli/src/commands/project/config.ts)_
+_See code: [src/commands/project/config.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.31.0/cli/src/commands/project/config.ts)_
 
 ## `lps project list`
 
@@ -1906,7 +2633,7 @@ EXAMPLES
   $ lps project list
 ```
 
-_See code: [src/commands/project/list.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.29.0/cli/src/commands/project/list.ts)_
+_See code: [src/commands/project/list.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.31.0/cli/src/commands/project/list.ts)_
 
 ## `lps project pull`
 
@@ -1923,7 +2650,7 @@ EXAMPLES
   $ lps project pull
 ```
 
-_See code: [src/commands/project/pull.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.29.0/cli/src/commands/project/pull.ts)_
+_See code: [src/commands/project/pull.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.31.0/cli/src/commands/project/pull.ts)_
 
 ## `lps project push`
 
@@ -1943,7 +2670,7 @@ EXAMPLES
   $ lps project push
 ```
 
-_See code: [src/commands/project/push.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.29.0/cli/src/commands/project/push.ts)_
+_See code: [src/commands/project/push.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.31.0/cli/src/commands/project/push.ts)_
 
 ## `lps project remove`
 
@@ -1960,7 +2687,7 @@ EXAMPLES
   $ lps project remove
 ```
 
-_See code: [src/commands/project/remove.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.29.0/cli/src/commands/project/remove.ts)_
+_See code: [src/commands/project/remove.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.31.0/cli/src/commands/project/remove.ts)_
 
 ## `lps project rotate`
 
@@ -1971,7 +2698,7 @@ USAGE
   $ lps project rotate [--env <value>]
 
 FLAGS
-  --env=<value>  Target environment by name, overriding the globally active one (lps project switch)
+  --env=<value>  Target environment by name (default: "local", or the project's only environment)
 
 DESCRIPTION
   Rotate the WordPress application password for the current (or --env) environment
@@ -1982,24 +2709,24 @@ EXAMPLES
   $ lps project rotate --env staging
 ```
 
-_See code: [src/commands/project/rotate.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.29.0/cli/src/commands/project/rotate.ts)_
+_See code: [src/commands/project/rotate.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.31.0/cli/src/commands/project/rotate.ts)_
 
 ## `lps project switch`
 
-Switch the active project and environment
+Switch the active project (pass --env to target a non-local environment)
 
 ```
 USAGE
   $ lps project switch
 
 DESCRIPTION
-  Switch the active project and environment
+  Switch the active project (pass --env to target a non-local environment)
 
 EXAMPLES
   $ lps project switch
 ```
 
-_See code: [src/commands/project/switch.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.29.0/cli/src/commands/project/switch.ts)_
+_See code: [src/commands/project/switch.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.31.0/cli/src/commands/project/switch.ts)_
 
 ## `lps promote FROM TO`
 
@@ -2007,15 +2734,16 @@ Copy every tracked resource from one environment to another by pulling from <fro
 
 ```
 USAGE
-  $ lps promote FROM TO [--json] [-d] [-y]
+  $ lps promote FROM TO [--json] [-d] [-y] [--overwrite]
 
 ARGUMENTS
   FROM  Environment to copy the configuration from
   TO    Environment to copy the configuration to
 
 FLAGS
-  -d, --dry-run  Show what would change without making changes
-  -y, --yes      Answer yes to confirmation prompts
+  -d, --dry-run    Show what would change without making changes
+  -y, --yes        Answer yes to confirmation prompts
+      --overwrite  Push even over changes made on the site outside Loopress since your last push
 
 GLOBAL FLAGS
   --json  Format output as json.
@@ -2031,11 +2759,11 @@ EXAMPLES
   $ lps promote production staging --dry-run
 ```
 
-_See code: [src/commands/promote.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.29.0/cli/src/commands/promote.ts)_
+_See code: [src/commands/promote.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.31.0/cli/src/commands/promote.ts)_
 
 ## `lps pull`
 
-Pull all content, plugins, composer dependencies, ACF, API routes, hooks, forms, SEO, menus, options, and snippets, from WordPress
+Pull all content, plugins, composer dependencies, post types, taxonomies, post meta, roles, ACF, API routes, hooks, forms, patterns, menus, options, and snippets, from WordPress
 
 ```
 USAGE
@@ -2044,14 +2772,14 @@ USAGE
 FLAGS
   -d, --dry-run      Show what would change without making changes
   -y, --yes          Answer yes to confirmation prompts
-      --env=<value>  Target environment by name, overriding the globally active one (lps project switch)
+      --env=<value>  Target environment by name (default: "local", or the project's only environment)
 
 GLOBAL FLAGS
   --json  Format output as json.
 
 DESCRIPTION
-  Pull all content, plugins, composer dependencies, ACF, API routes, hooks, forms, SEO, menus, options, and snippets,
-  from WordPress
+  Pull all content, plugins, composer dependencies, post types, taxonomies, post meta, roles, ACF, API routes, hooks,
+  forms, patterns, menus, options, and snippets, from WordPress
 
 EXAMPLES
   $ lps pull
@@ -2061,27 +2789,28 @@ EXAMPLES
   $ lps pull --dry-run
 ```
 
-_See code: [src/commands/pull.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.29.0/cli/src/commands/pull.ts)_
+_See code: [src/commands/pull.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.31.0/cli/src/commands/pull.ts)_
 
 ## `lps push`
 
-Push all local content, plugins, composer dependencies, ACF, API routes, hooks, forms, templates, pages, SEO, menus, options, and snippets, to WordPress
+Push all local content, plugins, composer dependencies, post types, taxonomies, post meta, roles, ACF, API routes, hooks, forms, patterns, templates, pages, menus, options, and snippets, to WordPress
 
 ```
 USAGE
-  $ lps push [--json] [--env <value>] [-d] [-y]
+  $ lps push [--json] [--env <value>] [-d] [-y] [--overwrite]
 
 FLAGS
   -d, --dry-run      Show what would change without making changes
   -y, --yes          Answer yes to confirmation prompts
-      --env=<value>  Target environment by name, overriding the globally active one (lps project switch)
+      --env=<value>  Target environment by name (default: "local", or the project's only environment)
+      --overwrite    Push even over changes made on the site outside Loopress since your last push
 
 GLOBAL FLAGS
   --json  Format output as json.
 
 DESCRIPTION
-  Push all local content, plugins, composer dependencies, ACF, API routes, hooks, forms, templates, pages, SEO, menus,
-  options, and snippets, to WordPress
+  Push all local content, plugins, composer dependencies, post types, taxonomies, post meta, roles, ACF, API routes,
+  hooks, forms, patterns, templates, pages, menus, options, and snippets, to WordPress
 
 EXAMPLES
   $ lps push
@@ -2091,145 +2820,203 @@ EXAMPLES
   $ lps push --dry-run
 ```
 
-_See code: [src/commands/push.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.29.0/cli/src/commands/push.ts)_
+_See code: [src/commands/push.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.31.0/cli/src/commands/push.ts)_
 
-## `lps seo diff [PATH]`
+## `lps role diff [PATH]`
 
-Show what differs in SEO settings, post meta, and redirects between your local files and a WordPress environment, or between two environments
+Show what differs in roles between your local roles/ files and a WordPress environment, or between two environments
 
 ```
 USAGE
-  $ lps seo diff [PATH] [--json] [--env <value>] [--against <value>]
+  $ lps role diff [PATH] [--json] [--env <value>] [--against <value>]
 
 ARGUMENTS
-  [PATH]  Path to SEO directory (overrides project config)
+  [PATH]  Path to roles directory (overrides project config)
 
 FLAGS
   --against=<value>  Compare the primary environment against this second environment instead of against local files
-  --env=<value>      Target environment by name, overriding the globally active one (lps project switch)
+  --env=<value>      Target environment by name (default: "local", or the project's only environment)
 
 GLOBAL FLAGS
   --json  Format output as json.
 
 DESCRIPTION
-  Show what differs in SEO settings, post meta, and redirects between your local files and a WordPress environment, or
-  between two environments
+  Show what differs in roles between your local roles/ files and a WordPress environment, or between two environments
 
 EXAMPLES
-  $ lps seo diff
+  $ lps role diff
 
-  $ lps seo diff --env staging
+  $ lps role diff --env staging
 
-  $ lps seo diff --env staging --against production
+  $ lps role diff --env staging --against production
 ```
 
-_See code: [src/commands/seo/diff.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.29.0/cli/src/commands/seo/diff.ts)_
+_See code: [src/commands/role/diff.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.31.0/cli/src/commands/role/diff.ts)_
 
-## `lps seo list`
+## `lps role list`
 
-List posts with SEO meta, and redirects if supported by the active SEO plugin, on WordPress
+List the user roles on WordPress, where each comes from (Loopress, WordPress, a plugin) and how many users have it. Only Loopress ones are pulled and pushed.
 
 ```
 USAGE
-  $ lps seo list [--json] [--env <value>] [--post-type <value>...]
+  $ lps role list [--json] [--env <value>]
 
 FLAGS
-  --env=<value>           Target environment by name, overriding the globally active one (lps project switch)
-  --post-type=<value>...  Limit to specific post types
+  --env=<value>  Target environment by name (default: "local", or the project's only environment)
 
 GLOBAL FLAGS
   --json  Format output as json.
 
 DESCRIPTION
-  List posts with SEO meta, and redirects if supported by the active SEO plugin, on WordPress
+  List the user roles on WordPress, where each comes from (Loopress, WordPress, a plugin) and how many users have it.
+  Only Loopress ones are pulled and pushed.
 
 EXAMPLES
-  $ lps seo list
+  $ lps role list
+```
+
+_See code: [src/commands/role/list.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.31.0/cli/src/commands/role/list.ts)_
 
-  $ lps seo list --post-type post
+## `lps role pull [PATH]`
+
+Pull the roles Loopress manages on WordPress into roles/<slug>.json files. Built-in roles and roles created by a plugin are never pulled, see `lps role list`.
+
+```
+USAGE
+  $ lps role pull [PATH] [--json] [--env <value>] [-d] [-y]
+
+ARGUMENTS
+  [PATH]  Path to the roles directory (overrides project config)
+
+FLAGS
+  -d, --dry-run      Show what would change without making changes
+  -y, --yes          Answer yes to confirmation prompts
+      --env=<value>  Target environment by name (default: "local", or the project's only environment)
+
+GLOBAL FLAGS
+  --json  Format output as json.
+
+DESCRIPTION
+  Pull the roles Loopress manages on WordPress into roles/<slug>.json files. Built-in roles and roles created by a
+  plugin are never pulled, see `lps role list`.
+
+EXAMPLES
+  $ lps role pull
 ```
 
-_See code: [src/commands/seo/list.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.29.0/cli/src/commands/seo/list.ts)_
+_See code: [src/commands/role/pull.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.31.0/cli/src/commands/role/pull.ts)_
 
-## `lps seo pull [PATH]`
+## `lps role push [PATH]`
 
-Pull SEO settings, post meta, and (if supported) redirects from WordPress
+Push local roles (roles/<slug>.json, a "name" and its "capabilities") to WordPress. Create or update only, never deletes a role (use `lps role rm`), never changes which users have it.
 
 ```
 USAGE
-  $ lps seo pull [PATH] [--json] [--env <value>] [-d] [-y] [--post-type <value>...]
+  $ lps role push [PATH] [--json] [--env <value>] [--overwrite] [-d] [-y]
 
 ARGUMENTS
-  [PATH]  Path to SEO directory (overrides project config)
+  [PATH]  Path to the roles directory (overrides project config)
 
 FLAGS
-  -d, --dry-run               Show what would change without making changes
-  -y, --yes                   Answer yes to confirmation prompts
-      --env=<value>           Target environment by name, overriding the globally active one (lps project switch)
-      --post-type=<value>...  Limit post meta to specific post types
+  -d, --dry-run      Show what would change without making changes
+  -y, --yes          Answer yes to confirmation prompts
+      --env=<value>  Target environment by name (default: "local", or the project's only environment)
+      --overwrite    Push even over changes made on the site outside Loopress since your last push
 
 GLOBAL FLAGS
   --json  Format output as json.
 
 DESCRIPTION
-  Pull SEO settings, post meta, and (if supported) redirects from WordPress
+  Push local roles (roles/<slug>.json, a "name" and its "capabilities") to WordPress. Create or update only, never
+  deletes a role (use `lps role rm`), never changes which users have it.
 
 EXAMPLES
-  $ lps seo pull
+  $ lps role push
+```
+
+_See code: [src/commands/role/push.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.31.0/cli/src/commands/role/push.ts)_
+
+## `lps role remove SLUG`
+
+Stop registering a Loopress role on WordPress. Its users keep it in their profile, with no capability until the role is pushed again.
 
-  $ lps seo pull --post-type post --post-type page
 ```
+USAGE
+  $ lps role remove SLUG [--json] [--env <value>] [-d] [-y]
+
+ARGUMENTS
+  SLUG  The role slug, its roles/ file name without .json
+
+FLAGS
+  -d, --dry-run      Show what would change without making changes
+  -y, --yes          Answer yes to confirmation prompts
+      --env=<value>  Target environment by name (default: "local", or the project's only environment)
+
+GLOBAL FLAGS
+  --json  Format output as json.
+
+DESCRIPTION
+  Stop registering a Loopress role on WordPress. Its users keep it in their profile, with no capability until the role
+  is pushed again.
+
+ALIASES
+  $ lps role remove
+
+EXAMPLES
+  $ lps role rm <slug>
 
-_See code: [src/commands/seo/pull.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.29.0/cli/src/commands/seo/pull.ts)_
+  $ lps role remove <slug> --yes
+```
 
-## `lps seo push [PATH]`
+## `lps role rm SLUG`
 
-Push SEO settings, post meta, and redirects to WordPress. Local redirect files created remotely are renamed on disk to the `<id>-<slug>` convention. Fails clearly per file if the active SEO plugin does not support redirects.
+Stop registering a Loopress role on WordPress. Its users keep it in their profile, with no capability until the role is pushed again.
 
 ```
 USAGE
-  $ lps seo push [PATH] [--json] [--env <value>] [-d] [-y] [--allow-external-redirects]
+  $ lps role rm SLUG [--json] [--env <value>] [-d] [-y]
 
 ARGUMENTS
-  [PATH]  Path to SEO directory (overrides project config)
+  SLUG  The role slug, its roles/ file name without .json
 
 FLAGS
-  -d, --dry-run                   Show what would change without making changes
-  -y, --yes                       Answer yes to confirmation prompts
-      --allow-external-redirects  Allow pushing a redirect whose target points off this site. Off by default: the server
-                                  rejects an off-site `urlTo` so a stray push can't 301 traffic away.
-      --env=<value>               Target environment by name, overriding the globally active one (lps project switch)
+  -d, --dry-run      Show what would change without making changes
+  -y, --yes          Answer yes to confirmation prompts
+      --env=<value>  Target environment by name (default: "local", or the project's only environment)
 
 GLOBAL FLAGS
   --json  Format output as json.
 
 DESCRIPTION
-  Push SEO settings, post meta, and redirects to WordPress. Local redirect files created remotely are renamed on disk to
-  the `<id>-<slug>` convention. Fails clearly per file if the active SEO plugin does not support redirects.
+  Stop registering a Loopress role on WordPress. Its users keep it in their profile, with no capability until the role
+  is pushed again.
+
+ALIASES
+  $ lps role remove
 
 EXAMPLES
-  $ lps seo push
+  $ lps role rm <slug>
 
-  $ lps seo push --allow-external-redirects
+  $ lps role remove <slug> --yes
 ```
 
-_See code: [src/commands/seo/push.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.29.0/cli/src/commands/seo/push.ts)_
+_See code: [src/commands/role/rm.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.31.0/cli/src/commands/role/rm.ts)_
 
-## `lps seo rollback [PATH]`
+## `lps role rollback [PATH]`
 
-Restore SEO settings, post meta, and redirects to a snapshot taken automatically before an earlier `lps seo push`
+Restore roles to a snapshot taken automatically before an earlier `lps role push`
 
 ```
 USAGE
-  $ lps seo rollback [PATH] [--json] [--env <value>] [-d] [-y] [--list] [--to <value>]
+  $ lps role rollback [PATH] [--json] [--env <value>] [-d] [-y] [--list] [--to <value>]
 
 ARGUMENTS
-  [PATH]  Path to SEO directory (overrides project config)
+  [PATH]  Path to roles directory (overrides project config)
 
 FLAGS
   -d, --dry-run      Show what would change without making changes
   -y, --yes          Answer yes to confirmation prompts
-      --env=<value>  Target environment by name, overriding the globally active one (lps project switch)
+      --env=<value>  Target environment by name (default: "local", or the project's only environment)
       --list         List available snapshots instead of rolling back
       --to=<value>   Roll back to this snapshot id instead of the most recent one
 
@@ -2237,19 +3024,19 @@ GLOBAL FLAGS
   --json  Format output as json.
 
 DESCRIPTION
-  Restore SEO settings, post meta, and redirects to a snapshot taken automatically before an earlier `lps seo push`
+  Restore roles to a snapshot taken automatically before an earlier `lps role push`
 
 EXAMPLES
-  $ lps seo rollback
+  $ lps role rollback
 
-  $ lps seo rollback --list
+  $ lps role rollback --list
 
-  $ lps seo rollback --to 1732000000000
+  $ lps role rollback --to 1732000000000
 
-  $ lps seo rollback --dry-run
+  $ lps role rollback --dry-run
 ```
 
-_See code: [src/commands/seo/rollback.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.29.0/cli/src/commands/seo/rollback.ts)_
+_See code: [src/commands/role/rollback.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.31.0/cli/src/commands/role/rollback.ts)_
 
 ## `lps snippet diff [PATH]`
 
@@ -2264,7 +3051,7 @@ ARGUMENTS
 
 FLAGS
   --against=<value>  Compare the primary environment against this second environment instead of against local files
-  --env=<value>      Target environment by name, overriding the globally active one (lps project switch)
+  --env=<value>      Target environment by name (default: "local", or the project's only environment)
 
 GLOBAL FLAGS
   --json  Format output as json.
@@ -2280,7 +3067,7 @@ EXAMPLES
   $ lps snippet diff --env staging --against production
 ```
 
-_See code: [src/commands/snippet/diff.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.29.0/cli/src/commands/snippet/diff.ts)_
+_See code: [src/commands/snippet/diff.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.31.0/cli/src/commands/snippet/diff.ts)_
 
 ## `lps snippet list`
 
@@ -2291,7 +3078,7 @@ USAGE
   $ lps snippet list [--json] [--env <value>]
 
 FLAGS
-  --env=<value>  Target environment by name, overriding the globally active one (lps project switch)
+  --env=<value>  Target environment by name (default: "local", or the project's only environment)
 
 GLOBAL FLAGS
   --json  Format output as json.
@@ -2303,7 +3090,7 @@ EXAMPLES
   $ lps snippet list
 ```
 
-_See code: [src/commands/snippet/list.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.29.0/cli/src/commands/snippet/list.ts)_
+_See code: [src/commands/snippet/list.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.31.0/cli/src/commands/snippet/list.ts)_
 
 ## `lps snippet publish [PATH]`
 
@@ -2326,7 +3113,7 @@ EXAMPLES
   $ lps snippet publish ./snippets
 ```
 
-_See code: [src/commands/snippet/publish.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.29.0/cli/src/commands/snippet/publish.ts)_
+_See code: [src/commands/snippet/publish.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.31.0/cli/src/commands/snippet/publish.ts)_
 
 ## `lps snippet pull [PATH]`
 
@@ -2342,7 +3129,7 @@ ARGUMENTS
 FLAGS
   -d, --dry-run      Show what would change without making changes
   -y, --yes          Answer yes to confirmation prompts
-      --env=<value>  Target environment by name, overriding the globally active one (lps project switch)
+      --env=<value>  Target environment by name (default: "local", or the project's only environment)
 
 GLOBAL FLAGS
   --json  Format output as json.
@@ -2356,7 +3143,7 @@ EXAMPLES
   $ lps snippet pull ./snippets
 ```
 
-_See code: [src/commands/snippet/pull.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.29.0/cli/src/commands/snippet/pull.ts)_
+_See code: [src/commands/snippet/pull.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.31.0/cli/src/commands/snippet/pull.ts)_
 
 ## `lps snippet push [PATH]`
 
@@ -2364,7 +3151,7 @@ Push snippets to WordPress. Local snippet files created or updated remotely are
 
 ```
 USAGE
-  $ lps snippet push [PATH] [--json] [--env <value>] [-d] [-y]
+  $ lps snippet push [PATH] [--json] [--env <value>] [--overwrite] [-d] [-y]
 
 ARGUMENTS
   [PATH]  Path to snippets directory (overrides project config)
@@ -2372,7 +3159,8 @@ ARGUMENTS
 FLAGS
   -d, --dry-run      Show what would change without making changes
   -y, --yes          Answer yes to confirmation prompts
-      --env=<value>  Target environment by name, overriding the globally active one (lps project switch)
+      --env=<value>  Target environment by name (default: "local", or the project's only environment)
+      --overwrite    Push even over changes made on the site outside Loopress since your last push
 
 GLOBAL FLAGS
   --json  Format output as json.
@@ -2387,7 +3175,7 @@ EXAMPLES
   $ lps snippet push ./snippets
 ```
 
-_See code: [src/commands/snippet/push.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.29.0/cli/src/commands/snippet/push.ts)_
+_See code: [src/commands/snippet/push.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.31.0/cli/src/commands/snippet/push.ts)_
 
 ## `lps snippet rollback [PATH]`
 
@@ -2403,7 +3191,7 @@ ARGUMENTS
 FLAGS
   -d, --dry-run      Show what would change without making changes
   -y, --yes          Answer yes to confirmation prompts
-      --env=<value>  Target environment by name, overriding the globally active one (lps project switch)
+      --env=<value>  Target environment by name (default: "local", or the project's only environment)
       --list         List available snapshots instead of rolling back
       --to=<value>   Roll back to this snapshot id instead of the most recent one
 
@@ -2423,7 +3211,7 @@ EXAMPLES
   $ lps snippet rollback --dry-run
 ```
 
-_See code: [src/commands/snippet/rollback.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.29.0/cli/src/commands/snippet/rollback.ts)_
+_See code: [src/commands/snippet/rollback.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.31.0/cli/src/commands/snippet/rollback.ts)_
 
 ## `lps status`
 
@@ -2448,7 +3236,224 @@ EXAMPLES
   $ lps status --env staging
 ```
 
-_See code: [src/commands/status.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.29.0/cli/src/commands/status.ts)_
+_See code: [src/commands/status.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.31.0/cli/src/commands/status.ts)_
+
+## `lps taxonomy diff [PATH]`
+
+Show what differs in taxonomies between your local taxonomies/ files and a WordPress environment, or between two environments
+
+```
+USAGE
+  $ lps taxonomy diff [PATH] [--json] [--env <value>] [--against <value>]
+
+ARGUMENTS
+  [PATH]  Path to taxonomies directory (overrides project config)
+
+FLAGS
+  --against=<value>  Compare the primary environment against this second environment instead of against local files
+  --env=<value>      Target environment by name (default: "local", or the project's only environment)
+
+GLOBAL FLAGS
+  --json  Format output as json.
+
+DESCRIPTION
+  Show what differs in taxonomies between your local taxonomies/ files and a WordPress environment, or between two
+  environments
+
+EXAMPLES
+  $ lps taxonomy diff
+
+  $ lps taxonomy diff --env staging
+
+  $ lps taxonomy diff --env staging --against production
+```
+
+_See code: [src/commands/taxonomy/diff.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.31.0/cli/src/commands/taxonomy/diff.ts)_
+
+## `lps taxonomy list`
+
+List the taxonomies registered on WordPress, where each comes from (Loopress, WordPress, ACF, CPT UI, a theme or plugin) and the post types it attaches to. Only Loopress ones are pulled and pushed.
+
+```
+USAGE
+  $ lps taxonomy list [--json] [--env <value>]
+
+FLAGS
+  --env=<value>  Target environment by name (default: "local", or the project's only environment)
+
+GLOBAL FLAGS
+  --json  Format output as json.
+
+DESCRIPTION
+  List the taxonomies registered on WordPress, where each comes from (Loopress, WordPress, ACF, CPT UI, a theme or
+  plugin) and the post types it attaches to. Only Loopress ones are pulled and pushed.
+
+EXAMPLES
+  $ lps taxonomy list
+```
+
+_See code: [src/commands/taxonomy/list.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.31.0/cli/src/commands/taxonomy/list.ts)_
+
+## `lps taxonomy pull [PATH]`
+
+Pull the taxonomies Loopress manages on WordPress into taxonomies/<slug>.json files, never their terms. Taxonomies registered by a theme or another plugin are never pulled, see `lps taxonomy list`.
+
+```
+USAGE
+  $ lps taxonomy pull [PATH] [--json] [--env <value>] [-d] [-y]
+
+ARGUMENTS
+  [PATH]  Path to the taxonomies directory (overrides project config)
+
+FLAGS
+  -d, --dry-run      Show what would change without making changes
+  -y, --yes          Answer yes to confirmation prompts
+      --env=<value>  Target environment by name (default: "local", or the project's only environment)
+
+GLOBAL FLAGS
+  --json  Format output as json.
+
+DESCRIPTION
+  Pull the taxonomies Loopress manages on WordPress into taxonomies/<slug>.json files, never their terms. Taxonomies
+  registered by a theme or another plugin are never pulled, see `lps taxonomy list`.
+
+EXAMPLES
+  $ lps taxonomy pull
+```
+
+_See code: [src/commands/taxonomy/pull.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.31.0/cli/src/commands/taxonomy/pull.ts)_
+
+## `lps taxonomy push [PATH]`
+
+Push local taxonomies (taxonomies/<slug>.json, register_taxonomy() arguments plus "object_type") to WordPress. Create or update only, never deletes a taxonomy (use `lps taxonomy rm`), never touches its terms.
+
+```
+USAGE
+  $ lps taxonomy push [PATH] [--json] [--env <value>] [--overwrite] [-d] [-y]
+
+ARGUMENTS
+  [PATH]  Path to the taxonomies directory (overrides project config)
+
+FLAGS
+  -d, --dry-run      Show what would change without making changes
+  -y, --yes          Answer yes to confirmation prompts
+      --env=<value>  Target environment by name (default: "local", or the project's only environment)
+      --overwrite    Push even over changes made on the site outside Loopress since your last push
+
+GLOBAL FLAGS
+  --json  Format output as json.
+
+DESCRIPTION
+  Push local taxonomies (taxonomies/<slug>.json, register_taxonomy() arguments plus "object_type") to WordPress. Create
+  or update only, never deletes a taxonomy (use `lps taxonomy rm`), never touches its terms.
+
+EXAMPLES
+  $ lps taxonomy push
+```
+
+_See code: [src/commands/taxonomy/push.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.31.0/cli/src/commands/taxonomy/push.ts)_
+
+## `lps taxonomy remove SLUG`
+
+Stop registering a Loopress taxonomy on WordPress. Its terms are kept in the database, hidden until the taxonomy is pushed again.
+
+```
+USAGE
+  $ lps taxonomy remove SLUG [--json] [--env <value>] [-d] [-y]
+
+ARGUMENTS
+  SLUG  The taxonomy slug, its taxonomies/ file name without .json
+
+FLAGS
+  -d, --dry-run      Show what would change without making changes
+  -y, --yes          Answer yes to confirmation prompts
+      --env=<value>  Target environment by name (default: "local", or the project's only environment)
+
+GLOBAL FLAGS
+  --json  Format output as json.
+
+DESCRIPTION
+  Stop registering a Loopress taxonomy on WordPress. Its terms are kept in the database, hidden until the taxonomy is
+  pushed again.
+
+ALIASES
+  $ lps taxonomy remove
+
+EXAMPLES
+  $ lps taxonomy rm <slug>
+
+  $ lps taxonomy remove <slug> --yes
+```
+
+## `lps taxonomy rm SLUG`
+
+Stop registering a Loopress taxonomy on WordPress. Its terms are kept in the database, hidden until the taxonomy is pushed again.
+
+```
+USAGE
+  $ lps taxonomy rm SLUG [--json] [--env <value>] [-d] [-y]
+
+ARGUMENTS
+  SLUG  The taxonomy slug, its taxonomies/ file name without .json
+
+FLAGS
+  -d, --dry-run      Show what would change without making changes
+  -y, --yes          Answer yes to confirmation prompts
+      --env=<value>  Target environment by name (default: "local", or the project's only environment)
+
+GLOBAL FLAGS
+  --json  Format output as json.
+
+DESCRIPTION
+  Stop registering a Loopress taxonomy on WordPress. Its terms are kept in the database, hidden until the taxonomy is
+  pushed again.
+
+ALIASES
+  $ lps taxonomy remove
+
+EXAMPLES
+  $ lps taxonomy rm <slug>
+
+  $ lps taxonomy remove <slug> --yes
+```
+
+_See code: [src/commands/taxonomy/rm.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.31.0/cli/src/commands/taxonomy/rm.ts)_
+
+## `lps taxonomy rollback [PATH]`
+
+Restore taxonomies to a snapshot taken automatically before an earlier `lps taxonomy push`
+
+```
+USAGE
+  $ lps taxonomy rollback [PATH] [--json] [--env <value>] [-d] [-y] [--list] [--to <value>]
+
+ARGUMENTS
+  [PATH]  Path to taxonomies directory (overrides project config)
+
+FLAGS
+  -d, --dry-run      Show what would change without making changes
+  -y, --yes          Answer yes to confirmation prompts
+      --env=<value>  Target environment by name (default: "local", or the project's only environment)
+      --list         List available snapshots instead of rolling back
+      --to=<value>   Roll back to this snapshot id instead of the most recent one
+
+GLOBAL FLAGS
+  --json  Format output as json.
+
+DESCRIPTION
+  Restore taxonomies to a snapshot taken automatically before an earlier `lps taxonomy push`
+
+EXAMPLES
+  $ lps taxonomy rollback
+
+  $ lps taxonomy rollback --list
+
+  $ lps taxonomy rollback --to 1732000000000
+
+  $ lps taxonomy rollback --dry-run
+```
+
+_See code: [src/commands/taxonomy/rollback.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.31.0/cli/src/commands/taxonomy/rollback.ts)_
 
 ## `lps telemetry disable`
 
@@ -2465,7 +3470,7 @@ EXAMPLES
   $ lps telemetry disable
 ```
 
-_See code: [src/commands/telemetry/disable.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.29.0/cli/src/commands/telemetry/disable.ts)_
+_See code: [src/commands/telemetry/disable.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.31.0/cli/src/commands/telemetry/disable.ts)_
 
 ## `lps telemetry enable`
 
@@ -2482,7 +3487,7 @@ EXAMPLES
   $ lps telemetry enable
 ```
 
-_See code: [src/commands/telemetry/enable.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.29.0/cli/src/commands/telemetry/enable.ts)_
+_See code: [src/commands/telemetry/enable.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.31.0/cli/src/commands/telemetry/enable.ts)_
 
 ## `lps theme add SLUG`
 
@@ -2497,7 +3502,7 @@ ARGUMENTS
 
 FLAGS
   -d, --dry-run          Show what would change without making changes
-      --env=<value>      Target environment by name, overriding the globally active one (lps project switch)
+      --env=<value>      Target environment by name (default: "local", or the project's only environment)
       --version=<value>  Exact version to pin (default: "latest")
 
 GLOBAL FLAGS
@@ -2512,7 +3517,7 @@ EXAMPLES
   $ lps theme add generatepress --version 3.4.0
 ```
 
-_See code: [src/commands/theme/add.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.29.0/cli/src/commands/theme/add.ts)_
+_See code: [src/commands/theme/add.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.31.0/cli/src/commands/theme/add.ts)_
 
 ## `lps theme pull`
 
@@ -2524,7 +3529,7 @@ USAGE
 
 FLAGS
   -d, --dry-run      Show what would change without making changes
-      --env=<value>  Target environment by name, overriding the globally active one (lps project switch)
+      --env=<value>  Target environment by name (default: "local", or the project's only environment)
 
 GLOBAL FLAGS
   --json  Format output as json.
@@ -2540,7 +3545,7 @@ EXAMPLES
   $ lps theme pull --dry-run
 ```
 
-_See code: [src/commands/theme/pull.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.29.0/cli/src/commands/theme/pull.ts)_
+_See code: [src/commands/theme/pull.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.31.0/cli/src/commands/theme/pull.ts)_
 
 ## `lps theme push`
 
@@ -2553,7 +3558,7 @@ USAGE
 FLAGS
   -d, --dry-run      Show what would change without making changes
   -y, --yes          Answer yes to confirmation prompts
-      --env=<value>  Target environment by name, overriding the globally active one (lps project switch)
+      --env=<value>  Target environment by name (default: "local", or the project's only environment)
       --force        Passed to `lps theme version push`
 
 GLOBAL FLAGS
@@ -2570,7 +3575,7 @@ EXAMPLES
   $ lps theme push --dry-run
 ```
 
-_See code: [src/commands/theme/push.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.29.0/cli/src/commands/theme/push.ts)_
+_See code: [src/commands/theme/push.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.31.0/cli/src/commands/theme/push.ts)_
 
 ## `lps theme status`
 
@@ -2581,7 +3586,7 @@ USAGE
   $ lps theme status [--json] [--env <value>]
 
 FLAGS
-  --env=<value>  Target environment by name, overriding the globally active one (lps project switch)
+  --env=<value>  Target environment by name (default: "local", or the project's only environment)
 
 GLOBAL FLAGS
   --json  Format output as json.
@@ -2593,7 +3598,7 @@ EXAMPLES
   $ lps theme status
 ```
 
-_See code: [src/commands/theme/status.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.29.0/cli/src/commands/theme/status.ts)_
+_See code: [src/commands/theme/status.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.31.0/cli/src/commands/theme/status.ts)_
 
 ## `lps theme style diff [PATH]`
 
@@ -2608,7 +3613,7 @@ ARGUMENTS
 
 FLAGS
   --against=<value>  Compare the primary environment against this second environment instead of against local files
-  --env=<value>      Target environment by name, overriding the globally active one (lps project switch)
+  --env=<value>      Target environment by name (default: "local", or the project's only environment)
 
 GLOBAL FLAGS
   --json  Format output as json.
@@ -2625,7 +3630,7 @@ EXAMPLES
   $ lps theme style diff --env staging --against production
 ```
 
-_See code: [src/commands/theme/style/diff.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.29.0/cli/src/commands/theme/style/diff.ts)_
+_See code: [src/commands/theme/style/diff.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.31.0/cli/src/commands/theme/style/diff.ts)_
 
 ## `lps theme style pull [PATH]`
 
@@ -2640,7 +3645,7 @@ ARGUMENTS
 
 FLAGS
   -d, --dry-run      Show what would change without making changes
-      --env=<value>  Target environment by name, overriding the globally active one (lps project switch)
+      --env=<value>  Target environment by name (default: "local", or the project's only environment)
 
 GLOBAL FLAGS
   --json  Format output as json.
@@ -2652,7 +3657,7 @@ EXAMPLES
   $ lps theme style pull
 ```
 
-_See code: [src/commands/theme/style/pull.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.29.0/cli/src/commands/theme/style/pull.ts)_
+_See code: [src/commands/theme/style/pull.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.31.0/cli/src/commands/theme/style/pull.ts)_
 
 ## `lps theme style push [PATH]`
 
@@ -2660,7 +3665,7 @@ Push the local Global Styles file to the active block theme's Site Editor > Styl
 
 ```
 USAGE
-  $ lps theme style push [PATH] [--json] [--env <value>] [-d] [-y]
+  $ lps theme style push [PATH] [--json] [--env <value>] [--overwrite] [-d] [-y]
 
 ARGUMENTS
   [PATH]  Path to theme styles directory (overrides project config)
@@ -2668,7 +3673,8 @@ ARGUMENTS
 FLAGS
   -d, --dry-run      Show what would change without making changes
   -y, --yes          Answer yes to confirmation prompts
-      --env=<value>  Target environment by name, overriding the globally active one (lps project switch)
+      --env=<value>  Target environment by name (default: "local", or the project's only environment)
+      --overwrite    Push even over changes made on the site outside Loopress since your last push
 
 GLOBAL FLAGS
   --json  Format output as json.
@@ -2680,7 +3686,7 @@ EXAMPLES
   $ lps theme style push
 ```
 
-_See code: [src/commands/theme/style/push.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.29.0/cli/src/commands/theme/style/push.ts)_
+_See code: [src/commands/theme/style/push.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.31.0/cli/src/commands/theme/style/push.ts)_
 
 ## `lps theme style rollback [PATH]`
 
@@ -2696,7 +3702,7 @@ ARGUMENTS
 FLAGS
   -d, --dry-run      Show what would change without making changes
   -y, --yes          Answer yes to confirmation prompts
-      --env=<value>  Target environment by name, overriding the globally active one (lps project switch)
+      --env=<value>  Target environment by name (default: "local", or the project's only environment)
       --list         List available snapshots instead of rolling back
       --to=<value>   Roll back to this snapshot id instead of the most recent one
 
@@ -2716,7 +3722,7 @@ EXAMPLES
   $ lps theme style rollback --dry-run
 ```
 
-_See code: [src/commands/theme/style/rollback.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.29.0/cli/src/commands/theme/style/rollback.ts)_
+_See code: [src/commands/theme/style/rollback.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.31.0/cli/src/commands/theme/style/rollback.ts)_
 
 ## `lps theme template diff`
 
@@ -2728,7 +3734,7 @@ USAGE
 
 FLAGS
   --against=<value>  Compare the primary environment against this second environment instead of against local files
-  --env=<value>      Target environment by name, overriding the globally active one (lps project switch)
+  --env=<value>      Target environment by name (default: "local", or the project's only environment)
 
 GLOBAL FLAGS
   --json  Format output as json.
@@ -2745,7 +3751,7 @@ EXAMPLES
   $ lps theme template diff --env staging --against production
 ```
 
-_See code: [src/commands/theme/template/diff.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.29.0/cli/src/commands/theme/template/diff.ts)_
+_See code: [src/commands/theme/template/diff.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.31.0/cli/src/commands/theme/template/diff.ts)_
 
 ## `lps theme template list`
 
@@ -2756,7 +3762,7 @@ USAGE
   $ lps theme template list [--json] [--env <value>]
 
 FLAGS
-  --env=<value>  Target environment by name, overriding the globally active one (lps project switch)
+  --env=<value>  Target environment by name (default: "local", or the project's only environment)
 
 GLOBAL FLAGS
   --json  Format output as json.
@@ -2768,28 +3774,30 @@ EXAMPLES
   $ lps theme template list
 ```
 
-_See code: [src/commands/theme/template/list.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.29.0/cli/src/commands/theme/template/list.ts)_
+_See code: [src/commands/theme/template/list.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.31.0/cli/src/commands/theme/template/list.ts)_
 
 ## `lps theme template push`
 
-Push block templates (templates/<slug>.html) and template parts (parts/<slug>.html) as the files of a child theme of the active block theme, <parent>-loopress. The child mirrors the project: files removed locally are removed from it. It is never activated for you.
+Push block templates (theme/templates/<slug>.html), template parts (theme/parts/<slug>.html) and the theme CSS (theme/css/style.css, theme/blocks/<namespace>/<block>.css, bundled with esbuild) as the files of a child theme of the active block theme, <parent>-loopress. The child mirrors the project: files removed locally are removed from it. It is never activated for you.
 
 ```
 USAGE
-  $ lps theme template push [--json] [--env <value>] [-d] [-y]
+  $ lps theme template push [--json] [--env <value>] [--overwrite] [-d] [-y]
 
 FLAGS
   -d, --dry-run      Show what would change without making changes
   -y, --yes          Answer yes to confirmation prompts
-      --env=<value>  Target environment by name, overriding the globally active one (lps project switch)
+      --env=<value>  Target environment by name (default: "local", or the project's only environment)
+      --overwrite    Push even over changes made on the site outside Loopress since your last push
 
 GLOBAL FLAGS
   --json  Format output as json.
 
 DESCRIPTION
-  Push block templates (templates/<slug>.html) and template parts (parts/<slug>.html) as the files of a child theme of
-  the active block theme, <parent>-loopress. The child mirrors the project: files removed locally are removed from it.
-  It is never activated for you.
+  Push block templates (theme/templates/<slug>.html), template parts (theme/parts/<slug>.html) and the theme CSS
+  (theme/css/style.css, theme/blocks/<namespace>/<block>.css, bundled with esbuild) as the files of a child theme of the
+  active block theme, <parent>-loopress. The child mirrors the project: files removed locally are removed from it. It is
+  never activated for you.
 
 EXAMPLES
   $ lps theme template push
@@ -2797,7 +3805,7 @@ EXAMPLES
   $ lps theme template push --dry-run
 ```
 
-_See code: [src/commands/theme/template/push.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.29.0/cli/src/commands/theme/template/push.ts)_
+_See code: [src/commands/theme/template/push.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.31.0/cli/src/commands/theme/template/push.ts)_
 
 ## `lps theme version pull`
 
@@ -2809,7 +3817,7 @@ USAGE
 
 FLAGS
   -d, --dry-run      Show what would change without making changes
-      --env=<value>  Target environment by name, overriding the globally active one (lps project switch)
+      --env=<value>  Target environment by name (default: "local", or the project's only environment)
 
 GLOBAL FLAGS
   --json  Format output as json.
@@ -2821,7 +3829,7 @@ EXAMPLES
   $ lps theme version pull
 ```
 
-_See code: [src/commands/theme/version/pull.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.29.0/cli/src/commands/theme/version/pull.ts)_
+_See code: [src/commands/theme/version/pull.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.31.0/cli/src/commands/theme/version/pull.ts)_
 
 ## `lps theme version push`
 
@@ -2829,13 +3837,14 @@ Install themes on WordPress to match loopress.json (versions only, never switche
 
 ```
 USAGE
-  $ lps theme version push [--json] [--env <value>] [-d] [-y] [--force]
+  $ lps theme version push [--json] [--env <value>] [--overwrite] [-d] [-y] [--force]
 
 FLAGS
   -d, --dry-run      Show what would change without making changes
   -y, --yes          Answer yes to confirmation prompts
-      --env=<value>  Target environment by name, overriding the globally active one (lps project switch)
+      --env=<value>  Target environment by name (default: "local", or the project's only environment)
       --force        Allow downgrades and take over themes installed outside Loopress
+      --overwrite    Push even over changes made on the site outside Loopress since your last push
 
 GLOBAL FLAGS
   --json  Format output as json.
@@ -2849,7 +3858,7 @@ EXAMPLES
   $ lps theme version push --force
 ```
 
-_See code: [src/commands/theme/version/push.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.29.0/cli/src/commands/theme/version/push.ts)_
+_See code: [src/commands/theme/version/push.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.31.0/cli/src/commands/theme/version/push.ts)_
 
 ## `lps validate`
 
@@ -2869,5 +3878,5 @@ EXAMPLES
   $ lps validate
 ```
 
-_See code: [src/commands/validate.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.29.0/cli/src/commands/validate.ts)_
+_See code: [src/commands/validate.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.31.0/cli/src/commands/validate.ts)_
 <!-- commandsstop -->