@loopress/cli 0.28.0 → 0.30.0

package/README.md

@@ -21,7 +21,7 @@ $ npm install -g @loopress/cli
 $ lps COMMAND
 running command...
 $ lps (--version)
-@loopress/cli/0.28.0 linux-x64 node-v24.21.0
+@loopress/cli/0.30.0 linux-x64 node-v24.21.0
 $ lps --help [COMMAND]
 USAGE
   $ lps COMMAND
@@ -57,6 +57,7 @@ report.
 * [`lps api publish [PATH]`](#lps-api-publish-path)
 * [`lps api pull [PATH]`](#lps-api-pull-path)
 * [`lps api push [PATH]`](#lps-api-push-path)
+* [`lps api remove FILENAME`](#lps-api-remove-filename)
 * [`lps api rm FILENAME`](#lps-api-rm-filename)
 * [`lps api rollback [PATH]`](#lps-api-rollback-path)
 * [`lps app list`](#lps-app-list)
@@ -66,6 +67,13 @@ report.
 * [`lps composer init`](#lps-composer-init)
 * [`lps composer pull`](#lps-composer-pull)
 * [`lps composer push`](#lps-composer-push)
+* [`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)
@@ -79,6 +87,7 @@ report.
 * [`lps hook list`](#lps-hook-list)
 * [`lps hook pull [PATH]`](#lps-hook-pull-path)
 * [`lps hook push [PATH]`](#lps-hook-push-path)
+* [`lps hook remove FILENAME`](#lps-hook-remove-filename)
 * [`lps hook rm FILENAME`](#lps-hook-rm-filename)
 * [`lps hook rollback [PATH]`](#lps-hook-rollback-path)
 * [`lps init`](#lps-init)
@@ -89,6 +98,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)
@@ -99,6 +115,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)
@@ -114,11 +137,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)
@@ -126,11 +151,15 @@ 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 template diff`](#lps-template-diff)
-* [`lps template list`](#lps-template-list)
-* [`lps template push`](#lps-template-push)
 * [`lps theme add SLUG`](#lps-theme-add-slug)
 * [`lps theme pull`](#lps-theme-pull)
 * [`lps theme push`](#lps-theme-push)
@@ -139,6 +168,11 @@ report.
 * [`lps theme style pull [PATH]`](#lps-theme-style-pull-path)
 * [`lps theme style push [PATH]`](#lps-theme-style-push-path)
 * [`lps theme style rollback [PATH]`](#lps-theme-style-rollback-path)
+* [`lps theme template diff`](#lps-theme-template-diff)
+* [`lps theme template list`](#lps-theme-template-list)
+* [`lps theme template push`](#lps-theme-template-push)
+* [`lps theme version pull`](#lps-theme-version-pull)
+* [`lps theme version push`](#lps-theme-version-push)
 * [`lps validate`](#lps-validate)
 
 ## `lps acf diff [PATH]`
@@ -154,7 +188,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.
@@ -171,7 +205,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.28.0/cli/src/commands/acf/diff.ts)_
+_See code: [src/commands/acf/diff.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.30.0/cli/src/commands/acf/diff.ts)_
 
 ## `lps acf list`
 
@@ -182,7 +216,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>
 
@@ -198,7 +232,7 @@ EXAMPLES
   $ lps acf list --type field-groups
 ```
 
-_See code: [src/commands/acf/list.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.28.0/cli/src/commands/acf/list.ts)_
+_See code: [src/commands/acf/list.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.30.0/cli/src/commands/acf/list.ts)_
 
 ## `lps acf pull [PATH]`
 
@@ -206,7 +240,8 @@ Pull ACF field groups, post types, taxonomies, and options pages from WordPress
 
 ```
 USAGE
-  $ lps acf pull [PATH] [--env <value>] [-d] [-y] [--type field-groups|post-types|taxonomies|options-pages...]
+  $ lps acf pull [PATH] [--json] [--env <value>] [-d] [-y] [--type
+    field-groups|post-types|taxonomies|options-pages...]
 
 ARGUMENTS
   [PATH]  Path to ACF directory (overrides project config)
@@ -214,10 +249,13 @@ 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>
 
+GLOBAL FLAGS
+  --json  Format output as json.
+
 DESCRIPTION
   Pull ACF field groups, post types, taxonomies, and options pages from WordPress
 
@@ -227,7 +265,7 @@ EXAMPLES
   $ lps acf pull --type field-groups
 ```
 
-_See code: [src/commands/acf/pull.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.28.0/cli/src/commands/acf/pull.ts)_
+_See code: [src/commands/acf/pull.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.30.0/cli/src/commands/acf/pull.ts)_
 
 ## `lps acf push [PATH]`
 
@@ -235,7 +273,8 @@ Push ACF field groups, post types, taxonomies, and options pages to WordPress
 
 ```
 USAGE
-  $ lps acf push [PATH] [--env <value>] [-d] [-y] [--type field-groups|post-types|taxonomies|options-pages...]
+  $ lps acf push [PATH] [--json] [--env <value>] [-d] [-y] [--type
+    field-groups|post-types|taxonomies|options-pages...]
 
 ARGUMENTS
   [PATH]  Path to ACF directory (overrides project config)
@@ -243,10 +282,13 @@ 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>
 
+GLOBAL FLAGS
+  --json  Format output as json.
+
 DESCRIPTION
   Push ACF field groups, post types, taxonomies, and options pages to WordPress
 
@@ -256,7 +298,7 @@ EXAMPLES
   $ lps acf push --type field-groups
 ```
 
-_See code: [src/commands/acf/push.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.28.0/cli/src/commands/acf/push.ts)_
+_See code: [src/commands/acf/push.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.30.0/cli/src/commands/acf/push.ts)_
 
 ## `lps acf rollback [PATH]`
 
@@ -272,7 +314,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
 
@@ -293,7 +335,7 @@ EXAMPLES
   $ lps acf rollback --dry-run
 ```
 
-_See code: [src/commands/acf/rollback.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.28.0/cli/src/commands/acf/rollback.ts)_
+_See code: [src/commands/acf/rollback.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.30.0/cli/src/commands/acf/rollback.ts)_
 
 ## `lps api diff [PATH]`
 
@@ -308,7 +350,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.
@@ -325,7 +367,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.28.0/cli/src/commands/api/diff.ts)_
+_See code: [src/commands/api/diff.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.30.0/cli/src/commands/api/diff.ts)_
 
 ## `lps api list`
 
@@ -336,7 +378,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.
@@ -348,7 +390,7 @@ EXAMPLES
   $ lps api list
 ```
 
-_See code: [src/commands/api/list.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.28.0/cli/src/commands/api/list.ts)_
+_See code: [src/commands/api/list.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.30.0/cli/src/commands/api/list.ts)_
 
 ## `lps api publish [PATH]`
 
@@ -368,10 +410,10 @@ DESCRIPTION
 EXAMPLES
   $ lps api publish
 
-  $ lps api publish --path ./api
+  $ lps api publish ./api
 ```
 
-_See code: [src/commands/api/publish.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.28.0/cli/src/commands/api/publish.ts)_
+_See code: [src/commands/api/publish.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.30.0/cli/src/commands/api/publish.ts)_
 
 ## `lps api pull [PATH]`
 
@@ -387,7 +429,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.
@@ -401,7 +443,7 @@ EXAMPLES
   $ lps api pull --path ./api
 ```
 
-_See code: [src/commands/api/pull.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.28.0/cli/src/commands/api/pull.ts)_
+_See code: [src/commands/api/pull.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.30.0/cli/src/commands/api/pull.ts)_
 
 ## `lps api push [PATH]`
 
@@ -417,7 +459,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)
       --prune        Delete server-side route files not present locally after pushing
 
 GLOBAL FLAGS
@@ -434,7 +476,38 @@ EXAMPLES
   $ lps api push --prune
 ```
 
-_See code: [src/commands/api/push.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.28.0/cli/src/commands/api/push.ts)_
+_See code: [src/commands/api/push.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.30.0/cli/src/commands/api/push.ts)_
+
+## `lps api remove FILENAME`
+
+Remove a custom API route file from WordPress
+
+```
+USAGE
+  $ lps api remove FILENAME [--json] [--env <value>] [-d] [-y]
+
+ARGUMENTS
+  FILENAME  The route file to remove, its slug without the .php extension (e.g. "hello" or "invoice-pdf/[order_id]")
+
+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
+  Remove a custom API route file from WordPress
+
+ALIASES
+  $ lps api remove
+
+EXAMPLES
+  $ lps api rm hello
+
+  $ lps api remove hello --yes
+```
 
 ## `lps api rm FILENAME`
 
@@ -450,7 +523,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.
@@ -458,13 +531,16 @@ GLOBAL FLAGS
 DESCRIPTION
   Remove a custom API route file from WordPress
 
+ALIASES
+  $ lps api remove
+
 EXAMPLES
   $ lps api rm hello
 
-  $ lps api rm hello --yes
+  $ lps api remove hello --yes
 ```
 
-_See code: [src/commands/api/rm.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.28.0/cli/src/commands/api/rm.ts)_
+_See code: [src/commands/api/rm.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.30.0/cli/src/commands/api/rm.ts)_
 
 ## `lps api rollback [PATH]`
 
@@ -480,7 +556,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
 
@@ -500,7 +576,7 @@ EXAMPLES
   $ lps api rollback --dry-run
 ```
 
-_See code: [src/commands/api/rollback.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.28.0/cli/src/commands/api/rollback.ts)_
+_See code: [src/commands/api/rollback.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.30.0/cli/src/commands/api/rollback.ts)_
 
 ## `lps app list`
 
@@ -511,7 +587,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.
@@ -523,7 +599,7 @@ EXAMPLES
   $ lps app list
 ```
 
-_See code: [src/commands/app/list.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.28.0/cli/src/commands/app/list.ts)_
+_See code: [src/commands/app/list.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.30.0/cli/src/commands/app/list.ts)_
 
 ## `lps app pull [PATH]`
 
@@ -539,7 +615,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.
@@ -551,7 +627,7 @@ EXAMPLES
   $ lps app pull
 ```
 
-_See code: [src/commands/app/pull.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.28.0/cli/src/commands/app/pull.ts)_
+_See code: [src/commands/app/pull.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.30.0/cli/src/commands/app/pull.ts)_
 
 ## `lps app push [NAME]`
 
@@ -568,7 +644,7 @@ 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)
 
 GLOBAL FLAGS
   --json  Format output as json.
@@ -586,7 +662,7 @@ EXAMPLES
   $ lps app push --no-build
 ```
 
-_See code: [src/commands/app/push.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.28.0/cli/src/commands/app/push.ts)_
+_See code: [src/commands/app/push.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.30.0/cli/src/commands/app/push.ts)_
 
 ## `lps app remove NAME`
 
@@ -602,7 +678,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.
@@ -615,7 +691,7 @@ EXAMPLES
   $ lps app remove search
 ```
 
-_See code: [src/commands/app/remove.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.28.0/cli/src/commands/app/remove.ts)_
+_See code: [src/commands/app/remove.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.30.0/cli/src/commands/app/remove.ts)_
 
 ## `lps composer init`
 
@@ -627,7 +703,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
@@ -638,7 +714,7 @@ EXAMPLES
   $ lps composer init --dry-run
 ```
 
-_See code: [src/commands/composer/init.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.28.0/cli/src/commands/composer/init.ts)_
+_See code: [src/commands/composer/init.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.30.0/cli/src/commands/composer/init.ts)_
 
 ## `lps composer pull`
 
@@ -650,7 +726,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.
@@ -664,7 +740,7 @@ EXAMPLES
   $ lps composer pull --dry-run
 ```
 
-_See code: [src/commands/composer/pull.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.28.0/cli/src/commands/composer/pull.ts)_
+_See code: [src/commands/composer/pull.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.30.0/cli/src/commands/composer/pull.ts)_
 
 ## `lps composer push`
 
@@ -677,7 +753,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        Allow downgrades and take over plugins/themes installed outside Loopress
 
 GLOBAL FLAGS
@@ -692,7 +768,223 @@ EXAMPLES
   $ lps composer push --dry-run
 ```
 
-_See code: [src/commands/composer/push.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.28.0/cli/src/commands/composer/push.ts)_
+_See code: [src/commands/composer/push.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.30.0/cli/src/commands/composer/push.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.30.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.30.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.30.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>] [-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
+  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.30.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.30.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.30.0/cli/src/commands/cpt/rollback.ts)_
 
 ## `lps dev`
 
@@ -703,9 +995,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"
@@ -719,34 +1012,37 @@ EXAMPLES
   $ lps dev --skip=plugins
 ```
 
-_See code: [src/commands/dev.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.28.0/cli/src/commands/dev.ts)_
+_See code: [src/commands/dev.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.30.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
@@ -760,7 +1056,7 @@ EXAMPLES
   $ lps diff --skip composer
 ```
 
-_See code: [src/commands/diff.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.28.0/cli/src/commands/diff.ts)_
+_See code: [src/commands/diff.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.30.0/cli/src/commands/diff.ts)_
 
 ## `lps doctor`
 
@@ -771,7 +1067,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.
@@ -785,7 +1081,7 @@ EXAMPLES
   $ lps doctor --env production
 ```
 
-_See code: [src/commands/doctor.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.28.0/cli/src/commands/doctor.ts)_
+_See code: [src/commands/doctor.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.30.0/cli/src/commands/doctor.ts)_
 
 ## `lps form diff [PATH]`
 
@@ -800,7 +1096,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.
@@ -816,7 +1112,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.28.0/cli/src/commands/form/diff.ts)_
+_See code: [src/commands/form/diff.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.30.0/cli/src/commands/form/diff.ts)_
 
 ## `lps form list`
 
@@ -827,7 +1123,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.
@@ -839,7 +1135,7 @@ EXAMPLES
   $ lps form list
 ```
 
-_See code: [src/commands/form/list.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.28.0/cli/src/commands/form/list.ts)_
+_See code: [src/commands/form/list.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.30.0/cli/src/commands/form/list.ts)_
 
 ## `lps form pull [PATH]`
 
@@ -847,7 +1143,7 @@ Pull forms from WordPress
 
 ```
 USAGE
-  $ lps form pull [PATH] [--env <value>] [-d] [-y]
+  $ lps form pull [PATH] [--json] [--env <value>] [-d] [-y]
 
 ARGUMENTS
   [PATH]  Path to forms directory (overrides project config)
@@ -855,7 +1151,10 @@ 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.
 
 DESCRIPTION
   Pull forms from WordPress
@@ -864,7 +1163,7 @@ EXAMPLES
   $ lps form pull
 ```
 
-_See code: [src/commands/form/pull.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.28.0/cli/src/commands/form/pull.ts)_
+_See code: [src/commands/form/pull.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.30.0/cli/src/commands/form/pull.ts)_
 
 ## `lps form push [PATH]`
 
@@ -872,7 +1171,7 @@ Push forms to WordPress. Local files created or updated remotely are renamed on
 
 ```
 USAGE
-  $ lps form push [PATH] [--env <value>] [-d] [-y] [--allow-notifications]
+  $ lps form push [PATH] [--json] [--env <value>] [-d] [-y] [--allow-notifications]
 
 ARGUMENTS
   [PATH]  Path to forms directory (overrides project config)
@@ -883,7 +1182,10 @@ 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)
+
+GLOBAL FLAGS
+  --json  Format output as json.
 
 DESCRIPTION
   Push forms to WordPress. Local files created or updated remotely are renamed on disk to the `<id>-<slug>.json`
@@ -895,7 +1197,7 @@ EXAMPLES
   $ lps form push --allow-notifications
 ```
 
-_See code: [src/commands/form/push.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.28.0/cli/src/commands/form/push.ts)_
+_See code: [src/commands/form/push.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.30.0/cli/src/commands/form/push.ts)_
 
 ## `lps form rollback [PATH]`
 
@@ -911,7 +1213,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
 
@@ -931,7 +1233,7 @@ EXAMPLES
   $ lps form rollback --dry-run
 ```
 
-_See code: [src/commands/form/rollback.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.28.0/cli/src/commands/form/rollback.ts)_
+_See code: [src/commands/form/rollback.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.30.0/cli/src/commands/form/rollback.ts)_
 
 ## `lps help [COMMAND]`
 
@@ -951,7 +1253,7 @@ DESCRIPTION
   Display help for lps.
 ```
 
-_See code: [@oclif/plugin-help](https://github.com/oclif/plugin-help/blob/7.0.0/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]`
 
@@ -966,7 +1268,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.
@@ -982,7 +1284,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.28.0/cli/src/commands/hook/diff.ts)_
+_See code: [src/commands/hook/diff.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.30.0/cli/src/commands/hook/diff.ts)_
 
 ## `lps hook list`
 
@@ -993,7 +1295,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.
@@ -1005,7 +1307,7 @@ EXAMPLES
   $ lps hook list
 ```
 
-_See code: [src/commands/hook/list.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.28.0/cli/src/commands/hook/list.ts)_
+_See code: [src/commands/hook/list.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.30.0/cli/src/commands/hook/list.ts)_
 
 ## `lps hook pull [PATH]`
 
@@ -1021,7 +1323,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.
@@ -1035,7 +1337,7 @@ EXAMPLES
   $ lps hook pull --path ./hooks
 ```
 
-_See code: [src/commands/hook/pull.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.28.0/cli/src/commands/hook/pull.ts)_
+_See code: [src/commands/hook/pull.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.30.0/cli/src/commands/hook/pull.ts)_
 
 ## `lps hook push [PATH]`
 
@@ -1051,7 +1353,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)
       --prune        Delete server-side hook files not present locally after pushing
 
 GLOBAL FLAGS
@@ -1068,7 +1370,38 @@ EXAMPLES
   $ lps hook push --prune
 ```
 
-_See code: [src/commands/hook/push.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.28.0/cli/src/commands/hook/push.ts)_
+_See code: [src/commands/hook/push.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.30.0/cli/src/commands/hook/push.ts)_
+
+## `lps hook remove FILENAME`
+
+Remove a hook file (action, filter, cron) from WordPress
+
+```
+USAGE
+  $ lps hook remove FILENAME [--json] [--env <value>] [-d] [-y]
+
+ARGUMENTS
+  FILENAME  The hook file to remove, its slug without the .php extension (e.g. "hello" or "invoice-pdf/[order_id]")
+
+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
+  Remove a hook file (action, filter, cron) from WordPress
+
+ALIASES
+  $ lps hook remove
+
+EXAMPLES
+  $ lps hook rm hello
+
+  $ lps hook remove hello --yes
+```
 
 ## `lps hook rm FILENAME`
 
@@ -1084,7 +1417,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.
@@ -1092,13 +1425,16 @@ GLOBAL FLAGS
 DESCRIPTION
   Remove a hook file (action, filter, cron) from WordPress
 
+ALIASES
+  $ lps hook remove
+
 EXAMPLES
   $ lps hook rm hello
 
-  $ lps hook rm hello --yes
+  $ lps hook remove hello --yes
 ```
 
-_See code: [src/commands/hook/rm.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.28.0/cli/src/commands/hook/rm.ts)_
+_See code: [src/commands/hook/rm.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.30.0/cli/src/commands/hook/rm.ts)_
 
 ## `lps hook rollback [PATH]`
 
@@ -1114,7 +1450,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
 
@@ -1134,7 +1470,7 @@ EXAMPLES
   $ lps hook rollback --dry-run
 ```
 
-_See code: [src/commands/hook/rollback.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.28.0/cli/src/commands/hook/rollback.ts)_
+_See code: [src/commands/hook/rollback.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.30.0/cli/src/commands/hook/rollback.ts)_
 
 ## `lps init`
 
@@ -1151,7 +1487,7 @@ EXAMPLES
   $ lps init
 ```
 
-_See code: [src/commands/init.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.28.0/cli/src/commands/init.ts)_
+_See code: [src/commands/init.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.30.0/cli/src/commands/init.ts)_
 
 ## `lps login`
 
@@ -1168,7 +1504,7 @@ EXAMPLES
   $ lps login
 ```
 
-_See code: [src/commands/login.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.28.0/cli/src/commands/login.ts)_
+_See code: [src/commands/login.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.30.0/cli/src/commands/login.ts)_
 
 ## `lps logout`
 
@@ -1185,7 +1521,7 @@ EXAMPLES
   $ lps logout
 ```
 
-_See code: [src/commands/logout.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.28.0/cli/src/commands/logout.ts)_
+_See code: [src/commands/logout.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.30.0/cli/src/commands/logout.ts)_
 
 ## `lps menu diff [PATH]`
 
@@ -1200,7 +1536,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.
@@ -1217,7 +1553,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.28.0/cli/src/commands/menu/diff.ts)_
+_See code: [src/commands/menu/diff.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.30.0/cli/src/commands/menu/diff.ts)_
 
 ## `lps menu list`
 
@@ -1228,7 +1564,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.
@@ -1240,7 +1576,7 @@ EXAMPLES
   $ lps menu list
 ```
 
-_See code: [src/commands/menu/list.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.28.0/cli/src/commands/menu/list.ts)_
+_See code: [src/commands/menu/list.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.30.0/cli/src/commands/menu/list.ts)_
 
 ## `lps menu pull [PATH]`
 
@@ -1248,7 +1584,7 @@ Pull nav menus and the active theme menu locations from WordPress
 
 ```
 USAGE
-  $ lps menu pull [PATH] [--env <value>] [-d] [-y]
+  $ lps menu pull [PATH] [--json] [--env <value>] [-d] [-y]
 
 ARGUMENTS
   [PATH]  Path to menus directory (overrides project config)
@@ -1256,7 +1592,10 @@ 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.
 
 DESCRIPTION
   Pull nav menus and the active theme menu locations from WordPress
@@ -1265,7 +1604,7 @@ EXAMPLES
   $ lps menu pull
 ```
 
-_See code: [src/commands/menu/pull.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.28.0/cli/src/commands/menu/pull.ts)_
+_See code: [src/commands/menu/pull.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.30.0/cli/src/commands/menu/pull.ts)_
 
 ## `lps menu push [PATH]`
 
@@ -1273,7 +1612,7 @@ Push local nav menus and the active theme menu locations to WordPress. Each menu
 
 ```
 USAGE
-  $ lps menu push [PATH] [--env <value>] [-d] [-y]
+  $ lps menu push [PATH] [--json] [--env <value>] [-d] [-y]
 
 ARGUMENTS
   [PATH]  Path to menus directory (overrides project config)
@@ -1281,7 +1620,10 @@ 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.
 
 DESCRIPTION
   Push local nav menus and the active theme menu locations to WordPress. Each menu's post_type/taxonomy items are
@@ -1292,7 +1634,7 @@ EXAMPLES
   $ lps menu push
 ```
 
-_See code: [src/commands/menu/push.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.28.0/cli/src/commands/menu/push.ts)_
+_See code: [src/commands/menu/push.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.30.0/cli/src/commands/menu/push.ts)_
 
 ## `lps menu rollback [PATH]`
 
@@ -1308,7 +1650,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
 
@@ -1328,92 +1670,308 @@ EXAMPLES
   $ lps menu rollback --dry-run
 ```
 
-_See code: [src/commands/menu/rollback.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.28.0/cli/src/commands/menu/rollback.ts)_
+_See code: [src/commands/menu/rollback.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.30.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.28.0/cli/src/commands/option/add.ts)_
+_See code: [src/commands/meta/diff.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.30.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.28.0/cli/src/commands/option/diff.ts)_
+_See code: [src/commands/meta/list.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.30.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 meta pull
+```
+
+_See code: [src/commands/meta/pull.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.30.0/cli/src/commands/meta/pull.ts)_
+
+## `lps meta push [PATH]`
+
+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 meta push [PATH] [--json] [--env <value>] [-d] [-y]
+
+ARGUMENTS
+  [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 (default: "local", or the project's only environment)
+
+GLOBAL FLAGS
+  --json  Format output as json.
+
+DESCRIPTION
+  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 meta push
+```
+
+_See code: [src/commands/meta/push.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.30.0/cli/src/commands/meta/push.ts)_
+
+## `lps meta remove SLUG`
+
+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 meta remove SLUG [--json] [--env <value>] [-d] [-y]
+
+ARGUMENTS
+  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 (default: "local", or the project's only environment)
+
+GLOBAL FLAGS
+  --json  Format output as json.
+
+DESCRIPTION
+  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 meta rm <slug>
+
+  $ lps meta remove <slug> --yes
+```
+
+## `lps meta rm SLUG`
+
+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 meta rm SLUG [--json] [--env <value>] [-d] [-y]
+
+ARGUMENTS
+  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 (default: "local", or the project's only environment)
+
+GLOBAL FLAGS
+  --json  Format output as json.
+
+DESCRIPTION
+  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 meta rm <slug>
+
+  $ lps meta remove <slug> --yes
+```
+
+_See code: [src/commands/meta/rm.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.30.0/cli/src/commands/meta/rm.ts)_
+
+## `lps meta rollback [PATH]`
+
+Restore post meta keys to a snapshot taken automatically before an earlier `lps meta push`
+
+```
+USAGE
+  $ lps meta rollback [PATH] [--json] [--env <value>] [-d] [-y] [--list] [--to <value>]
+
+ARGUMENTS
+  [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 (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 post meta keys to a snapshot taken automatically before an earlier `lps meta push`
+
+EXAMPLES
+  $ lps meta rollback
+
+  $ lps meta rollback --list
+
+  $ lps meta rollback --to 1732000000000
+
+  $ lps meta rollback --dry-run
+```
+
+_See code: [src/commands/meta/rollback.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.30.0/cli/src/commands/meta/rollback.ts)_
+
+## `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.30.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.30.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
@@ -1421,7 +1979,7 @@ EXAMPLES
   $ lps option list --no-core
 ```
 
-_See code: [src/commands/option/list.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.28.0/cli/src/commands/option/list.ts)_
+_See code: [src/commands/option/list.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.30.0/cli/src/commands/option/list.ts)_
 
 ## `lps option pull [PATH]`
 
@@ -1437,7 +1995,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.
@@ -1450,7 +2008,7 @@ EXAMPLES
   $ lps option pull
 ```
 
-_See code: [src/commands/option/pull.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.28.0/cli/src/commands/option/pull.ts)_
+_See code: [src/commands/option/pull.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.30.0/cli/src/commands/option/pull.ts)_
 
 ## `lps option push [PATH]`
 
@@ -1466,7 +2024,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.
@@ -1479,7 +2037,7 @@ EXAMPLES
   $ lps option push
 ```
 
-_See code: [src/commands/option/push.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.28.0/cli/src/commands/option/push.ts)_
+_See code: [src/commands/option/push.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.30.0/cli/src/commands/option/push.ts)_
 
 ## `lps option remove NAME`
 
@@ -1495,7 +2053,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)
       --local-only    Untrack locally without deleting the option on WordPress
       --path=<value>  Path to options directory (overrides project config)
 
@@ -1512,7 +2070,7 @@ EXAMPLES
   $ lps option remove wpseo_titles --local-only
 ```
 
-_See code: [src/commands/option/remove.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.28.0/cli/src/commands/option/remove.ts)_
+_See code: [src/commands/option/remove.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.30.0/cli/src/commands/option/remove.ts)_
 
 ## `lps option rollback [PATH]`
 
@@ -1528,7 +2086,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
 
@@ -1548,7 +2106,7 @@ EXAMPLES
   $ lps option rollback --dry-run
 ```
 
-_See code: [src/commands/option/rollback.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.28.0/cli/src/commands/option/rollback.ts)_
+_See code: [src/commands/option/rollback.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.30.0/cli/src/commands/option/rollback.ts)_
 
 ## `lps page diff [PATH]`
 
@@ -1563,7 +2121,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.
@@ -1579,7 +2137,7 @@ EXAMPLES
   $ lps page diff --env staging --against production
 ```
 
-_See code: [src/commands/page/diff.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.28.0/cli/src/commands/page/diff.ts)_
+_See code: [src/commands/page/diff.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.30.0/cli/src/commands/page/diff.ts)_
 
 ## `lps page list`
 
@@ -1590,7 +2148,7 @@ USAGE
   $ lps page 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.
@@ -1602,7 +2160,7 @@ EXAMPLES
   $ lps page list
 ```
 
-_See code: [src/commands/page/list.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.28.0/cli/src/commands/page/list.ts)_
+_See code: [src/commands/page/list.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.30.0/cli/src/commands/page/list.ts)_
 
 ## `lps page push [SLUG]`
 
@@ -1618,7 +2176,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.
@@ -1635,7 +2193,223 @@ EXAMPLES
   $ lps page push --dry-run
 ```
 
-_See code: [src/commands/page/push.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.28.0/cli/src/commands/page/push.ts)_
+_See code: [src/commands/page/push.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.30.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.30.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.30.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.30.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>] [-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
+  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 pattern push
+```
+
+_See code: [src/commands/pattern/push.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.30.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.
+
+```
+USAGE
+  $ lps pattern remove SLUG [--json] [--env <value>] [-d] [-y]
+
+ARGUMENTS
+  SLUG  The pattern slug, its patterns/ file name without .html
+
+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 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 pattern rm SLUG [--json] [--env <value>] [-d] [-y]
+
+ARGUMENTS
+  SLUG  The pattern slug, its patterns/ file name without .html
+
+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 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
+```
+
+_See code: [src/commands/pattern/rm.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.30.0/cli/src/commands/pattern/rm.ts)_
+
+## `lps pattern rollback [PATH]`
+
+Restore block patterns to a snapshot taken automatically before an earlier `lps pattern push`
+
+```
+USAGE
+  $ lps pattern rollback [PATH] [--json] [--env <value>] [-d] [-y] [--list] [--to <value>]
+
+ARGUMENTS
+  [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 (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 block patterns to a snapshot taken automatically before an earlier `lps pattern push`
+
+EXAMPLES
+  $ lps pattern rollback
+
+  $ lps pattern rollback --list
+
+  $ lps pattern rollback --to 1732000000000
+
+  $ lps pattern rollback --dry-run
+```
+
+_See code: [src/commands/pattern/rollback.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.30.0/cli/src/commands/pattern/rollback.ts)_
 
 ## `lps plugin add SLUG`
 
@@ -1650,7 +2424,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
@@ -1667,7 +2441,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.28.0/cli/src/commands/plugin/add.ts)_
+_See code: [src/commands/plugin/add.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.30.0/cli/src/commands/plugin/add.ts)_
 
 ## `lps plugin audit`
 
@@ -1678,7 +2452,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.
@@ -1690,33 +2464,37 @@ EXAMPLES
   $ lps plugin audit
 ```
 
-_See code: [src/commands/plugin/audit.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.28.0/cli/src/commands/plugin/audit.ts)_
+_See code: [src/commands/plugin/audit.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.30.0/cli/src/commands/plugin/audit.ts)_
 
 ## `lps plugin pull`
 
-Pull installed plugins from WordPress into loopress.json, pinned to their live versions
+Pull installed plugins from WordPress into loopress.json (or composer.json), pinned to their live versions. Plugins already tracked are refreshed; new ones are offered as a list to tick, so plugins that only belong on this environment (cache, security, backups) stay out of the project.
 
 ```
 USAGE
-  $ lps plugin pull [--json] [--env <value>] [-d]
+  $ lps plugin pull [--json] [--env <value>] [-d] [-y] [--plugin <value>...]
 
 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)
+  -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)
+      --plugin=<value>...  Start tracking this installed plugin too, without asking (repeatable)
 
 GLOBAL FLAGS
   --json  Format output as json.
 
 DESCRIPTION
-  Pull installed plugins from WordPress into loopress.json, pinned to their live versions
+  Pull installed plugins from WordPress into loopress.json (or composer.json), pinned to their live versions. Plugins
+  already tracked are refreshed; new ones are offered as a list to tick, so plugins that only belong on this environment
+  (cache, security, backups) stay out of the project.
 
 EXAMPLES
   $ lps plugin pull
 
-  $ lps plugin pull --dry-run
+  $ lps plugin pull --env production --plugin query-monitor
 ```
 
-_See code: [src/commands/plugin/pull.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.28.0/cli/src/commands/plugin/pull.ts)_
+_See code: [src/commands/plugin/pull.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.30.0/cli/src/commands/plugin/pull.ts)_
 
 ## `lps plugin push`
 
@@ -1731,7 +2509,7 @@ FLAGS
   -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)
       --prune        Deactivate plugins that are active on the site but absent from loopress.json (or composer.json)
 
@@ -1749,7 +2527,7 @@ EXAMPLES
   $ lps plugin push --force --prune
 ```
 
-_See code: [src/commands/plugin/push.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.28.0/cli/src/commands/plugin/push.ts)_
+_See code: [src/commands/plugin/push.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.30.0/cli/src/commands/plugin/push.ts)_
 
 ## `lps plugin status`
 
@@ -1760,7 +2538,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.
@@ -1772,7 +2550,7 @@ EXAMPLES
   $ lps plugin status
 ```
 
-_See code: [src/commands/plugin/status.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.28.0/cli/src/commands/plugin/status.ts)_
+_See code: [src/commands/plugin/status.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.30.0/cli/src/commands/plugin/status.ts)_
 
 ## `lps project config`
 
@@ -1790,7 +2568,7 @@ EXAMPLES
   $ lps project config
 ```
 
-_See code: [src/commands/project/config.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.28.0/cli/src/commands/project/config.ts)_
+_See code: [src/commands/project/config.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.30.0/cli/src/commands/project/config.ts)_
 
 ## `lps project list`
 
@@ -1810,7 +2588,7 @@ EXAMPLES
   $ lps project list
 ```
 
-_See code: [src/commands/project/list.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.28.0/cli/src/commands/project/list.ts)_
+_See code: [src/commands/project/list.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.30.0/cli/src/commands/project/list.ts)_
 
 ## `lps project pull`
 
@@ -1827,7 +2605,7 @@ EXAMPLES
   $ lps project pull
 ```
 
-_See code: [src/commands/project/pull.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.28.0/cli/src/commands/project/pull.ts)_
+_See code: [src/commands/project/pull.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.30.0/cli/src/commands/project/pull.ts)_
 
 ## `lps project push`
 
@@ -1847,7 +2625,7 @@ EXAMPLES
   $ lps project push
 ```
 
-_See code: [src/commands/project/push.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.28.0/cli/src/commands/project/push.ts)_
+_See code: [src/commands/project/push.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.30.0/cli/src/commands/project/push.ts)_
 
 ## `lps project remove`
 
@@ -1864,7 +2642,7 @@ EXAMPLES
   $ lps project remove
 ```
 
-_See code: [src/commands/project/remove.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.28.0/cli/src/commands/project/remove.ts)_
+_See code: [src/commands/project/remove.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.30.0/cli/src/commands/project/remove.ts)_
 
 ## `lps project rotate`
 
@@ -1875,7 +2653,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
@@ -1886,24 +2664,24 @@ EXAMPLES
   $ lps project rotate --env staging
 ```
 
-_See code: [src/commands/project/rotate.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.28.0/cli/src/commands/project/rotate.ts)_
+_See code: [src/commands/project/rotate.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.30.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.28.0/cli/src/commands/project/switch.ts)_
+_See code: [src/commands/project/switch.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.30.0/cli/src/commands/project/switch.ts)_
 
 ## `lps promote FROM TO`
 
@@ -1935,11 +2713,11 @@ EXAMPLES
   $ lps promote production staging --dry-run
 ```
 
-_See code: [src/commands/promote.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.28.0/cli/src/commands/promote.ts)_
+_See code: [src/commands/promote.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.30.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
@@ -1948,14 +2726,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
@@ -1965,11 +2743,11 @@ EXAMPLES
   $ lps pull --dry-run
 ```
 
-_See code: [src/commands/pull.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.28.0/cli/src/commands/pull.ts)_
+_See code: [src/commands/pull.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.30.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
@@ -1978,14 +2756,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
-  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
@@ -1995,139 +2773,202 @@ EXAMPLES
   $ lps push --dry-run
 ```
 
-_See code: [src/commands/push.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.28.0/cli/src/commands/push.ts)_
+_See code: [src/commands/push.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.30.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 roles between your local roles/ files and a WordPress environment, or between two environments
+
+EXAMPLES
+  $ lps role diff
+
+  $ lps role diff --env staging
+
+  $ lps role diff --env staging --against production
+```
+
+_See code: [src/commands/role/diff.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.30.0/cli/src/commands/role/diff.ts)_
+
+## `lps role list`
+
+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 role 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 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 role list
+```
+
+_See code: [src/commands/role/list.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.30.0/cli/src/commands/role/list.ts)_
+
+## `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
-  Show what differs in SEO settings, post meta, and redirects between your local files and a WordPress environment, or
-  between two environments
+  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 seo diff
-
-  $ lps seo diff --env staging
-
-  $ lps seo diff --env staging --against production
+  $ lps role pull
 ```
 
-_See code: [src/commands/seo/diff.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.28.0/cli/src/commands/seo/diff.ts)_
+_See code: [src/commands/role/pull.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.30.0/cli/src/commands/role/pull.ts)_
 
-## `lps seo list`
+## `lps role push [PATH]`
 
-List posts with SEO meta, and redirects if supported by the active SEO plugin, on 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 list [--json] [--env <value>] [--post-type <value>...]
+  $ lps role push [PATH] [--json] [--env <value>] [-d] [-y]
+
+ARGUMENTS
+  [PATH]  Path to the roles directory (overrides project config)
 
 FLAGS
-  --env=<value>           Target environment by name, overriding the globally active one (lps project switch)
-  --post-type=<value>...  Limit 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)
 
 GLOBAL FLAGS
   --json  Format output as json.
 
 DESCRIPTION
-  List posts with SEO meta, and redirects if supported by the active SEO plugin, on 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 list
-
-  $ lps seo list --post-type post
+  $ lps role push
 ```
 
-_See code: [src/commands/seo/list.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.28.0/cli/src/commands/seo/list.ts)_
+_See code: [src/commands/role/push.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.30.0/cli/src/commands/role/push.ts)_
 
-## `lps seo pull [PATH]`
+## `lps role remove SLUG`
 
-Pull SEO settings, post meta, and (if supported) redirects from WordPress
+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 pull [PATH] [--env <value>] [-d] [-y] [--post-type <value>...]
+  $ lps role remove 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
-      --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)
+
+GLOBAL FLAGS
+  --json  Format output as json.
 
 DESCRIPTION
-  Pull SEO settings, post meta, and (if supported) redirects from WordPress
+  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 pull
+  $ lps role rm <slug>
 
-  $ lps seo pull --post-type post --post-type page
+  $ lps role remove <slug> --yes
 ```
 
-_See code: [src/commands/seo/pull.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.28.0/cli/src/commands/seo/pull.ts)_
-
-## `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] [--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.28.0/cli/src/commands/seo/push.ts)_
+_See code: [src/commands/role/rm.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.30.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
 
@@ -2135,19 +2976,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.28.0/cli/src/commands/seo/rollback.ts)_
+_See code: [src/commands/role/rollback.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.30.0/cli/src/commands/role/rollback.ts)_
 
 ## `lps snippet diff [PATH]`
 
@@ -2162,7 +3003,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.
@@ -2178,7 +3019,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.28.0/cli/src/commands/snippet/diff.ts)_
+_See code: [src/commands/snippet/diff.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.30.0/cli/src/commands/snippet/diff.ts)_
 
 ## `lps snippet list`
 
@@ -2189,7 +3030,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.
@@ -2201,7 +3042,7 @@ EXAMPLES
   $ lps snippet list
 ```
 
-_See code: [src/commands/snippet/list.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.28.0/cli/src/commands/snippet/list.ts)_
+_See code: [src/commands/snippet/list.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.30.0/cli/src/commands/snippet/list.ts)_
 
 ## `lps snippet publish [PATH]`
 
@@ -2221,10 +3062,10 @@ DESCRIPTION
 EXAMPLES
   $ lps snippet publish
 
-  $ lps snippet publish --path ./snippets
+  $ lps snippet publish ./snippets
 ```
 
-_See code: [src/commands/snippet/publish.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.28.0/cli/src/commands/snippet/publish.ts)_
+_See code: [src/commands/snippet/publish.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.30.0/cli/src/commands/snippet/publish.ts)_
 
 ## `lps snippet pull [PATH]`
 
@@ -2240,7 +3081,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.
@@ -2251,10 +3092,10 @@ DESCRIPTION
 EXAMPLES
   $ lps snippet pull
 
-  $ lps snippet pull --path ./snippets
+  $ lps snippet pull ./snippets
 ```
 
-_See code: [src/commands/snippet/pull.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.28.0/cli/src/commands/snippet/pull.ts)_
+_See code: [src/commands/snippet/pull.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.30.0/cli/src/commands/snippet/pull.ts)_
 
 ## `lps snippet push [PATH]`
 
@@ -2270,7 +3111,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.
@@ -2282,10 +3123,10 @@ DESCRIPTION
 EXAMPLES
   $ lps snippet push
 
-  $ lps snippet push --path ./snippets
+  $ lps snippet push ./snippets
 ```
 
-_See code: [src/commands/snippet/push.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.28.0/cli/src/commands/snippet/push.ts)_
+_See code: [src/commands/snippet/push.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.30.0/cli/src/commands/snippet/push.ts)_
 
 ## `lps snippet rollback [PATH]`
 
@@ -2301,7 +3142,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
 
@@ -2321,7 +3162,7 @@ EXAMPLES
   $ lps snippet rollback --dry-run
 ```
 
-_See code: [src/commands/snippet/rollback.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.28.0/cli/src/commands/snippet/rollback.ts)_
+_See code: [src/commands/snippet/rollback.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.30.0/cli/src/commands/snippet/rollback.ts)_
 
 ## `lps status`
 
@@ -2346,122 +3187,257 @@ EXAMPLES
   $ lps status --env staging
 ```
 
-_See code: [src/commands/status.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.28.0/cli/src/commands/status.ts)_
+_See code: [src/commands/status.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.30.0/cli/src/commands/status.ts)_
 
-## `lps telemetry disable`
+## `lps taxonomy diff [PATH]`
 
-Disable error reporting to Sentry
+Show what differs in taxonomies between your local taxonomies/ files and a WordPress environment, or between two environments
 
 ```
 USAGE
-  $ lps telemetry disable
+  $ 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
-  Disable error reporting to Sentry
+  Show what differs in taxonomies between your local taxonomies/ files and a WordPress environment, or between two
+  environments
 
 EXAMPLES
-  $ lps telemetry disable
+  $ lps taxonomy diff
+
+  $ lps taxonomy diff --env staging
+
+  $ lps taxonomy diff --env staging --against production
 ```
 
-_See code: [src/commands/telemetry/disable.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.28.0/cli/src/commands/telemetry/disable.ts)_
+_See code: [src/commands/taxonomy/diff.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.30.0/cli/src/commands/taxonomy/diff.ts)_
 
-## `lps telemetry enable`
+## `lps taxonomy list`
 
-Enable error reporting to Sentry
+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 telemetry enable
+  $ 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
-  Enable error reporting to Sentry
+  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 telemetry enable
+  $ lps taxonomy list
 ```
 
-_See code: [src/commands/telemetry/enable.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.28.0/cli/src/commands/telemetry/enable.ts)_
+_See code: [src/commands/taxonomy/list.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.30.0/cli/src/commands/taxonomy/list.ts)_
 
-## `lps template diff`
+## `lps taxonomy pull [PATH]`
 
-Show what differs in block templates and parts between your local files and a WordPress environment, or between two environments. Templates and parts edited in the Site Editor show up too.
+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 template diff [--json] [--env <value>] [--against <value>]
+  $ lps taxonomy pull [PATH] [--json] [--env <value>] [-d] [-y]
+
+ARGUMENTS
+  [PATH]  Path to the 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, 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
-  Show what differs in block templates and parts between your local files and a WordPress environment, or between two
-  environments. Templates and parts edited in the Site Editor show up too.
+  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.30.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>] [-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
+  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 template diff
+  $ lps taxonomy push
+```
+
+_See code: [src/commands/taxonomy/push.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.30.0/cli/src/commands/taxonomy/push.ts)_
 
-  $ lps template diff --env staging
+## `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.
 
-  $ lps template diff --env staging --against production
 ```
+USAGE
+  $ lps taxonomy remove SLUG [--json] [--env <value>] [-d] [-y]
 
-_See code: [src/commands/template/diff.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.28.0/cli/src/commands/template/diff.ts)_
+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)
 
-## `lps template list`
+GLOBAL FLAGS
+  --json  Format output as json.
 
-Show the Loopress child theme of the active block theme: its templates, parts, and those edited in the Site Editor
+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 template list [--json] [--env <value>]
+  $ lps taxonomy rm SLUG [--json] [--env <value>] [-d] [-y]
+
+ARGUMENTS
+  SLUG  The taxonomy slug, its taxonomies/ file name without .json
 
 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
-  Show the Loopress child theme of the active block theme: its templates, parts, and those edited in the Site Editor
+  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 template list
+  $ lps taxonomy rm <slug>
+
+  $ lps taxonomy remove <slug> --yes
 ```
 
-_See code: [src/commands/template/list.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.28.0/cli/src/commands/template/list.ts)_
+_See code: [src/commands/taxonomy/rm.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.30.0/cli/src/commands/taxonomy/rm.ts)_
 
-## `lps template push`
+## `lps taxonomy rollback [PATH]`
 
-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.
+Restore taxonomies to a snapshot taken automatically before an earlier `lps taxonomy push`
 
 ```
 USAGE
-  $ lps template push [--json] [--env <value>] [-d] [-y]
+  $ 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, 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 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.
+  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.30.0/cli/src/commands/taxonomy/rollback.ts)_
+
+## `lps telemetry disable`
+
+Disable error reporting to Sentry
+
+```
+USAGE
+  $ lps telemetry disable
+
+DESCRIPTION
+  Disable error reporting to Sentry
 
 EXAMPLES
-  $ lps template push
+  $ lps telemetry disable
+```
+
+_See code: [src/commands/telemetry/disable.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.30.0/cli/src/commands/telemetry/disable.ts)_
 
-  $ lps template push --dry-run
+## `lps telemetry enable`
+
+Enable error reporting to Sentry
+
+```
+USAGE
+  $ lps telemetry enable
+
+DESCRIPTION
+  Enable error reporting to Sentry
+
+EXAMPLES
+  $ lps telemetry enable
 ```
 
-_See code: [src/commands/template/push.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.28.0/cli/src/commands/template/push.ts)_
+_See code: [src/commands/telemetry/enable.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.30.0/cli/src/commands/telemetry/enable.ts)_
 
 ## `lps theme add SLUG`
 
@@ -2476,7 +3452,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
@@ -2491,11 +3467,11 @@ 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.28.0/cli/src/commands/theme/add.ts)_
+_See code: [src/commands/theme/add.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.30.0/cli/src/commands/theme/add.ts)_
 
 ## `lps theme pull`
 
-Pull installed themes from WordPress into loopress.json, pinned to their live versions
+Pull everything theme related from WordPress: theme versions and Global Styles
 
 ```
 USAGE
@@ -2503,23 +3479,27 @@ 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.
 
 DESCRIPTION
-  Pull installed themes from WordPress into loopress.json, pinned to their live versions
+  Pull everything theme related from WordPress: theme versions and Global Styles
 
 EXAMPLES
   $ lps theme pull
+
+  $ lps theme pull --env staging
+
+  $ lps theme pull --dry-run
 ```
 
-_See code: [src/commands/theme/pull.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.28.0/cli/src/commands/theme/pull.ts)_
+_See code: [src/commands/theme/pull.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.30.0/cli/src/commands/theme/pull.ts)_
 
 ## `lps theme push`
 
-Install themes on WordPress to match loopress.json (versions only, never switches the active theme)
+Push everything theme related to WordPress: theme versions, templates and parts, then Global Styles
 
 ```
 USAGE
@@ -2528,22 +3508,24 @@ 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)
-      --force        Allow downgrades and take over themes installed outside Loopress
+      --env=<value>  Target environment by name (default: "local", or the project's only environment)
+      --force        Passed to `lps theme version push`
 
 GLOBAL FLAGS
   --json  Format output as json.
 
 DESCRIPTION
-  Install themes on WordPress to match loopress.json (versions only, never switches the active theme)
+  Push everything theme related to WordPress: theme versions, templates and parts, then Global Styles
 
 EXAMPLES
   $ lps theme push
 
-  $ lps theme push --force
+  $ lps theme push --env staging
+
+  $ lps theme push --dry-run
 ```
 
-_See code: [src/commands/theme/push.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.28.0/cli/src/commands/theme/push.ts)_
+_See code: [src/commands/theme/push.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.30.0/cli/src/commands/theme/push.ts)_
 
 ## `lps theme status`
 
@@ -2554,7 +3536,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.
@@ -2566,7 +3548,7 @@ EXAMPLES
   $ lps theme status
 ```
 
-_See code: [src/commands/theme/status.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.28.0/cli/src/commands/theme/status.ts)_
+_See code: [src/commands/theme/status.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.30.0/cli/src/commands/theme/status.ts)_
 
 ## `lps theme style diff [PATH]`
 
@@ -2581,7 +3563,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.
@@ -2598,7 +3580,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.28.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.30.0/cli/src/commands/theme/style/diff.ts)_
 
 ## `lps theme style pull [PATH]`
 
@@ -2606,14 +3588,17 @@ Pull the active block theme's Global Styles customizations (Site Editor > Styles
 
 ```
 USAGE
-  $ lps theme style pull [PATH] [--env <value>] [-d]
+  $ lps theme style pull [PATH] [--json] [--env <value>] [-d]
 
 ARGUMENTS
   [PATH]  Path to theme styles 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)
+      --env=<value>  Target environment by name (default: "local", or the project's only environment)
+
+GLOBAL FLAGS
+  --json  Format output as json.
 
 DESCRIPTION
   Pull the active block theme's Global Styles customizations (Site Editor > Styles) from WordPress into a local file
@@ -2622,7 +3607,7 @@ EXAMPLES
   $ lps theme style pull
 ```
 
-_See code: [src/commands/theme/style/pull.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.28.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.30.0/cli/src/commands/theme/style/pull.ts)_
 
 ## `lps theme style push [PATH]`
 
@@ -2630,14 +3615,18 @@ Push the local Global Styles file to the active block theme's Site Editor > Styl
 
 ```
 USAGE
-  $ lps theme style push [PATH] [--env <value>] [-d]
+  $ lps theme style push [PATH] [--json] [--env <value>] [-d] [-y]
 
 ARGUMENTS
   [PATH]  Path to theme styles 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)
+  -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 the local Global Styles file to the active block theme's Site Editor > Styles on WordPress
@@ -2646,7 +3635,7 @@ EXAMPLES
   $ lps theme style push
 ```
 
-_See code: [src/commands/theme/style/push.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.28.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.30.0/cli/src/commands/theme/style/push.ts)_
 
 ## `lps theme style rollback [PATH]`
 
@@ -2662,7 +3651,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
 
@@ -2682,7 +3671,141 @@ EXAMPLES
   $ lps theme style rollback --dry-run
 ```
 
-_See code: [src/commands/theme/style/rollback.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.28.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.30.0/cli/src/commands/theme/style/rollback.ts)_
+
+## `lps theme template diff`
+
+Show what differs in block templates and parts between your local files and a WordPress environment, or between two environments. Templates and parts edited in the Site Editor show up too.
+
+```
+USAGE
+  $ lps theme template diff [--json] [--env <value>] [--against <value>]
+
+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 templates and parts between your local files and a WordPress environment, or between two
+  environments. Templates and parts edited in the Site Editor show up too.
+
+EXAMPLES
+  $ lps theme template diff
+
+  $ lps theme template diff --env staging
+
+  $ 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.30.0/cli/src/commands/theme/template/diff.ts)_
+
+## `lps theme template list`
+
+Show the Loopress child theme of the active block theme: its templates, parts, and those edited in the Site Editor
+
+```
+USAGE
+  $ lps theme template 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
+  Show the Loopress child theme of the active block theme: its templates, parts, and those edited in the Site Editor
+
+EXAMPLES
+  $ lps theme template list
+```
+
+_See code: [src/commands/theme/template/list.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.30.0/cli/src/commands/theme/template/list.ts)_
+
+## `lps theme template push`
+
+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]
+
+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
+  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
+
+  $ lps theme template push --dry-run
+```
+
+_See code: [src/commands/theme/template/push.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.30.0/cli/src/commands/theme/template/push.ts)_
+
+## `lps theme version pull`
+
+Pull installed themes from WordPress into loopress.json, pinned to their live versions
+
+```
+USAGE
+  $ lps theme version pull [--json] [--env <value>] [-d]
+
+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)
+
+GLOBAL FLAGS
+  --json  Format output as json.
+
+DESCRIPTION
+  Pull installed themes from WordPress into loopress.json, pinned to their live versions
+
+EXAMPLES
+  $ lps theme version pull
+```
+
+_See code: [src/commands/theme/version/pull.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.30.0/cli/src/commands/theme/version/pull.ts)_
+
+## `lps theme version push`
+
+Install themes on WordPress to match loopress.json (versions only, never switches the active theme)
+
+```
+USAGE
+  $ lps theme version push [--json] [--env <value>] [-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 (default: "local", or the project's only environment)
+      --force        Allow downgrades and take over themes installed outside Loopress
+
+GLOBAL FLAGS
+  --json  Format output as json.
+
+DESCRIPTION
+  Install themes on WordPress to match loopress.json (versions only, never switches the active theme)
+
+EXAMPLES
+  $ lps theme version push
+
+  $ lps theme version push --force
+```
+
+_See code: [src/commands/theme/version/push.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.30.0/cli/src/commands/theme/version/push.ts)_
 
 ## `lps validate`
 
@@ -2702,5 +3825,5 @@ EXAMPLES
   $ lps validate
 ```
 
-_See code: [src/commands/validate.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.28.0/cli/src/commands/validate.ts)_
+_See code: [src/commands/validate.ts](https://github.com/loopress/loopress/blob/%40loopress%2Fcli%400.30.0/cli/src/commands/validate.ts)_
 <!-- commandsstop -->