postman-cli-completion 1.75.0 → 1.77.0

package/completions/fish/postman.fish

@@ -1,4 +1,4 @@
-# Fish completion for Postman CLI (postman v1.75.0)
+# Fish completion for Postman CLI (postman v1.77.0)
 # Auto-generated by scripts/generate.mjs — DO NOT EDIT
 # Source: spec/commands.json
 # https://github.com/yokawasa/postman-cli-completion
@@ -75,25 +75,27 @@ complete -c postman -n '__fish_seen_subcommand_from api; and __fish_seen_subcomm
 complete -c postman -n '__fish_seen_subcommand_from api; and __fish_seen_subcommand_from publish' -s h -l help -d 'display help for command'
 
 # ---------- collection ----------
-complete -c postman -n '__postman_using_subcommand collection new migrate lint ai-readiness get delete publish generate sync request folder example import list run' -a new -d 'Scaffold a v3 collection on disk, or create one in a cloud Postman workspace with --workspace.'
-complete -c postman -n '__postman_using_subcommand collection new migrate lint ai-readiness get delete publish generate sync request folder example import list run' -a migrate -d 'Migrate a v2.1 collection to the v3 format'
-complete -c postman -n '__postman_using_subcommand collection new migrate lint ai-readiness get delete publish generate sync request folder example import list run' -a lint -d 'Run linting on a local v3 collection at the given file or directory path.'
-complete -c postman -n '__postman_using_subcommand collection new migrate lint ai-readiness get delete publish generate sync request folder example import list run' -a ai-readiness -d 'Score a Postman collection for AI readiness by ID, local file path, or local-mode directory.'
-complete -c postman -n '__postman_using_subcommand collection new migrate lint ai-readiness get delete publish generate sync request folder example import list run' -a get -d 'Fetch a Postman collection in the V3 format and print it.'
-complete -c postman -n '__postman_using_subcommand collection new migrate lint ai-readiness get delete publish generate sync request folder example import list run' -a delete -d 'Delete a cloud collection by id or a local collection directory by path. Prompts unless --yes is passed.'
-complete -c postman -n '__postman_using_subcommand collection new migrate lint ai-readiness get delete publish generate sync request folder example import list run' -a publish -d 'Publish a cloud collection\'s documentation (or request Community Manager approval).'
-complete -c postman -n '__postman_using_subcommand collection new migrate lint ai-readiness get delete publish generate sync request folder example import list run' -a generate -d 'Generate artifacts from a collection.'
-complete -c postman -n '__postman_using_subcommand collection new migrate lint ai-readiness get delete publish generate sync request folder example import list run' -a sync -d 'Sync artifacts generated from a collection.'
-complete -c postman -n '__postman_using_subcommand collection new migrate lint ai-readiness get delete publish generate sync request folder example import list run' -a request -d 'Add, get, update, or remove requests in a local v3 collection.'
-complete -c postman -n '__postman_using_subcommand collection new migrate lint ai-readiness get delete publish generate sync request folder example import list run' -a folder -d 'Add, get, update, or remove folders in a local v3 collection.'
-complete -c postman -n '__postman_using_subcommand collection new migrate lint ai-readiness get delete publish generate sync request folder example import list run' -a example -d 'Add, update, remove, get, or list examples (saved responses) under a request.'
-complete -c postman -n '__postman_using_subcommand collection new migrate lint ai-readiness get delete publish generate sync request folder example import list run' -a import -d 'Import a cURL or HAR source into a v3 collection (local, or cloud with --workspace).'
-complete -c postman -n '__postman_using_subcommand collection new migrate lint ai-readiness get delete publish generate sync request folder example import list run' -a list -d 'List collections: your local project\'s collections by default, or a Postman cloud workspace\'s collections with --workspace.'
-complete -c postman -n '__postman_using_subcommand collection new migrate lint ai-readiness get delete publish generate sync request folder example import list run' -a run -d 'Initiate a Postman collection run from a given ID or path.'
+complete -c postman -n '__postman_using_subcommand collection new migrate lint ai-readiness get delete publish generate sync share request folder example import list run' -a new -d 'Scaffold a v3 collection on disk, or create one in a cloud Postman workspace with --workspace.'
+complete -c postman -n '__postman_using_subcommand collection new migrate lint ai-readiness get delete publish generate sync share request folder example import list run' -a migrate -d 'Migrate a v2.1 collection to the v3 format'
+complete -c postman -n '__postman_using_subcommand collection new migrate lint ai-readiness get delete publish generate sync share request folder example import list run' -a lint -d 'Run linting on a local v3 collection at the given file or directory path.'
+complete -c postman -n '__postman_using_subcommand collection new migrate lint ai-readiness get delete publish generate sync share request folder example import list run' -a ai-readiness -d 'Score a Postman collection for AI readiness by ID, local file path, or local-mode directory.'
+complete -c postman -n '__postman_using_subcommand collection new migrate lint ai-readiness get delete publish generate sync share request folder example import list run' -a get -d 'Fetch a Postman collection in the V3 format and print it.'
+complete -c postman -n '__postman_using_subcommand collection new migrate lint ai-readiness get delete publish generate sync share request folder example import list run' -a delete -d 'Delete a cloud collection by id or a local collection directory by path. Prompts unless --yes is passed.'
+complete -c postman -n '__postman_using_subcommand collection new migrate lint ai-readiness get delete publish generate sync share request folder example import list run' -a publish -d 'Publish a cloud collection\'s documentation (or request Community Manager approval).'
+complete -c postman -n '__postman_using_subcommand collection new migrate lint ai-readiness get delete publish generate sync share request folder example import list run' -a generate -d 'Generate artifacts from a collection.'
+complete -c postman -n '__postman_using_subcommand collection new migrate lint ai-readiness get delete publish generate sync share request folder example import list run' -a sync -d 'Sync artifacts generated from a collection.'
+complete -c postman -n '__postman_using_subcommand collection new migrate lint ai-readiness get delete publish generate sync share request folder example import list run' -a share -d 'Grant a role on a collection to one or more people.'
+complete -c postman -n '__postman_using_subcommand collection new migrate lint ai-readiness get delete publish generate sync share request folder example import list run' -a request -d 'Add, get, update, or remove requests in a local v3 collection.'
+complete -c postman -n '__postman_using_subcommand collection new migrate lint ai-readiness get delete publish generate sync share request folder example import list run' -a folder -d 'Add, get, update, or remove folders in a local v3 collection.'
+complete -c postman -n '__postman_using_subcommand collection new migrate lint ai-readiness get delete publish generate sync share request folder example import list run' -a example -d 'Add, update, remove, get, or list examples (saved responses) under a request.'
+complete -c postman -n '__postman_using_subcommand collection new migrate lint ai-readiness get delete publish generate sync share request folder example import list run' -a import -d 'Import a cURL or HAR source into a v3 collection (local, or cloud with --workspace).'
+complete -c postman -n '__postman_using_subcommand collection new migrate lint ai-readiness get delete publish generate sync share request folder example import list run' -a list -d 'List collections: your local project\'s collections by default, or a Postman cloud workspace\'s collections with --workspace.'
+complete -c postman -n '__postman_using_subcommand collection new migrate lint ai-readiness get delete publish generate sync share request folder example import list run' -a run -d 'Initiate a Postman collection run from a given ID or path.'
 complete -c postman -n '__fish_seen_subcommand_from collection' -s h -l help -d 'display help for command'
 # ---------- collection new ----------
 complete -c postman -n '__fish_seen_subcommand_from collection; and __fish_seen_subcommand_from new' -s w -l workspace -d 'Create the collection in a cloud Postman workspace instead of scaffolding it locally. Required when the current directory is not a local Postman workspace.' -x
 complete -c postman -n '__fish_seen_subcommand_from collection; and __fish_seen_subcommand_from new' -l force -d 'Rewrite the definition of an existing local collection. Existing request files are left alone.'
+complete -c postman -n '__fish_seen_subcommand_from collection; and __fish_seen_subcommand_from new' -s m -l message -d 'Short note on what changed, like a commit message (max 500 characters). Shown on the workspace activity feed. Cloud mode (--workspace) only.' -x
 complete -c postman -n '__fish_seen_subcommand_from collection; and __fish_seen_subcommand_from new' -l verbose -d 'Verbose output'
 complete -c postman -n '__fish_seen_subcommand_from collection; and __fish_seen_subcommand_from new' -l json -d 'JSON output'
 complete -c postman -n '__fish_seen_subcommand_from collection; and __fish_seen_subcommand_from new' -s h -l help -d 'display help for command'
@@ -119,6 +121,7 @@ complete -c postman -n '__fish_seen_subcommand_from collection; and __fish_seen_
 # ---------- collection delete ----------
 complete -c postman -n '__fish_seen_subcommand_from collection; and __fish_seen_subcommand_from delete' -s y -l yes -d 'Delete without asking for confirmation first'
 complete -c postman -n '__fish_seen_subcommand_from collection; and __fish_seen_subcommand_from delete' -l api-key -d 'Postman API key, used when deleting a cloud collection' -r
+complete -c postman -n '__fish_seen_subcommand_from collection; and __fish_seen_subcommand_from delete' -s m -l message -d 'Short note on why, like a commit message (max 500 characters). Shown on the workspace activity feed. Cloud collections only.' -x
 complete -c postman -n '__fish_seen_subcommand_from collection; and __fish_seen_subcommand_from delete' -l verbose -d 'Verbose output'
 complete -c postman -n '__fish_seen_subcommand_from collection; and __fish_seen_subcommand_from delete' -l json -d 'Output the result as JSON'
 complete -c postman -n '__fish_seen_subcommand_from collection; and __fish_seen_subcommand_from delete' -s h -l help -d 'display help for command'
@@ -150,6 +153,13 @@ complete -c postman -n '__fish_seen_subcommand_from collection; and __fish_seen_
 complete -c postman -n '__fish_seen_subcommand_from collection; and __fish_seen_subcommand_from sync; and __fish_seen_subcommand_from spec' -l api-key -d 'Postman API key' -r
 complete -c postman -n '__fish_seen_subcommand_from collection; and __fish_seen_subcommand_from sync; and __fish_seen_subcommand_from spec' -s h -l help -d 'display help for command'
 complete -c postman -n '__fish_seen_subcommand_from collection; and __fish_seen_subcommand_from sync; and __fish_seen_subcommand_from spec' -r -k -a '(__fish_complete_suffix .json)'
+# ---------- collection share ----------
+complete -c postman -n '__fish_seen_subcommand_from collection; and __fish_seen_subcommand_from share' -l user -d 'Who to share with. Repeatable, and each value may be a comma-separated list. A value containing @ is treated as an email address, anything else as a Postman user id.' -x
+complete -c postman -n '__fish_seen_subcommand_from collection; and __fish_seen_subcommand_from share' -l role -d 'The role to grant. (default: "viewer")' -x
+complete -c postman -n '__fish_seen_subcommand_from collection; and __fish_seen_subcommand_from share' -l json -d 'Print the outcome as machine-readable JSON.'
+complete -c postman -n '__fish_seen_subcommand_from collection; and __fish_seen_subcommand_from share' -l timeout -d 'Milliseconds to wait for Postman. Defaults to 30000.' -x
+complete -c postman -n '__fish_seen_subcommand_from collection; and __fish_seen_subcommand_from share' -l api-key -d 'Postman API key (defaults to your `postman login` session)' -r
+complete -c postman -n '__fish_seen_subcommand_from collection; and __fish_seen_subcommand_from share' -s h -l help -d 'display help for command'
 # ---------- collection request ----------
 complete -c postman -n '__postman_using_subcommand request add get update rm remove' -a add -d 'Add an empty request to a local v3 collection (set its details later with `update`).'
 complete -c postman -n '__postman_using_subcommand request add get update rm remove' -a get -d 'Show a request (any type) in a v3 collection: its own fields, with examples and messages as references.'
@@ -162,6 +172,7 @@ complete -c postman -n '__fish_seen_subcommand_from collection; and __fish_seen_
 complete -c postman -n '__fish_seen_subcommand_from collection; and __fish_seen_subcommand_from request; and __fish_seen_subcommand_from add' -l folder -d 'Folder within the collection, e.g. "Users/Admin". Defaults to the root.' -x
 complete -c postman -n '__fish_seen_subcommand_from collection; and __fish_seen_subcommand_from request; and __fish_seen_subcommand_from add' -l type -d 'Request type: http, graphql, grpc, websocket, socketio. (default: "http")' -x
 complete -c postman -n '__fish_seen_subcommand_from collection; and __fish_seen_subcommand_from request; and __fish_seen_subcommand_from add' -s w -l workspace -d 'Target a Postman cloud workspace by id (cloud mode).' -x
+complete -c postman -n '__fish_seen_subcommand_from collection; and __fish_seen_subcommand_from request; and __fish_seen_subcommand_from add' -s m -l message -d 'Short note on what changed, like a commit message (max 500 characters). Shown on the workspace activity feed. Cloud mode only.' -x
 complete -c postman -n '__fish_seen_subcommand_from collection; and __fish_seen_subcommand_from request; and __fish_seen_subcommand_from add' -l json -d 'JSON output.'
 complete -c postman -n '__fish_seen_subcommand_from collection; and __fish_seen_subcommand_from request; and __fish_seen_subcommand_from add' -s h -l help -d 'display help for command'
 # ---------- collection request get ----------
@@ -186,6 +197,7 @@ complete -c postman -n '__fish_seen_subcommand_from collection; and __fish_seen_
 complete -c postman -n '__fish_seen_subcommand_from collection; and __fish_seen_subcommand_from request; and __fish_seen_subcommand_from update' -l scripts -d 'Replace scripts. event is prerequest or test; script is @file, - for stdin, or inline. Repeatable; any request type. (default: [])' -x
 complete -c postman -n '__fish_seen_subcommand_from collection; and __fish_seen_subcommand_from request; and __fish_seen_subcommand_from update' -s w -l workspace -d 'Target a Postman cloud workspace by id (cloud mode).' -x
 complete -c postman -n '__fish_seen_subcommand_from collection; and __fish_seen_subcommand_from request; and __fish_seen_subcommand_from update' -l type -d 'Request type for cloud mode: http, graphql, grpc, websocket, socketio. (default: "http")' -x
+complete -c postman -n '__fish_seen_subcommand_from collection; and __fish_seen_subcommand_from request; and __fish_seen_subcommand_from update' -s m -l message -d 'Short note on what changed, like a commit message (max 500 characters). Shown on the workspace activity feed. Cloud mode only.' -x
 complete -c postman -n '__fish_seen_subcommand_from collection; and __fish_seen_subcommand_from request; and __fish_seen_subcommand_from update' -l json -d 'JSON output.'
 complete -c postman -n '__fish_seen_subcommand_from collection; and __fish_seen_subcommand_from request; and __fish_seen_subcommand_from update' -s h -l help -d 'display help for command'
 # ---------- collection request rm ----------
@@ -193,6 +205,7 @@ complete -c postman -n '__fish_seen_subcommand_from collection; and __fish_seen_
 complete -c postman -n '__fish_seen_subcommand_from collection; and __fish_seen_subcommand_from request; and __fish_seen_subcommand_from rm' -l folder -d 'Folder to scope the request selector, e.g. "Users/Admin" (local: name/path; cloud: id).' -x
 complete -c postman -n '__fish_seen_subcommand_from collection; and __fish_seen_subcommand_from request; and __fish_seen_subcommand_from rm' -s w -l workspace -d 'Target a Postman cloud workspace by id (cloud mode).' -x
 complete -c postman -n '__fish_seen_subcommand_from collection; and __fish_seen_subcommand_from request; and __fish_seen_subcommand_from rm' -l type -d 'Request type for cloud mode: http, graphql, grpc, websocket, socketio. (default: "http")' -x
+complete -c postman -n '__fish_seen_subcommand_from collection; and __fish_seen_subcommand_from request; and __fish_seen_subcommand_from rm' -s m -l message -d 'Short note on what changed, like a commit message (max 500 characters). Shown on the workspace activity feed. Cloud mode only.' -x
 complete -c postman -n '__fish_seen_subcommand_from collection; and __fish_seen_subcommand_from request; and __fish_seen_subcommand_from rm' -l json -d 'JSON output.'
 complete -c postman -n '__fish_seen_subcommand_from collection; and __fish_seen_subcommand_from request; and __fish_seen_subcommand_from rm' -s h -l help -d 'display help for command'
 # ---------- collection folder ----------
@@ -206,6 +219,7 @@ complete -c postman -n '__fish_seen_subcommand_from collection; and __fish_seen_
 complete -c postman -n '__fish_seen_subcommand_from collection; and __fish_seen_subcommand_from folder; and __fish_seen_subcommand_from add' -l collection -d 'Target collection: name, directory, id, cloud id, or path. Required.' -x
 complete -c postman -n '__fish_seen_subcommand_from collection; and __fish_seen_subcommand_from folder; and __fish_seen_subcommand_from add' -l folder -d 'Parent folder within the collection, e.g. "Users/Admin". Defaults to the root.' -x
 complete -c postman -n '__fish_seen_subcommand_from collection; and __fish_seen_subcommand_from folder; and __fish_seen_subcommand_from add' -s w -l workspace -d 'Target a Postman cloud workspace by id (cloud mode).' -x
+complete -c postman -n '__fish_seen_subcommand_from collection; and __fish_seen_subcommand_from folder; and __fish_seen_subcommand_from add' -s m -l message -d 'Short note on what changed, like a commit message (max 500 characters). Shown on the workspace activity feed. Cloud mode only.' -x
 complete -c postman -n '__fish_seen_subcommand_from collection; and __fish_seen_subcommand_from folder; and __fish_seen_subcommand_from add' -l json -d 'JSON output.'
 complete -c postman -n '__fish_seen_subcommand_from collection; and __fish_seen_subcommand_from folder; and __fish_seen_subcommand_from add' -s h -l help -d 'display help for command'
 # ---------- collection folder get ----------
@@ -222,6 +236,7 @@ complete -c postman -n '__fish_seen_subcommand_from collection; and __fish_seen_
 complete -c postman -n '__fish_seen_subcommand_from collection; and __fish_seen_subcommand_from folder; and __fish_seen_subcommand_from update' -l auth -d 'Folder auth: none, inherit, bearer:TOKEN, basic:USER:PASS, apikey:KEY:VALUE[:header|query], oauth2:TOKEN.' -x
 complete -c postman -n '__fish_seen_subcommand_from collection; and __fish_seen_subcommand_from folder; and __fish_seen_subcommand_from update' -l scripts -d 'Replace folder scripts. event is prerequest or test; script is @file, - for stdin, or inline. Repeatable. (default: [])' -x
 complete -c postman -n '__fish_seen_subcommand_from collection; and __fish_seen_subcommand_from folder; and __fish_seen_subcommand_from update' -s w -l workspace -d 'Target a Postman cloud workspace by id (cloud mode).' -x
+complete -c postman -n '__fish_seen_subcommand_from collection; and __fish_seen_subcommand_from folder; and __fish_seen_subcommand_from update' -s m -l message -d 'Short note on what changed, like a commit message (max 500 characters). Shown on the workspace activity feed. Cloud mode only.' -x
 complete -c postman -n '__fish_seen_subcommand_from collection; and __fish_seen_subcommand_from folder; and __fish_seen_subcommand_from update' -l json -d 'JSON output.'
 complete -c postman -n '__fish_seen_subcommand_from collection; and __fish_seen_subcommand_from folder; and __fish_seen_subcommand_from update' -s h -l help -d 'display help for command'
 # ---------- collection folder rm ----------
@@ -229,6 +244,7 @@ complete -c postman -n '__fish_seen_subcommand_from collection; and __fish_seen_
 complete -c postman -n '__fish_seen_subcommand_from collection; and __fish_seen_subcommand_from folder; and __fish_seen_subcommand_from rm' -l folder -d 'Parent folder to scope the selector, e.g. "Users" (local: name/path; cloud: id).' -x
 complete -c postman -n '__fish_seen_subcommand_from collection; and __fish_seen_subcommand_from folder; and __fish_seen_subcommand_from rm' -s y -l yes -d 'Skip the confirmation prompt (required when stdout is not a TTY).'
 complete -c postman -n '__fish_seen_subcommand_from collection; and __fish_seen_subcommand_from folder; and __fish_seen_subcommand_from rm' -s w -l workspace -d 'Target a Postman cloud workspace by id (cloud mode).' -x
+complete -c postman -n '__fish_seen_subcommand_from collection; and __fish_seen_subcommand_from folder; and __fish_seen_subcommand_from rm' -s m -l message -d 'Short note on what changed, like a commit message (max 500 characters). Shown on the workspace activity feed. Cloud mode only.' -x
 complete -c postman -n '__fish_seen_subcommand_from collection; and __fish_seen_subcommand_from folder; and __fish_seen_subcommand_from rm' -l json -d 'JSON output.'
 complete -c postman -n '__fish_seen_subcommand_from collection; and __fish_seen_subcommand_from folder; and __fish_seen_subcommand_from rm' -s h -l help -d 'display help for command'
 # ---------- collection example ----------
@@ -245,6 +261,7 @@ complete -c postman -n '__fish_seen_subcommand_from collection; and __fish_seen_
 complete -c postman -n '__fish_seen_subcommand_from collection; and __fish_seen_subcommand_from example; and __fish_seen_subcommand_from add' -l folder -d 'Folder to scope the request selector, e.g. "Users/Admin".' -x
 complete -c postman -n '__fish_seen_subcommand_from collection; and __fish_seen_subcommand_from example; and __fish_seen_subcommand_from add' -l type -d 'Example type: http (default). (default: "http")' -x
 complete -c postman -n '__fish_seen_subcommand_from collection; and __fish_seen_subcommand_from example; and __fish_seen_subcommand_from add' -s w -l workspace -d 'Target a Postman cloud workspace by id (cloud mode).' -x
+complete -c postman -n '__fish_seen_subcommand_from collection; and __fish_seen_subcommand_from example; and __fish_seen_subcommand_from add' -s m -l message -d 'Short note on what changed, like a commit message (max 500 characters). Shown on the workspace activity feed. Cloud mode only.' -x
 complete -c postman -n '__fish_seen_subcommand_from collection; and __fish_seen_subcommand_from example; and __fish_seen_subcommand_from add' -l json -d 'JSON output.'
 complete -c postman -n '__fish_seen_subcommand_from collection; and __fish_seen_subcommand_from example; and __fish_seen_subcommand_from add' -s h -l help -d 'display help for command'
 # ---------- collection example update ----------
@@ -266,6 +283,7 @@ complete -c postman -n '__fish_seen_subcommand_from collection; and __fish_seen_
 complete -c postman -n '__fish_seen_subcommand_from collection; and __fish_seen_subcommand_from example; and __fish_seen_subcommand_from update' -l clear-request -d 'Remove the example.request snapshot.'
 complete -c postman -n '__fish_seen_subcommand_from collection; and __fish_seen_subcommand_from example; and __fish_seen_subcommand_from update' -s w -l workspace -d 'Target a Postman cloud workspace by id (cloud mode).' -x
 complete -c postman -n '__fish_seen_subcommand_from collection; and __fish_seen_subcommand_from example; and __fish_seen_subcommand_from update' -l type -d 'Example type for cloud mode: http. (default: "http")' -x
+complete -c postman -n '__fish_seen_subcommand_from collection; and __fish_seen_subcommand_from example; and __fish_seen_subcommand_from update' -s m -l message -d 'Short note on what changed, like a commit message (max 500 characters). Shown on the workspace activity feed. Cloud mode only.' -x
 complete -c postman -n '__fish_seen_subcommand_from collection; and __fish_seen_subcommand_from example; and __fish_seen_subcommand_from update' -l json -d 'JSON output.'
 complete -c postman -n '__fish_seen_subcommand_from collection; and __fish_seen_subcommand_from example; and __fish_seen_subcommand_from update' -s h -l help -d 'display help for command'
 # ---------- collection example rm ----------
@@ -274,6 +292,7 @@ complete -c postman -n '__fish_seen_subcommand_from collection; and __fish_seen_
 complete -c postman -n '__fish_seen_subcommand_from collection; and __fish_seen_subcommand_from example; and __fish_seen_subcommand_from rm' -l folder -d 'Folder to scope the request selector.' -x
 complete -c postman -n '__fish_seen_subcommand_from collection; and __fish_seen_subcommand_from example; and __fish_seen_subcommand_from rm' -s w -l workspace -d 'Target a Postman cloud workspace by id (cloud mode).' -x
 complete -c postman -n '__fish_seen_subcommand_from collection; and __fish_seen_subcommand_from example; and __fish_seen_subcommand_from rm' -l type -d 'Example type for cloud mode: http. (default: "http")' -x
+complete -c postman -n '__fish_seen_subcommand_from collection; and __fish_seen_subcommand_from example; and __fish_seen_subcommand_from rm' -s m -l message -d 'Short note on what changed, like a commit message (max 500 characters). Shown on the workspace activity feed. Cloud mode only.' -x
 complete -c postman -n '__fish_seen_subcommand_from collection; and __fish_seen_subcommand_from example; and __fish_seen_subcommand_from rm' -l json -d 'JSON output.'
 complete -c postman -n '__fish_seen_subcommand_from collection; and __fish_seen_subcommand_from example; and __fish_seen_subcommand_from rm' -s h -l help -d 'display help for command'
 # ---------- collection example get ----------
@@ -344,8 +363,7 @@ complete -c postman -n '__fish_seen_subcommand_from collection; and __fish_seen_
 complete -c postman -n '__fish_seen_subcommand_from collection; and __fish_seen_subcommand_from run' -l cookie-jar -d 'Specify the path to a custom cookie jar (serialized tough-cookie JSON)' -r
 complete -c postman -n '__fish_seen_subcommand_from collection; and __fish_seen_subcommand_from run' -l export-cookie-jar -d 'Exports the cookie jar to a file after completing the run' -r
 complete -c postman -n '__fish_seen_subcommand_from collection; and __fish_seen_subcommand_from run' -l verbose -d 'Show detailed information of collection run and each request sent'
-complete -c postman -n '__fish_seen_subcommand_from collection; and __fish_seen_subcommand_from run' -l mock -d 'Start a mock server for the run, its path if it lives in your repository (relative or absolute, e.g. ./postman/mocks/orders) or its id if it lives in Postman cloud (fetched then run locally). An id needs `postman login` (or --postman-api-key).' -r
-complete -c postman -n '__fish_seen_subcommand_from collection; and __fish_seen_subcommand_from run' -l port -d 'Port for the --mock server or --simulation (e.g. 4010), or "auto" for a free one. Defaults to the configured port. Only valid with --mock or --simulation.' -x
+complete -c postman -n '__fish_seen_subcommand_from collection; and __fish_seen_subcommand_from run' -l port -d 'Port for the --simulation server (e.g. 4010), or "auto" for a free one. Defaults to the configured port. Only valid with --simulation.' -x
 complete -c postman -n '__fish_seen_subcommand_from collection; and __fish_seen_subcommand_from run' -l use-mock -d 'Redirect requests for a URL or {{variable}} to a mock during the run. Format: "<url> mock|mock-server:<path|id> [scenario]". Repeat the flag to redirect several URLs (one --use-mock each). Use "mock:<path>" for a mock in your repository (path relative or absolute, e.g. ./postman/mocks/orders), "mock:<id>" for a mock in Postman cloud (fetched then run locally), or "mock-server:<id>" to send requests to a deployed mock server. An id needs `postman login` (or --postman-api-key). The optional third field picks a scenario (defaults to "default"). (default: [])' -x
 complete -c postman -n '__fish_seen_subcommand_from collection; and __fish_seen_subcommand_from run' -l simulation -d 'Run the mocks in a simulation for the run, its .sim.yaml path if it lives in your repository (relative or absolute, e.g. ./postman/simulations/checkout.sim.yaml) or its id if it lives in Postman cloud (fetched then run locally). Members share one port and are addressed by routeKey (e.g. http://localhost:3000/<routeKey>/path). An id needs `postman login` (or --postman-api-key).' -r
 complete -c postman -n '__fish_seen_subcommand_from collection; and __fish_seen_subcommand_from run' -s w -l workspace -d 'Workspace to record the --simulation run\'s start history against. Defaults to the simulation\'s own workspace (when run by id) or the linked project\'s workspace.' -x
@@ -380,7 +398,7 @@ complete -c postman -n '__fish_seen_subcommand_from dataset; and __fish_seen_sub
 complete -c postman -n '__fish_seen_subcommand_from dataset; and __fish_seen_subcommand_from query' -s s -l source -d 'Execute directly against a database datasource; without --source, use federated SQLite' -x
 complete -c postman -n '__fish_seen_subcommand_from dataset; and __fish_seen_subcommand_from query' -s p -l param -d 'Bind values to $1, $2, ... in order; pass multiple values after -p or repeat -p' -x
 complete -c postman -n '__fish_seen_subcommand_from dataset; and __fish_seen_subcommand_from query' -l api-key -d 'Postman API key (defaults to the `postman login` session)' -r
-complete -c postman -n '__fish_seen_subcommand_from dataset; and __fish_seen_subcommand_from query' -l json -d 'Output rows as JSON instead of a table'
+complete -c postman -n '__fish_seen_subcommand_from dataset; and __fish_seen_subcommand_from query' -l json -d 'Output rows as JSON instead of a table; a failure prints a JSON error on stdout'
 complete -c postman -n '__fish_seen_subcommand_from dataset; and __fish_seen_subcommand_from query' -l debug -d 'Include safe classified dataset diagnostics'
 complete -c postman -n '__fish_seen_subcommand_from dataset; and __fish_seen_subcommand_from query' -s h -l help -d 'display help for command'
 # ---------- dataset create ----------
@@ -423,19 +441,20 @@ complete -c postman -n '__fish_seen_subcommand_from dataset; and __fish_seen_sub
 complete -c postman -n '__fish_seen_subcommand_from dataset; and __fish_seen_subcommand_from source; and __fish_seen_subcommand_from add' -l driver-class -d 'Driver class. Auto-resolved when the JAR contains exactly one' -x
 complete -c postman -n '__fish_seen_subcommand_from dataset; and __fish_seen_subcommand_from source; and __fish_seen_subcommand_from add' -l driver-name -d 'Label for this driver type (defaults to the JAR filename)' -x
 complete -c postman -n '__fish_seen_subcommand_from dataset; and __fish_seen_subcommand_from source; and __fish_seen_subcommand_from add' -l url-template -d 'JDBC URL with {{placeholders}}, e.g. jdbc:postgresql://{{host}}:{{port}}/{{database}}' -x
-complete -c postman -n '__fish_seen_subcommand_from dataset; and __fish_seen_subcommand_from source; and __fish_seen_subcommand_from add' -l var -d 'Value for a {{placeholder}}. Repeatable. Use vault:<vaultId>/<secretId> for a secret. WARNING: a literal value is visible in `ps` output and shell history, and is stored in clear text in the dataset YAML (local) or sent in the request body (cloud). Prefer a Shared Vault reference.' -x
-complete -c postman -n '__fish_seen_subcommand_from dataset; and __fish_seen_subcommand_from source; and __fish_seen_subcommand_from add' -l prop -d 'Driver connection property. Repeatable. Same vault: syntax as --var' -x
-complete -c postman -n '__fish_seen_subcommand_from dataset; and __fish_seen_subcommand_from source; and __fish_seen_subcommand_from add' -l vars-file -d 'JSON object of --var values; "-" reads stdin. Supports {"$vaultId":..,"$secretId":..} objects, and keeps secrets out of argv entirely' -r
+complete -c postman -n '__fish_seen_subcommand_from dataset; and __fish_seen_subcommand_from source; and __fish_seen_subcommand_from add' -l var -d 'Value for a {{placeholder}}. Repeatable. Accepts a secret reference: vault:<KEY> (preferred), vault:<vaultId>/<secretId>, or env:<NAME> — see "Secrets" below. WARNING: a literal value is visible in `ps` output and shell history, and is stored in clear text in the dataset YAML (local) or sent in the request body (cloud).' -x
+complete -c postman -n '__fish_seen_subcommand_from dataset; and __fish_seen_subcommand_from source; and __fish_seen_subcommand_from add' -l prop -d 'Driver connection property. Repeatable. Same secret syntax as --var' -x
+complete -c postman -n '__fish_seen_subcommand_from dataset; and __fish_seen_subcommand_from source; and __fish_seen_subcommand_from add' -l vars-file -d 'JSON object of values; "-" reads stdin. Keys are host, port, user, password, database (mysql/postgresql/sqlserver), or --var names for jdbc, with optional "vars"/"props" objects for template variables / connection properties. Values take the same secret syntax, or {"$vaultId":..,"$secretId":..} objects, and keep secrets out of argv entirely' -r
+complete -c postman -n '__fish_seen_subcommand_from dataset; and __fish_seen_subcommand_from source; and __fish_seen_subcommand_from add' -s w -l workspace -d 'Workspace whose Shared Vault resolves vault:<KEY> (falls back to .postman/resources.yaml in the current directory)' -x
 complete -c postman -n '__fish_seen_subcommand_from dataset; and __fish_seen_subcommand_from source; and __fish_seen_subcommand_from add' -l from-source -d 'Reuse another source\'s driver JAR, class and URL template' -x
 complete -c postman -n '__fish_seen_subcommand_from dataset; and __fish_seen_subcommand_from source; and __fish_seen_subcommand_from add' -l java-path -d 'Java runtime to use. Machine-local only - never written to the dataset. Also read from POSTMAN_JDBC_JAVA_PATH' -r
 complete -c postman -n '__fish_seen_subcommand_from dataset; and __fish_seen_subcommand_from source; and __fish_seen_subcommand_from add' -l no-test -d 'Skip the pre-write connection test. Note that resolving the driver class still starts a JVM — on a machine with no Java, pass --driver-class (or --from-source) too'
 complete -c postman -n '__fish_seen_subcommand_from dataset; and __fish_seen_subcommand_from source; and __fish_seen_subcommand_from add' -l ssh-target-host-variable -d 'Template variable holding the tunnelled host (inferred when omitted)' -x
 complete -c postman -n '__fish_seen_subcommand_from dataset; and __fish_seen_subcommand_from source; and __fish_seen_subcommand_from add' -l ssh-target-port-variable -d 'Template variable holding the tunnelled port (inferred when omitted)' -x
 complete -c postman -n '__fish_seen_subcommand_from dataset; and __fish_seen_subcommand_from source; and __fish_seen_subcommand_from add' -l json -d 'Emit the result as JSON instead of prose'
-complete -c postman -n '__fish_seen_subcommand_from dataset; and __fish_seen_subcommand_from source; and __fish_seen_subcommand_from add' -l host -d 'DB host (mysql/postgresql/sqlserver)' -x
+complete -c postman -n '__fish_seen_subcommand_from dataset; and __fish_seen_subcommand_from source; and __fish_seen_subcommand_from add' -l host -d 'DB host (mysql/postgresql/sqlserver). Accepts a secret reference: vault:<KEY> (preferred), vault:<vaultId>/<secretId>, or env:<NAME> — see "Secrets" below.' -x
 complete -c postman -n '__fish_seen_subcommand_from dataset; and __fish_seen_subcommand_from source; and __fish_seen_subcommand_from add' -l port -d 'DB port (defaults to 1433 for sqlserver)' -x
-complete -c postman -n '__fish_seen_subcommand_from dataset; and __fish_seen_subcommand_from source; and __fish_seen_subcommand_from add' -l user -d 'DB user. WARNING: a literal value is visible in `ps` output and shell history, and is stored in clear text in the dataset YAML (local) or sent in the request body (cloud). Prefer a Shared Vault reference.' -x
-complete -c postman -n '__fish_seen_subcommand_from dataset; and __fish_seen_subcommand_from source; and __fish_seen_subcommand_from add' -l password -d 'DB password. WARNING: a literal value is visible in `ps` output and shell history, and is stored in clear text in the dataset YAML (local) or sent in the request body (cloud). Prefer a Shared Vault reference.' -x
+complete -c postman -n '__fish_seen_subcommand_from dataset; and __fish_seen_subcommand_from source; and __fish_seen_subcommand_from add' -l user -d 'DB user. Accepts a secret reference: vault:<KEY> (preferred), vault:<vaultId>/<secretId>, or env:<NAME> — see "Secrets" below. WARNING: a literal value is visible in `ps` output and shell history, and is stored in clear text in the dataset YAML (local) or sent in the request body (cloud).' -x
+complete -c postman -n '__fish_seen_subcommand_from dataset; and __fish_seen_subcommand_from source; and __fish_seen_subcommand_from add' -l password -d 'DB password. Accepts a secret reference: vault:<KEY> (preferred), vault:<vaultId>/<secretId>, or env:<NAME> — see "Secrets" below. WARNING: a literal value is visible in `ps` output and shell history, and is stored in clear text in the dataset YAML (local) or sent in the request body (cloud).' -x
 complete -c postman -n '__fish_seen_subcommand_from dataset; and __fish_seen_subcommand_from source; and __fish_seen_subcommand_from add' -l database -d 'DB database name' -x
 complete -c postman -n '__fish_seen_subcommand_from dataset; and __fish_seen_subcommand_from source; and __fish_seen_subcommand_from add' -l table -d 'DB table to load (required for sqlserver). Leave it out to connect to the whole database; query it with `dataset query -s <source>` or `dataset view create -s <source>`' -x
 complete -c postman -n '__fish_seen_subcommand_from dataset; and __fish_seen_subcommand_from source; and __fish_seen_subcommand_from add' -l ssh-host -d 'SSH bastion host' -x
@@ -469,18 +488,19 @@ complete -c postman -n '__fish_seen_subcommand_from dataset; and __fish_seen_sub
 complete -c postman -n '__fish_seen_subcommand_from dataset; and __fish_seen_subcommand_from source; and __fish_seen_subcommand_from update' -l driver-class -d 'Replace the JDBC driver class' -x
 complete -c postman -n '__fish_seen_subcommand_from dataset; and __fish_seen_subcommand_from source; and __fish_seen_subcommand_from update' -l driver-name -d 'Rename the JDBC driver type label' -x
 complete -c postman -n '__fish_seen_subcommand_from dataset; and __fish_seen_subcommand_from source; and __fish_seen_subcommand_from update' -l url-template -d 'Replace the JDBC URL template' -x
-complete -c postman -n '__fish_seen_subcommand_from dataset; and __fish_seen_subcommand_from source; and __fish_seen_subcommand_from update' -l var -d 'Set a JDBC template variable. Merges onto the existing values. Use vault:<vaultId>/<secretId> for a secret. WARNING: a literal value is visible in `ps` output and shell history, and is stored in clear text in the dataset YAML (local) or sent in the request body (cloud). Prefer a Shared Vault reference.' -x
-complete -c postman -n '__fish_seen_subcommand_from dataset; and __fish_seen_subcommand_from source; and __fish_seen_subcommand_from update' -l prop -d 'Set a JDBC connection property. Merges, same vault: syntax' -x
+complete -c postman -n '__fish_seen_subcommand_from dataset; and __fish_seen_subcommand_from source; and __fish_seen_subcommand_from update' -l var -d 'Set a JDBC template variable. Merges onto the existing values. Accepts a secret reference: vault:<KEY> (preferred), vault:<vaultId>/<secretId>, or env:<NAME> — see "Secrets" below. WARNING: a literal value is visible in `ps` output and shell history, and is stored in clear text in the dataset YAML (local) or sent in the request body (cloud).' -x
+complete -c postman -n '__fish_seen_subcommand_from dataset; and __fish_seen_subcommand_from source; and __fish_seen_subcommand_from update' -l prop -d 'Set a JDBC connection property. Merges, same secret syntax' -x
 complete -c postman -n '__fish_seen_subcommand_from dataset; and __fish_seen_subcommand_from source; and __fish_seen_subcommand_from update' -l unset-var -d 'Remove a JDBC template variable. Merging alone can never remove a key' -x
 complete -c postman -n '__fish_seen_subcommand_from dataset; and __fish_seen_subcommand_from source; and __fish_seen_subcommand_from update' -l unset-prop -d 'Remove a JDBC connection property' -x
-complete -c postman -n '__fish_seen_subcommand_from dataset; and __fish_seen_subcommand_from source; and __fish_seen_subcommand_from update' -l vars-file -d 'JSON object of --var values; "-" reads stdin' -r
+complete -c postman -n '__fish_seen_subcommand_from dataset; and __fish_seen_subcommand_from source; and __fish_seen_subcommand_from update' -l vars-file -d 'JSON object of values to merge; "-" reads stdin. Keys are host, port, user, password, database (mysql/postgresql/sqlserver), or --var names for jdbc, with optional "vars"/"props" objects. Values take the same secret syntax' -r
+complete -c postman -n '__fish_seen_subcommand_from dataset; and __fish_seen_subcommand_from source; and __fish_seen_subcommand_from update' -s w -l workspace -d 'Workspace whose Shared Vault resolves vault:<KEY> (falls back to .postman/resources.yaml in the current directory)' -x
 complete -c postman -n '__fish_seen_subcommand_from dataset; and __fish_seen_subcommand_from source; and __fish_seen_subcommand_from update' -l ssh-target-host-variable -d 'Template variable holding the tunnelled host (JDBC)' -x
 complete -c postman -n '__fish_seen_subcommand_from dataset; and __fish_seen_subcommand_from source; and __fish_seen_subcommand_from update' -l ssh-target-port-variable -d 'Template variable holding the tunnelled port (JDBC)' -x
 complete -c postman -n '__fish_seen_subcommand_from dataset; and __fish_seen_subcommand_from source; and __fish_seen_subcommand_from update' -l java-path -d 'Java runtime for JDBC operations. Machine-local only' -r
-complete -c postman -n '__fish_seen_subcommand_from dataset; and __fish_seen_subcommand_from source; and __fish_seen_subcommand_from update' -l host -d 'Update DB host (mysql/postgresql/sqlserver)' -x
+complete -c postman -n '__fish_seen_subcommand_from dataset; and __fish_seen_subcommand_from source; and __fish_seen_subcommand_from update' -l host -d 'Update DB host (mysql/postgresql/sqlserver). Accepts a secret reference: vault:<KEY> (preferred), vault:<vaultId>/<secretId>, or env:<NAME> — see "Secrets" below.' -x
 complete -c postman -n '__fish_seen_subcommand_from dataset; and __fish_seen_subcommand_from source; and __fish_seen_subcommand_from update' -l port -d 'Update DB port' -x
-complete -c postman -n '__fish_seen_subcommand_from dataset; and __fish_seen_subcommand_from source; and __fish_seen_subcommand_from update' -l user -d 'Update DB user. WARNING: a literal value is visible in `ps` output and shell history, and is stored in clear text in the dataset YAML (local) or sent in the request body (cloud). Prefer a Shared Vault reference.' -x
-complete -c postman -n '__fish_seen_subcommand_from dataset; and __fish_seen_subcommand_from source; and __fish_seen_subcommand_from update' -l password -d 'Update DB password. WARNING: a literal value is visible in `ps` output and shell history, and is stored in clear text in the dataset YAML (local) or sent in the request body (cloud). Prefer a Shared Vault reference.' -x
+complete -c postman -n '__fish_seen_subcommand_from dataset; and __fish_seen_subcommand_from source; and __fish_seen_subcommand_from update' -l user -d 'Update DB user. Accepts a secret reference: vault:<KEY> (preferred), vault:<vaultId>/<secretId>, or env:<NAME> — see "Secrets" below. WARNING: a literal value is visible in `ps` output and shell history, and is stored in clear text in the dataset YAML (local) or sent in the request body (cloud).' -x
+complete -c postman -n '__fish_seen_subcommand_from dataset; and __fish_seen_subcommand_from source; and __fish_seen_subcommand_from update' -l password -d 'Update DB password. Accepts a secret reference: vault:<KEY> (preferred), vault:<vaultId>/<secretId>, or env:<NAME> — see "Secrets" below. WARNING: a literal value is visible in `ps` output and shell history, and is stored in clear text in the dataset YAML (local) or sent in the request body (cloud).' -x
 complete -c postman -n '__fish_seen_subcommand_from dataset; and __fish_seen_subcommand_from source; and __fish_seen_subcommand_from update' -l database -d 'Update DB database name' -x
 complete -c postman -n '__fish_seen_subcommand_from dataset; and __fish_seen_subcommand_from source; and __fish_seen_subcommand_from update' -l table -d 'Update the DB table to load. A source without a table connects to the whole database; query it with `dataset query -s <source>` or `dataset view create -s <source>`' -x
 complete -c postman -n '__fish_seen_subcommand_from dataset; and __fish_seen_subcommand_from source; and __fish_seen_subcommand_from update' -l ssh-host -d 'Update SSH bastion host' -x
@@ -556,12 +576,13 @@ complete -c postman -n '__fish_seen_subcommand_from dataset; and __fish_seen_sub
 complete -c postman -n '__fish_seen_subcommand_from dataset; and __fish_seen_subcommand_from jdbc; and __fish_seen_subcommand_from inspect' -s h -l help -d 'display help for command'
 
 # ---------- environment ----------
-complete -c postman -n '__postman_using_subcommand environment new list get delete var lint' -a new -d 'Scaffold a local environment file, or create one in a Postman workspace with --workspace.'
-complete -c postman -n '__postman_using_subcommand environment new list get delete var lint' -a list -d 'List environments in a Postman workspace.'
-complete -c postman -n '__postman_using_subcommand environment new list get delete var lint' -a get -d 'Read an environment by ID or local environment file path.'
-complete -c postman -n '__postman_using_subcommand environment new list get delete var lint' -a delete -d 'Delete an environment by ID or local environment file path. Prompts unless --yes is passed.'
-complete -c postman -n '__postman_using_subcommand environment new list get delete var lint' -a var -d 'Read and update environment variables.'
-complete -c postman -n '__postman_using_subcommand environment new list get delete var lint' -a lint -d 'Run linting on a local Postman environment at the given file or directory path.'
+complete -c postman -n '__postman_using_subcommand environment new list get share delete var lint' -a new -d 'Scaffold a local environment file, or create one in a Postman workspace with --workspace.'
+complete -c postman -n '__postman_using_subcommand environment new list get share delete var lint' -a list -d 'List environments in a Postman workspace.'
+complete -c postman -n '__postman_using_subcommand environment new list get share delete var lint' -a get -d 'Read an environment by ID or local environment file path.'
+complete -c postman -n '__postman_using_subcommand environment new list get share delete var lint' -a share -d 'Grant a role on a cloud environment to one or more people.'
+complete -c postman -n '__postman_using_subcommand environment new list get share delete var lint' -a delete -d 'Delete an environment by ID or local environment file path. Prompts unless --yes is passed.'
+complete -c postman -n '__postman_using_subcommand environment new list get share delete var lint' -a var -d 'Read and update environment variables.'
+complete -c postman -n '__postman_using_subcommand environment new list get share delete var lint' -a lint -d 'Run linting on a local Postman environment at the given file or directory path.'
 complete -c postman -n '__fish_seen_subcommand_from environment' -s h -l help -d 'display help for command'
 # ---------- environment new ----------
 complete -c postman -n '__fish_seen_subcommand_from environment; and __fish_seen_subcommand_from new' -s w -l workspace -d 'Create the environment in a cloud Postman workspace instead of scaffolding it locally. Required when the current directory is not a local Postman workspace.' -x
@@ -580,6 +601,14 @@ complete -c postman -n '__fish_seen_subcommand_from environment; and __fish_seen
 complete -c postman -n '__fish_seen_subcommand_from environment; and __fish_seen_subcommand_from get' -l json -d 'JSON output'
 complete -c postman -n '__fish_seen_subcommand_from environment; and __fish_seen_subcommand_from get' -s h -l help -d 'display help for command'
 complete -c postman -n '__fish_seen_subcommand_from environment; and __fish_seen_subcommand_from get' -r -k -a '(__fish_complete_suffix .json)'
+# ---------- environment share ----------
+complete -c postman -n '__fish_seen_subcommand_from environment; and __fish_seen_subcommand_from share' -l user -d 'Who to share with. Repeatable, and each value may be a comma-separated list. A value containing @ is treated as an email address, anything else as a Postman user id.' -x
+complete -c postman -n '__fish_seen_subcommand_from environment; and __fish_seen_subcommand_from share' -l role -d 'The role to grant. (default: "viewer")' -x
+complete -c postman -n '__fish_seen_subcommand_from environment; and __fish_seen_subcommand_from share' -l json -d 'Print the outcome as machine-readable JSON.'
+complete -c postman -n '__fish_seen_subcommand_from environment; and __fish_seen_subcommand_from share' -l timeout -d 'Milliseconds to wait for Postman. Defaults to 30000.' -x
+complete -c postman -n '__fish_seen_subcommand_from environment; and __fish_seen_subcommand_from share' -l api-key -d 'Postman API key (defaults to your `postman login` session)' -r
+complete -c postman -n '__fish_seen_subcommand_from environment; and __fish_seen_subcommand_from share' -s h -l help -d 'display help for command'
+complete -c postman -n '__fish_seen_subcommand_from environment; and __fish_seen_subcommand_from share' -r -k -a '(__fish_complete_suffix .json)'
 # ---------- environment delete ----------
 complete -c postman -n '__fish_seen_subcommand_from environment; and __fish_seen_subcommand_from delete' -s y -l yes -d 'Delete without asking for confirmation first'
 complete -c postman -n '__fish_seen_subcommand_from environment; and __fish_seen_subcommand_from delete' -l verbose -d 'Verbose output'
@@ -755,7 +784,7 @@ complete -c postman -n '__fish_seen_subcommand_from globals; and __fish_seen_sub
 complete -c postman -n '__fish_seen_subcommand_from globals; and __fish_seen_subcommand_from lint' -r -k -a '(__fish_complete_suffix .json)'
 
 # ---------- mock ----------
-complete -c postman -n '__postman_using_subcommand mock generate run push deploy get list log delete' -a generate -d 'Generate a mock from a Postman collection or an OpenAPI file, or from a built-in sample shopping-cart mock (POST /cart/items, GET /cart, POST /checkout). Writes a local mock by default, or a cloud mock with --workspace.'
+complete -c postman -n '__postman_using_subcommand mock generate run push deploy get list log delete' -a generate -d 'Generate a mock from a Postman collection or an OpenAPI file, or from a built-in sample shopping-cart mock (POST /cart/items, GET /cart, POST /checkout). Writes a local mock by default, or a cloud mock with --workspace. Add --deploy to also make it a live mock server.'
 complete -c postman -n '__postman_using_subcommand mock generate run push deploy get list log delete' -a run -d 'Start a mock using its path if it lives in your repository, or its id if it lives in Postman cloud (fetched and run locally).'
 complete -c postman -n '__postman_using_subcommand mock generate run push deploy get list log delete' -a push -d 'Upload a mock from your repository to Postman cloud (creates it the first time, updates it after).'
 complete -c postman -n '__postman_using_subcommand mock generate run push deploy get list log delete' -a deploy -d 'Turn a mock in Postman cloud into a live mock server others can call over the internet.'
@@ -771,8 +800,12 @@ complete -c postman -n '__fish_seen_subcommand_from mock; and __fish_seen_subcom
 complete -c postman -n '__fish_seen_subcommand_from mock; and __fish_seen_subcommand_from generate' -l stateful -d 'Generate pm.state-backed CRUD handlers (create/read/list/update/delete) instead of static example responses. Endpoints that are not CRUD-shaped stay static. Applies to collection or spec sources.'
 complete -c postman -n '__fish_seen_subcommand_from mock; and __fish_seen_subcommand_from generate' -l force -d 'Overwrite the mock\'s files if the target folder already has one'
 complete -c postman -n '__fish_seen_subcommand_from mock; and __fish_seen_subcommand_from generate' -s u -l update -d 'Update an existing mock from the source instead of creating a new one. Path to the mock, relative or absolute, e.g. ./postman/mocks/orders. Cannot be used with --output.' -r
-complete -c postman -n '__fish_seen_subcommand_from mock; and __fish_seen_subcommand_from generate' -s w -l workspace -d 'Save the mock to this Postman cloud workspace (by id) instead of your repository. Cannot be used with --output, --force, or --update.' -x
-complete -c postman -n '__fish_seen_subcommand_from mock; and __fish_seen_subcommand_from generate' -l api-key -d 'Postman API key to use with --workspace (defaults to your `postman login` session)' -r
+complete -c postman -n '__fish_seen_subcommand_from mock; and __fish_seen_subcommand_from generate' -s w -l workspace -d 'Save the mock to this Postman cloud workspace (by id) instead of your repository. Cannot be used with --output, --force, or --update, except with --deploy, where it only picks the workspace.' -x
+complete -c postman -n '__fish_seen_subcommand_from mock; and __fish_seen_subcommand_from generate' -l deploy -d 'After generating, upload the mock to Postman cloud and deploy it to a live mock server (private by default). Uses --workspace, else the workspace linked to this project.'
+complete -c postman -n '__fish_seen_subcommand_from mock; and __fish_seen_subcommand_from generate' -l public -d 'With --deploy, let anyone with the link reach the server (default: callers need an API key)'
+complete -c postman -n '__fish_seen_subcommand_from mock; and __fish_seen_subcommand_from generate' -s s -l slug -d 'With --deploy, the short label used in the server\'s web address' -x
+complete -c postman -n '__fish_seen_subcommand_from mock; and __fish_seen_subcommand_from generate' -l json -d 'Print the result (with --deploy, the live server details) as machine-readable data instead of a summary'
+complete -c postman -n '__fish_seen_subcommand_from mock; and __fish_seen_subcommand_from generate' -l api-key -d 'Postman API key to use with --workspace or --deploy (defaults to your `postman login` session)' -r
 complete -c postman -n '__fish_seen_subcommand_from mock; and __fish_seen_subcommand_from generate' -s x -l suppress-exit-code -d 'Always exit with code 0, even on failure'
 complete -c postman -n '__fish_seen_subcommand_from mock; and __fish_seen_subcommand_from generate' -s h -l help -d 'display help for command'
 # ---------- mock run ----------
@@ -790,6 +823,7 @@ complete -c postman -n '__fish_seen_subcommand_from mock; and __fish_seen_subcom
 # ---------- mock push ----------
 complete -c postman -n '__fish_seen_subcommand_from mock; and __fish_seen_subcommand_from push' -s w -l workspace -d 'Postman cloud workspace to upload to, by id (defaults to the workspace already linked to this project)' -x
 complete -c postman -n '__fish_seen_subcommand_from mock; and __fish_seen_subcommand_from push' -l api-key -d 'Postman API key (defaults to your `postman login` session)' -r
+complete -c postman -n '__fish_seen_subcommand_from mock; and __fish_seen_subcommand_from push' -l json -d 'Print the result as machine-readable data'
 complete -c postman -n '__fish_seen_subcommand_from mock; and __fish_seen_subcommand_from push' -s h -l help -d 'display help for command'
 complete -c postman -n '__fish_seen_subcommand_from mock; and __fish_seen_subcommand_from push' -r -k -a '(__fish_complete_suffix .json)'
 # ---------- mock deploy ----------
@@ -800,11 +834,12 @@ complete -c postman -n '__fish_seen_subcommand_from mock; and __fish_seen_subcom
 complete -c postman -n '__fish_seen_subcommand_from mock; and __fish_seen_subcommand_from deploy' -l auto-deploy -d 'Update the live server automatically whenever the mock changes (off by default)'
 complete -c postman -n '__fish_seen_subcommand_from mock; and __fish_seen_subcommand_from deploy' -s y -l yes -d 'Use the defaults and skip all questions (private, no auto-deploy)'
 complete -c postman -n '__fish_seen_subcommand_from mock; and __fish_seen_subcommand_from deploy' -l api-key -d 'Postman API key (defaults to your `postman login` session)' -r
+complete -c postman -n '__fish_seen_subcommand_from mock; and __fish_seen_subcommand_from deploy' -l json -d 'Print the live server details as machine-readable data instead of a summary (asks no questions)'
 complete -c postman -n '__fish_seen_subcommand_from mock; and __fish_seen_subcommand_from deploy' -s h -l help -d 'display help for command'
 complete -c postman -n '__fish_seen_subcommand_from mock; and __fish_seen_subcommand_from deploy' -r -k -a '(__fish_complete_suffix .json)'
 # ---------- mock get ----------
 complete -c postman -n '__fish_seen_subcommand_from mock; and __fish_seen_subcommand_from get' -l api-key -d 'Postman API key (defaults to your `postman login` session)' -r
-complete -c postman -n '__fish_seen_subcommand_from mock; and __fish_seen_subcommand_from get' -l json -d 'Print the details as machine-readable data instead of a table'
+complete -c postman -n '__fish_seen_subcommand_from mock; and __fish_seen_subcommand_from get' -l json -d 'Print the details as machine-readable data instead of a summary'
 complete -c postman -n '__fish_seen_subcommand_from mock; and __fish_seen_subcommand_from get' -s h -l help -d 'display help for command'
 complete -c postman -n '__fish_seen_subcommand_from mock; and __fish_seen_subcommand_from get' -r -k -a '(__fish_complete_suffix .json)'
 # ---------- mock list ----------
@@ -827,42 +862,44 @@ complete -c postman -n '__fish_seen_subcommand_from mock; and __fish_seen_subcom
 # ---------- mock delete ----------
 complete -c postman -n '__fish_seen_subcommand_from mock; and __fish_seen_subcommand_from delete' -s y -l yes -d 'Delete without asking for confirmation first'
 complete -c postman -n '__fish_seen_subcommand_from mock; and __fish_seen_subcommand_from delete' -l api-key -d 'Postman API key, used with a Postman cloud id (defaults to your `postman login` session)' -r
+complete -c postman -n '__fish_seen_subcommand_from mock; and __fish_seen_subcommand_from delete' -l json -d 'Print the result as machine-readable data (requires --yes)'
 complete -c postman -n '__fish_seen_subcommand_from mock; and __fish_seen_subcommand_from delete' -s h -l help -d 'display help for command'
 complete -c postman -n '__fish_seen_subcommand_from mock; and __fish_seen_subcommand_from delete' -r -k -a '(__fish_complete_suffix .json)'
 
 # ---------- monitor ----------
-complete -c postman -n '__postman_using_subcommand monitor run create update delete jobs runs list get metrics pause resume' -a run -d 'Invoke a monitor run and display results.'
-complete -c postman -n '__postman_using_subcommand monitor run create update delete jobs runs list get metrics pause resume' -a create -d 'Create a collection-based monitor.'
-complete -c postman -n '__postman_using_subcommand monitor run create update delete jobs runs list get metrics pause resume' -a update -d 'Update a monitor\'s schedule, runner, notifications, request selection or run options.'
-complete -c postman -n '__postman_using_subcommand monitor run create update delete jobs runs list get metrics pause resume' -a delete -d 'Permanently delete a monitor. Prompts for confirmation unless --yes is passed.'
-complete -c postman -n '__postman_using_subcommand monitor run create update delete jobs runs list get metrics pause resume' -a jobs -d 'Inspect a monitor\'s jobs and their per-region runs.'
-complete -c postman -n '__postman_using_subcommand monitor run create update delete jobs runs list get metrics pause resume' -a runs -d 'Inspect a monitor run\'s attempts.'
-complete -c postman -n '__postman_using_subcommand monitor run create update delete jobs runs list get metrics pause resume' -a list -d 'List the monitors visible to you.'
-complete -c postman -n '__postman_using_subcommand monitor run create update delete jobs runs list get metrics pause resume' -a get -d 'Show a monitor\'s configuration.'
-complete -c postman -n '__postman_using_subcommand monitor run create update delete jobs runs list get metrics pause resume' -a metrics -d 'Show per-request latency and outcome history for a monitor.'
-complete -c postman -n '__postman_using_subcommand monitor run create update delete jobs runs list get metrics pause resume' -a pause -d 'Pause a monitor, so it stops firing on schedule.'
-complete -c postman -n '__postman_using_subcommand monitor run create update delete jobs runs list get metrics pause resume' -a resume -d 'Resume a paused monitor, so it fires on schedule again.'
+complete -c postman -n '__postman_using_subcommand monitor run create update delete jobs runs list get metrics pause resume share' -a run -d 'Run a monitor now and report the result.'
+complete -c postman -n '__postman_using_subcommand monitor run create update delete jobs runs list get metrics pause resume share' -a create -d 'Create a collection-based monitor.'
+complete -c postman -n '__postman_using_subcommand monitor run create update delete jobs runs list get metrics pause resume share' -a update -d 'Update a monitor\'s schedule, runner, notifications, request selection or run options.'
+complete -c postman -n '__postman_using_subcommand monitor run create update delete jobs runs list get metrics pause resume share' -a delete -d 'Permanently delete a monitor. Prompts for confirmation unless --yes is passed.'
+complete -c postman -n '__postman_using_subcommand monitor run create update delete jobs runs list get metrics pause resume share' -a jobs -d 'Inspect a monitor\'s jobs (also called executions) and their per-runner runs.'
+complete -c postman -n '__postman_using_subcommand monitor run create update delete jobs runs list get metrics pause resume share' -a runs -d 'Inspect one run of a monitor job: its requests, assertions and attempts.'
+complete -c postman -n '__postman_using_subcommand monitor run create update delete jobs runs list get metrics pause resume share' -a list -d 'List the monitors visible to you, one page at a time.'
+complete -c postman -n '__postman_using_subcommand monitor run create update delete jobs runs list get metrics pause resume share' -a get -d 'Show a monitor\'s configuration and its last run.'
+complete -c postman -n '__postman_using_subcommand monitor run create update delete jobs runs list get metrics pause resume share' -a metrics -d 'Show per-request latency and outcome history for a monitor.'
+complete -c postman -n '__postman_using_subcommand monitor run create update delete jobs runs list get metrics pause resume share' -a pause -d 'Pause a monitor, so it stops firing on schedule.'
+complete -c postman -n '__postman_using_subcommand monitor run create update delete jobs runs list get metrics pause resume share' -a resume -d 'Resume a paused monitor, so it fires on schedule again.'
+complete -c postman -n '__postman_using_subcommand monitor run create update delete jobs runs list get metrics pause resume share' -a share -d 'Grant a role on a monitor to one or more people.'
 complete -c postman -n '__fish_seen_subcommand_from monitor' -s h -l help -d 'display help for command'
 # ---------- monitor run ----------
 complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from run' -l api-key -d 'Postman API key (defaults to POSTMAN_API_KEY, then the `postman login` session, then a guest session)' -r
-complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from run' -s x -l suppress-exit-code -d 'Specify whether or not to override the default exit code for the current run'
-complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from run' -s t -l timeout -d 'Maximum wait time for run completion in milliseconds (default: 15 minutes) (default: 900000)' -x
-complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from run' -l async -d 'Submit the run and return immediately with its job id and Postman URL, without waiting for completion'
-complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from run' -l json -d 'Output the run\'s verdict as JSON instead of a table, printing nothing else'
+complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from run' -s x -l suppress-exit-code -d 'Always exit 0, whatever the run\'s result or the failure'
+complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from run' -s t -l timeout -d 'How long to wait for the run to finish, in milliseconds (default: 900000)' -x
+complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from run' -l async -d 'Submit the run and print its job id and Postman URL without waiting for it to finish'
+complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from run' -l json -d 'Print { state, monitorId, jobId, url, stats } as JSON, and nothing else'
 complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from run' -s h -l help -d 'display help for command'
 # ---------- monitor create ----------
-complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from create' -s c -l collection -d 'Collection to monitor -- accepts the id shown in the Postman app, prefixed or bare' -x
+complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from create' -s c -l collection -d 'Collection to monitor: its id or uid, from the Postman app or `postman collection list`' -x
 complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from create' -l name -d 'Monitor name (defaults to the linked collection\'s own name)' -x
-complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from create' -s e -l environment -d 'Environment to run the monitored collection with' -x
-complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from create' -s w -l workspace -d 'Workspace to create the monitor in (defaults to the workspace named in the local .postman/resources.yaml manifest; required if neither is available)' -x
-complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from create' -l schedule -d 'Cron expression for the monitor\'s schedule' -x
+complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from create' -s e -l environment -d 'Environment to run the collection with: its uid, from the Postman app or `postman environment list`' -x
+complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from create' -s w -l workspace -d 'Workspace to create the monitor in, from `postman workspace list` (defaults to the workspace named in the local .postman/resources.yaml manifest; required if neither is available)' -x
+complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from create' -l schedule -d 'Cron expression for the monitor\'s schedule, five fields: minute hour day-of-month month day-of-week, for example "0 9 * * MON". Leave month as * unless the monitor should run only in certain months; then write the month as a name (jan-dec)' -x
 complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from create' -l timezone -d 'Time zone for --schedule, for example America/New_York (defaults to the host machine\'s own zone)' -x
 complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from create' -l runner -d 'A Postman region name (see `postman runner regions`) or the id of a self-hosted runner created in Postman (list existing ones with `postman runner list`) to run from (repeatable) (default: [])' -x
 complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from create' -s i -l item -d 'Id of a request or folder in the collection to run, in the order given (repeatable; ids only, not names or paths; defaults to every request; list ids with `postman collection get <collection-id> --json`) (default: [])' -x
 complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from create' -l notify-email -d 'Email to notify on a run failure or error (repeatable) (default: [])' -x
 complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from create' -l notification-limit -d 'Consecutive failure notifications to send before muting them' -x
-complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from create' -l retry -d 'Times to retry a failed run' -x
-complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from create' -l timeout -d 'Request timeout in milliseconds' -x
+complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from create' -l retry -d 'Times to retry a failed run: --retry 2 allows up to 3 attempts' -x
+complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from create' -l timeout -d 'Per-request timeout the monitor applies when it runs, in milliseconds (this command does not wait for a run; `postman monitor run --timeout` sets how long that waits)' -x
 complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from create' -l delay -d 'Delay between requests in milliseconds' -x
 complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from create' -l strict-ssl -d 'Fail the run when the target\'s TLS certificate cannot be verified'
 complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from create' -l insecure -d 'Skip TLS certificate verification for the monitored target'
@@ -874,22 +911,22 @@ complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_sub
 complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from create' -l iteration-strategy -d 'How iteration data is consumed, for example round_robin, repeat_last or stop_at_end (requires --iteration-count, --dataset-id and --dataset-view-id)' -x
 complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from create' -l no-run-now -d 'Do not trigger an immediate run after creating the monitor'
 complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from create' -l api-key -d 'Postman API key (defaults to POSTMAN_API_KEY, then the `postman login` session, then a guest session)' -r
-complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from create' -l json -d 'Output as JSON instead of a table'
+complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from create' -l json -d 'Print the outcome, the created monitor\'s id, uid, name and active state, and the job of its first run, as JSON'
 complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from create' -s h -l help -d 'display help for command'
 # ---------- monitor update ----------
 complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from update' -l name -d 'New monitor name' -x
-complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from update' -l schedule -d 'New cron expression for the monitor\'s schedule' -x
+complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from update' -l schedule -d 'New cron expression for the monitor\'s schedule, five fields: minute hour day-of-month month day-of-week, for example "0 9 * * MON". Leave month as * unless the monitor should run only in certain months; then write the month as a name (jan-dec)' -x
 complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from update' -l timezone -d 'Time zone for --schedule, for example America/New_York (defaults to the host machine\'s own zone)' -x
 complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from update' -l runner -d 'A Postman region name (see `postman runner regions`) or the id of a self-hosted runner created in Postman (list existing ones with `postman runner list`) to run from (repeatable; replaces the current set) (default: [])' -x
 complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from update' -s i -l item -d 'Id of a request or folder in the collection to run, in the order given (repeatable; ids only, not names or paths; replaces the saved selection; list ids with `postman collection get <collection-id> --json`) (default: [])' -x
 complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from update' -l clear-items -d 'Remove the saved selection so the monitor runs every request in its collection'
 complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from update' -l notify-email -d 'Email to notify on a run failure or error (repeatable; replaces the current list) (default: [])' -x
 complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from update' -l clear-notifications -d 'Remove every notification recipient'
-complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from update' -s e -l environment -d 'Environment to run the monitored collection with (replaces the current one)' -x
+complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from update' -s e -l environment -d 'Environment to run the collection with, replacing the current one: its uid, from `postman environment list`' -x
 complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from update' -l clear-environment -d 'Run the monitored collection with no environment'
 complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from update' -l notification-limit -d 'Consecutive failure notifications to send before muting them' -x
-complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from update' -l retry -d 'Times to retry a failed run' -x
-complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from update' -l timeout -d 'Request timeout in milliseconds' -x
+complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from update' -l retry -d 'Times to retry a failed run: --retry 2 allows up to 3 attempts' -x
+complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from update' -l timeout -d 'Per-request timeout the monitor applies when it runs, in milliseconds (this command does not wait for a run; `postman monitor run --timeout` sets how long that waits)' -x
 complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from update' -l delay -d 'Delay between requests in milliseconds' -x
 complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from update' -l strict-ssl -d 'Fail the run when the target\'s TLS certificate cannot be verified'
 complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from update' -l insecure -d 'Skip TLS certificate verification for the monitored target'
@@ -900,76 +937,82 @@ complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_sub
 complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from update' -l iteration-count -d 'Number of iterations to run' -x
 complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from update' -l iteration-strategy -d 'How iteration data is consumed, for example round_robin, repeat_last or stop_at_end (requires --iteration-count, --dataset-id and --dataset-view-id)' -x
 complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from update' -l api-key -d 'Postman API key (defaults to POSTMAN_API_KEY, then the `postman login` session, then a guest session)' -r
-complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from update' -l json -d 'Output as JSON instead of a table'
+complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from update' -l json -d 'Print the outcome and the monitor\'s id, uid, name and active state as JSON'
 complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from update' -s h -l help -d 'display help for command'
 # ---------- monitor delete ----------
-complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from delete' -s y -l yes -d 'Skip the confirmation prompt'
+complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from delete' -s y -l yes -d 'Skip the confirmation prompt; required when there is no interactive terminal or with --silent'
 complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from delete' -l api-key -d 'Postman API key (defaults to POSTMAN_API_KEY, then the `postman login` session, then a guest session)' -r
-complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from delete' -l json -d 'Output the outcome, including any failure, as JSON instead of a plain message'
+complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from delete' -l json -d 'Print the outcome (deleted or aborted) and the monitor id as JSON'
 complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from delete' -s h -l help -d 'display help for command'
 # ---------- monitor jobs ----------
-complete -c postman -n '__postman_using_subcommand jobs list get' -a list -d 'List a monitor\'s recent jobs.'
-complete -c postman -n '__postman_using_subcommand jobs list get' -a get -d 'Report one job\'s terminal state and its per-region run outcomes.'
+complete -c postman -n '__postman_using_subcommand jobs list get' -a list -d 'List a monitor\'s recent jobs, newest first. A job (also called an execution) is one firing of the monitor, with one run per runner.'
+complete -c postman -n '__postman_using_subcommand jobs list get' -a get -d 'Show one job (also called an execution) and the state, runner and duration of each of its runs. A run\'s duration covers every attempt, including retries.'
 complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from jobs' -s h -l help -d 'display help for command'
 # ---------- monitor jobs list ----------
-complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from jobs; and __fish_seen_subcommand_from list' -l api-key -d 'Postman API key (defaults to POSTMAN_API_KEY, then the `postman login` session)' -r
-complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from jobs; and __fish_seen_subcommand_from list' -l result -d 'Filter by outcome, for example success, failure, error or abort' -x
-complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from jobs; and __fish_seen_subcommand_from list' -l trigger -d 'Filter by trigger, for example api, schedule, webhook or postman-cli' -x
+complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from jobs; and __fish_seen_subcommand_from list' -l api-key -d 'Postman API key (defaults to POSTMAN_API_KEY, then the `postman login` session, then a guest session)' -r
+complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from jobs; and __fish_seen_subcommand_from list' -l result -d 'Only jobs that finished in this state: success, failure, error or abort; any other value is rejected before any request' -x
+complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from jobs; and __fish_seen_subcommand_from list' -l trigger -d 'Only jobs started by this trigger: api, schedule, webhook or postman-cli; any other value is rejected before any request' -x
 complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from jobs; and __fish_seen_subcommand_from list' -l since -d 'Only jobs that finished at or after this ISO 8601 date-time' -x
-complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from jobs; and __fish_seen_subcommand_from list' -l limit -d 'Maximum number of jobs to return' -x
-complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from jobs; and __fish_seen_subcommand_from list' -l cursor -d 'Opaque pagination cursor' -x
-complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from jobs; and __fish_seen_subcommand_from list' -l json -d 'Output as JSON instead of a table'
+complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from jobs; and __fish_seen_subcommand_from list' -l limit -d 'Jobs per page, 1-25 (default: 25)' -x
+complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from jobs; and __fish_seen_subcommand_from list' -l cursor -d 'Page number to read, from the "Next page" line or `nextCursor` under --json of a previous listing; pass the same --limit and filters' -x
+complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from jobs; and __fish_seen_subcommand_from list' -l json -d 'Print { monitorId, jobs, nextCursor } as JSON, each job with its runs'
 complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from jobs; and __fish_seen_subcommand_from list' -s h -l help -d 'display help for command'
 # ---------- monitor jobs get ----------
-complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from jobs; and __fish_seen_subcommand_from get' -l api-key -d 'Postman API key (defaults to POSTMAN_API_KEY, then the `postman login` session)' -r
-complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from jobs; and __fish_seen_subcommand_from get' -l json -d 'Output as JSON instead of a table'
+complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from jobs; and __fish_seen_subcommand_from get' -l api-key -d 'Postman API key (defaults to POSTMAN_API_KEY, then the `postman login` session, then a guest session)' -r
+complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from jobs; and __fish_seen_subcommand_from get' -l json -d 'Print the job as JSON, with each run\'s state, runner, counts, duration and attempts'
 complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from jobs; and __fish_seen_subcommand_from get' -s h -l help -d 'display help for command'
 # ---------- monitor runs ----------
-complete -c postman -n '__postman_using_subcommand runs get' -a get -d 'Report which test assertions ran during one attempt of a run, which failed, and why.'
+complete -c postman -n '__postman_using_subcommand runs get' -a get -d 'Show one attempt of a run: each request with its response or error, and its assertions, console lines and exceptions. A retried run has several attempts, numbered from 0; the latest is shown unless --attempt names another. Console, assertion and exception messages are the collection\'s own output, printed as the run recorded them.'
 complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from runs' -s h -l help -d 'display help for command'
 # ---------- monitor runs get ----------
-complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from runs; and __fish_seen_subcommand_from get' -l api-key -d 'Postman API key (defaults to POSTMAN_API_KEY, then the `postman login` session)' -r
-complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from runs; and __fish_seen_subcommand_from get' -l attempt -d 'Which attempt of the run to show, where 0 is the first (default: the most recent)' -x
-complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from runs; and __fish_seen_subcommand_from get' -l failed-only -d 'Show only failed assertions'
-complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from runs; and __fish_seen_subcommand_from get' -l json -d 'Output as JSON instead of a table'
+complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from runs; and __fish_seen_subcommand_from get' -l api-key -d 'Postman API key (defaults to POSTMAN_API_KEY, then the `postman login` session, then a guest session)' -r
+complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from runs; and __fish_seen_subcommand_from get' -l attempt -d 'Which attempt to show, from 0 for the first (default: the latest)' -x
+complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from runs; and __fish_seen_subcommand_from get' -l failed-only -d 'Show only requests with a failed assertion, an exception or a network error'
+complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from runs; and __fish_seen_subcommand_from get' -l json -d 'Print the run as JSON: its state, attempt, assertion counts and every request with its entries'
 complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from runs; and __fish_seen_subcommand_from get' -s h -l help -d 'display help for command'
 # ---------- monitor list ----------
 complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from list' -l api-key -d 'Postman API key (defaults to POSTMAN_API_KEY, then the `postman login` session, then a guest session)' -r
-complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from list' -s w -l workspace -d 'Filter to monitors in this workspace' -x
-complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from list' -s c -l collection -d 'Filter to monitors on this collection' -x
-complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from list' -s e -l environment -d 'Filter to monitors on this environment' -x
-complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from list' -l runner -d 'Filter to a self-hosted runner id, not a Postman region. Cannot be combined with --workspace, --collection, --environment, --owner, --team or --active' -x
-complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from list' -l owner -d 'Filter to monitors created by this user id (shown in the Owner column)' -x
-complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from list' -l team -d 'Filter to monitors owned by your own team'
-complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from list' -l active -d 'Filter by active state' -x
-complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from list' -l limit -d 'Maximum number of monitors to return (Postman caps the page size and rejects a larger value)' -x
-complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from list' -l cursor -d 'Pagination cursor from a previous page\'s response' -x
-complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from list' -l columns -d 'Comma-separated columns to show. Defaults to Name, Status, ID, Schedule, Owner, Collection. Also available: State, Notifications, Environment, Runners' -x
-complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from list' -l no-headers -d 'Omit the header row'
-complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from list' -s f -l filter -d 'Show only monitors whose name contains this text (applies to the returned page, case-insensitive)' -x
+complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from list' -s w -l workspace -d 'Only monitors in this workspace (ids from `postman workspace list`)' -x
+complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from list' -s c -l collection -d 'Only monitors on this collection: its id or uid' -x
+complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from list' -s e -l environment -d 'Only monitors on this environment: its uid' -x
+complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from list' -l runner -d 'Only monitors on this self-hosted runner id, from `postman runner list` (not a Postman region). Cannot be combined with --workspace, --collection, --environment, --owner or --active' -x
+complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from list' -l owner -d 'Only monitors created by this user id: the `owner` field under --json' -x
+complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from list' -l active -d 'Only active (true) or paused (false) monitors' -x
+complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from list' -l limit -d 'Monitors per page, 1-25' -x
+complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from list' -l cursor -d 'Page to read: the cursor from the "Next page" line of a previous listing, or `nextCursor` under --json; pass the same filters and --limit' -x
+complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from list' -l columns -d 'Comma-separated columns to show. Defaults to Name, ID, State, Health, Schedule, Owner, Collection, dropping Collection, Owner, Schedule in that order when the table is wider than the terminal. Also available: Environment, Runners, Notifications' -x
+complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from list' -l no-headers -d 'Omit the header row and its rule'
+complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from list' -s f -l filter -d 'Only monitors whose name contains this text, case-insensitive (applies to the returned page)' -x
 complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from list' -l sort -d 'Sort the returned page by "name" or "active"' -x
-complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from list' -l json -d 'Output as JSON instead of a table'
+complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from list' -l json -d 'Print { monitors, nextCursor } as JSON, every monitor field except lastRun present (null when unset); monitor get carries lastRun'
 complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from list' -s h -l help -d 'display help for command'
 # ---------- monitor get ----------
 complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from get' -l api-key -d 'Postman API key (defaults to POSTMAN_API_KEY, then the `postman login` session, then a guest session)' -r
-complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from get' -l json -d 'Output as JSON instead of a table'
+complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from get' -l json -d 'Print the monitor as JSON, every field present (null when unset)'
 complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from get' -s h -l help -d 'display help for command'
 # ---------- monitor metrics ----------
 complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from metrics' -l api-key -d 'Postman API key (defaults to POSTMAN_API_KEY, then the `postman login` session, then a guest session)' -r
 complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from metrics' -l since -d 'Only executions at or after this ISO 8601 date-time (defaults to 7 days ago)' -x
 complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from metrics' -l until -d 'Only executions at or before this ISO 8601 date-time (defaults to now)' -x
 complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from metrics' -s f -l filter -d 'Show only requests whose name contains this text (case-insensitive)' -x
-complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from metrics' -l limit -d 'Maximum number of rows to show: executions, newest first, under --json, or requests, worst-behaving first, in the table. Applied to the results after they are fetched, so it does not make the command faster' -x
-complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from metrics' -l json -d 'Output as JSON instead of a table'
+complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from metrics' -l limit -d 'Rows to show, any positive whole number: the worst-behaving requests in the table, or the newest executions under --json. Applied after the results are fetched' -x
+complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from metrics' -l json -d 'Print { monitorId, window, metricsAvailable, executions } as JSON, one entry per request per job per runner'
 complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from metrics' -s h -l help -d 'display help for command'
 # ---------- monitor pause ----------
 complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from pause' -l api-key -d 'Postman API key (defaults to POSTMAN_API_KEY, then the `postman login` session, then a guest session)' -r
-complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from pause' -l json -d 'Output as JSON instead of a table'
+complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from pause' -l json -d 'Print the outcome and the monitor\'s id, uid, name and active state as JSON'
 complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from pause' -s h -l help -d 'display help for command'
 # ---------- monitor resume ----------
 complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from resume' -l api-key -d 'Postman API key (defaults to POSTMAN_API_KEY, then the `postman login` session, then a guest session)' -r
-complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from resume' -l json -d 'Output as JSON instead of a table'
+complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from resume' -l json -d 'Print the outcome and the monitor\'s id, uid, name and active state as JSON'
 complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from resume' -s h -l help -d 'display help for command'
+# ---------- monitor share ----------
+complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from share' -l user -d 'Who to share with. Repeatable, and each value may be a comma-separated list. A value containing @ is treated as an email address, anything else as a Postman user id.' -x
+complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from share' -l role -d 'The role to grant. (default: "viewer")' -x
+complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from share' -l json -d 'Print the outcome as machine-readable JSON.'
+complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from share' -l timeout -d 'Milliseconds to wait for Postman. Defaults to 30000.' -x
+complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from share' -l api-key -d 'Postman API key (defaults to your `postman login` session)' -r
+complete -c postman -n '__fish_seen_subcommand_from monitor; and __fish_seen_subcommand_from share' -s h -l help -d 'display help for command'
 
 # ---------- request ----------
 complete -c postman -n '__fish_seen_subcommand_from request' -s H -l header -d 'Add HTTP header in key:value format. Can be used multiple times. Example: -H "Content-Type:application/json" -H "X-API-Key:abc123" (default: [])' -x
@@ -1036,7 +1079,7 @@ complete -c postman -n '__fish_seen_subcommand_from runner' -s h -l help -d 'dis
 # ---------- runner start ----------
 complete -c postman -n '__fish_seen_subcommand_from runner; and __fish_seen_subcommand_from start' -l id -d 'The ID of the runner to execute' -x
 complete -c postman -n '__fish_seen_subcommand_from runner; and __fish_seen_subcommand_from start' -l key -d 'The secret key for the runner' -r
-complete -c postman -n '__fish_seen_subcommand_from runner; and __fish_seen_subcommand_from start' -l region -d 'Region this runner reports to -- use "eu" for the EU region' -x
+complete -c postman -n '__fish_seen_subcommand_from runner; and __fish_seen_subcommand_from start' -l region -d 'Data residency of the Postman account the runner belongs to: "us" (default) or "eu". This is not a monitor runner region' -x
 complete -c postman -n '__fish_seen_subcommand_from runner; and __fish_seen_subcommand_from start' -l proxy -d 'External proxy URL, for example http://proxy.com or http://proxy.com:8080' -x
 complete -c postman -n '__fish_seen_subcommand_from runner; and __fish_seen_subcommand_from start' -l egress-proxy -d 'Enable built-in egress proxy'
 complete -c postman -n '__fish_seen_subcommand_from runner; and __fish_seen_subcommand_from start' -l egress-proxy-authz-url -d 'Custom egress proxy authorization service base URL' -x
@@ -1049,12 +1092,12 @@ complete -c postman -n '__fish_seen_subcommand_from runner; and __fish_seen_subc
 complete -c postman -n '__fish_seen_subcommand_from runner; and __fish_seen_subcommand_from start' -s h -l help -d 'display help for command'
 # ---------- runner list ----------
 complete -c postman -n '__fish_seen_subcommand_from runner; and __fish_seen_subcommand_from list' -l api-key -d 'Postman API key (defaults to POSTMAN_API_KEY, then the `postman login` session)' -r
-complete -c postman -n '__fish_seen_subcommand_from runner; and __fish_seen_subcommand_from list' -s w -l workspace -d 'Filter to runners in this workspace' -x
-complete -c postman -n '__fish_seen_subcommand_from runner; and __fish_seen_subcommand_from list' -l json -d 'Output the runner list as JSON instead of a table'
+complete -c postman -n '__fish_seen_subcommand_from runner; and __fish_seen_subcommand_from list' -s w -l workspace -d 'Only runners this workspace can use: runners scoped to it and runners shared with the whole team' -x
+complete -c postman -n '__fish_seen_subcommand_from runner; and __fish_seen_subcommand_from list' -l json -d 'Print { runners } as JSON, every field present (null when unset)'
 complete -c postman -n '__fish_seen_subcommand_from runner; and __fish_seen_subcommand_from list' -s h -l help -d 'display help for command'
 # ---------- runner regions ----------
 complete -c postman -n '__fish_seen_subcommand_from runner; and __fish_seen_subcommand_from regions' -l api-key -d 'Postman API key (defaults to POSTMAN_API_KEY, then the `postman login` session)' -r
-complete -c postman -n '__fish_seen_subcommand_from runner; and __fish_seen_subcommand_from regions' -l json -d 'Output the region list as JSON instead of a table'
+complete -c postman -n '__fish_seen_subcommand_from runner; and __fish_seen_subcommand_from regions' -l json -d 'Print { regions } as JSON, every field present (null when unset)'
 complete -c postman -n '__fish_seen_subcommand_from runner; and __fish_seen_subcommand_from regions' -s h -l help -d 'display help for command'
 
 # ---------- sdk ----------
@@ -1203,11 +1246,11 @@ complete -c postman -n '__fish_seen_subcommand_from spec; and __fish_seen_subcom
 complete -c postman -n '__fish_seen_subcommand_from spec; and __fish_seen_subcommand_from create' -s h -l help -d 'display help for command'
 complete -c postman -n '__fish_seen_subcommand_from spec; and __fish_seen_subcommand_from create' -r -k -a '(__fish_complete_suffix .json)'
 # ---------- spec generate ----------
-complete -c postman -n '__postman_using_subcommand generate collection' -a collection -d 'Generate a Postman collection from a specification.'
+complete -c postman -n '__postman_using_subcommand generate collection' -a collection -d 'Generate a Postman collection from an OpenAPI or AsyncAPI (Kafka) specification. Only Kafka AsyncAPI 2.x and 3.0 specs are supported: the spec must declare a kafka or kafka-secure server.'
 complete -c postman -n '__fish_seen_subcommand_from spec; and __fish_seen_subcommand_from generate' -s h -l help -d 'display help for command'
 # ---------- spec generate collection ----------
 complete -c postman -n '__fish_seen_subcommand_from spec; and __fish_seen_subcommand_from generate; and __fish_seen_subcommand_from collection' -s n -l name -d 'Collection name' -x
-complete -c postman -n '__fish_seen_subcommand_from spec; and __fish_seen_subcommand_from generate; and __fish_seen_subcommand_from collection' -l folder-strategy -d 'Folder strategy: Paths or Tags (default: Paths) (default: "Paths")' -x
+complete -c postman -n '__fish_seen_subcommand_from spec; and __fish_seen_subcommand_from generate; and __fish_seen_subcommand_from collection' -l folder-strategy -d 'Folder strategy: Paths or Tags (default: Paths). OpenAPI only (default: "Paths")' -x
 complete -c postman -n '__fish_seen_subcommand_from spec; and __fish_seen_subcommand_from generate; and __fish_seen_subcommand_from collection' -s w -l workspace -d 'Workspace ID (cloud mode)' -x
 complete -c postman -n '__fish_seen_subcommand_from spec; and __fish_seen_subcommand_from generate; and __fish_seen_subcommand_from collection' -l api-key -d 'Postman API key' -r
 complete -c postman -n '__fish_seen_subcommand_from spec; and __fish_seen_subcommand_from generate; and __fish_seen_subcommand_from collection' -l force -d 'Overwrite the collection if one with this name already exists (local mode)'
@@ -1218,8 +1261,8 @@ complete -c postman -n '__fish_seen_subcommand_from spec; and __fish_seen_subcom
 # ---------- spec sync collection ----------
 complete -c postman -n '__fish_seen_subcommand_from spec; and __fish_seen_subcommand_from sync; and __fish_seen_subcommand_from collection' -l collection-id -d 'Collection ID to sync (required for cloud mode)' -x
 complete -c postman -n '__fish_seen_subcommand_from spec; and __fish_seen_subcommand_from sync; and __fish_seen_subcommand_from collection' -l api-key -d 'Postman API key' -r
-complete -c postman -n '__fish_seen_subcommand_from spec; and __fish_seen_subcommand_from sync; and __fish_seen_subcommand_from collection' -l force -d 'Overwrite hand-written scripts, headers and descriptions that the spec would otherwise drop'
-complete -c postman -n '__fish_seen_subcommand_from spec; and __fish_seen_subcommand_from sync; and __fish_seen_subcommand_from collection' -l dry-run -d 'Report what sync would change and remove without writing anything'
+complete -c postman -n '__fish_seen_subcommand_from spec; and __fish_seen_subcommand_from sync; and __fish_seen_subcommand_from collection' -l force -d 'Overwrite hand-written scripts, headers and descriptions that the spec would otherwise drop (OpenAPI), or collection files that could not be read (AsyncAPI)'
+complete -c postman -n '__fish_seen_subcommand_from spec; and __fish_seen_subcommand_from sync; and __fish_seen_subcommand_from collection' -l dry-run -d 'Report what sync would change and remove without writing anything (OpenAPI only)'
 complete -c postman -n '__fish_seen_subcommand_from spec; and __fish_seen_subcommand_from sync; and __fish_seen_subcommand_from collection' -s h -l help -d 'display help for command'
 # ---------- spec delete ----------
 complete -c postman -n '__fish_seen_subcommand_from spec; and __fish_seen_subcommand_from delete' -s y -l yes -d 'Delete without asking for confirmation first'
@@ -1227,18 +1270,19 @@ complete -c postman -n '__fish_seen_subcommand_from spec; and __fish_seen_subcom
 complete -c postman -n '__fish_seen_subcommand_from spec; and __fish_seen_subcommand_from delete' -s h -l help -d 'display help for command'
 
 # ---------- workspace ----------
-complete -c postman -n '__postman_using_subcommand workspace list prepare push lint get activity create delete pull connect-git disconnect-git diff' -a list -d 'List all available Postman Workspaces'
-complete -c postman -n '__postman_using_subcommand workspace list prepare push lint get activity create delete pull connect-git disconnect-git diff' -a prepare -d 'Prepare local collections and environments for push by validating and regenerating IDs if needed.'
-complete -c postman -n '__postman_using_subcommand workspace list prepare push lint get activity create delete pull connect-git disconnect-git diff' -a push -d 'Push local workspace entities (collections, environments, specifications, mocks and more) to Postman workspace.'
-complete -c postman -n '__postman_using_subcommand workspace list prepare push lint get activity create delete pull connect-git disconnect-git diff' -a lint -d 'Lint the current local Postman workspace: its configuration (.postman/resources.yaml) plus every discovered entity. Use --meta to lint only the configuration.'
-complete -c postman -n '__postman_using_subcommand workspace list prepare push lint get activity create delete pull connect-git disconnect-git diff' -a get -d 'Read a workspace\'s metadata, and optionally the ids of what it holds.'
-complete -c postman -n '__postman_using_subcommand workspace list prepare push lint get activity create delete pull connect-git disconnect-git diff' -a activity -d 'Read a workspace\'s activity feed.'
-complete -c postman -n '__postman_using_subcommand workspace list prepare push lint get activity create delete pull connect-git disconnect-git diff' -a create -d 'Create a Postman workspace and bind it to this git repository.'
-complete -c postman -n '__postman_using_subcommand workspace list prepare push lint get activity create delete pull connect-git disconnect-git diff' -a delete -d 'Permanently delete a workspace and everything in it. Prompts for confirmation unless --yes is passed.'
-complete -c postman -n '__postman_using_subcommand workspace list prepare push lint get activity create delete pull connect-git disconnect-git diff' -a pull -d 'Pull workspace entities from a Postman workspace into the local git-native folder.'
-complete -c postman -n '__postman_using_subcommand workspace list prepare push lint get activity create delete pull connect-git disconnect-git diff' -a connect-git -d 'Connect a Postman workspace to a local git repository.'
-complete -c postman -n '__postman_using_subcommand workspace list prepare push lint get activity create delete pull connect-git disconnect-git diff' -a disconnect-git -d 'Disconnect a Postman workspace from its local git repository.'
-complete -c postman -n '__postman_using_subcommand workspace list prepare push lint get activity create delete pull connect-git disconnect-git diff' -a diff -d 'Preview local-vs-cloud drift before pushing. Read-only: nothing is created, updated or deleted.'
+complete -c postman -n '__postman_using_subcommand workspace list prepare push lint get activity create delete share pull connect-git disconnect-git diff' -a list -d 'List all available Postman Workspaces'
+complete -c postman -n '__postman_using_subcommand workspace list prepare push lint get activity create delete share pull connect-git disconnect-git diff' -a prepare -d 'Prepare local collections and environments for push by validating and regenerating IDs if needed.'
+complete -c postman -n '__postman_using_subcommand workspace list prepare push lint get activity create delete share pull connect-git disconnect-git diff' -a push -d 'Push local workspace entities (collections, environments, specifications, mocks and more) to Postman workspace.'
+complete -c postman -n '__postman_using_subcommand workspace list prepare push lint get activity create delete share pull connect-git disconnect-git diff' -a lint -d 'Lint the current local Postman workspace: its configuration (.postman/resources.yaml) plus every discovered entity. Use --meta to lint only the configuration.'
+complete -c postman -n '__postman_using_subcommand workspace list prepare push lint get activity create delete share pull connect-git disconnect-git diff' -a get -d 'Read a workspace\'s metadata, and optionally the ids of what it holds.'
+complete -c postman -n '__postman_using_subcommand workspace list prepare push lint get activity create delete share pull connect-git disconnect-git diff' -a activity -d 'Read a workspace\'s activity feed.'
+complete -c postman -n '__postman_using_subcommand workspace list prepare push lint get activity create delete share pull connect-git disconnect-git diff' -a create -d 'Create a Postman workspace and bind it to this git repository.'
+complete -c postman -n '__postman_using_subcommand workspace list prepare push lint get activity create delete share pull connect-git disconnect-git diff' -a delete -d 'Permanently delete a workspace and everything in it. Prompts for confirmation unless --yes is passed.'
+complete -c postman -n '__postman_using_subcommand workspace list prepare push lint get activity create delete share pull connect-git disconnect-git diff' -a share -d 'Grant a role on a workspace to one or more people.'
+complete -c postman -n '__postman_using_subcommand workspace list prepare push lint get activity create delete share pull connect-git disconnect-git diff' -a pull -d 'Pull workspace entities from a Postman workspace into the local folder.'
+complete -c postman -n '__postman_using_subcommand workspace list prepare push lint get activity create delete share pull connect-git disconnect-git diff' -a connect-git -d 'Connect a Postman workspace to a local git repository.'
+complete -c postman -n '__postman_using_subcommand workspace list prepare push lint get activity create delete share pull connect-git disconnect-git diff' -a disconnect-git -d 'Disconnect a Postman workspace from its local git repository.'
+complete -c postman -n '__postman_using_subcommand workspace list prepare push lint get activity create delete share pull connect-git disconnect-git diff' -a diff -d 'Preview local-vs-cloud drift before pushing. Read-only: nothing is created, updated or deleted.'
 complete -c postman -n '__fish_seen_subcommand_from workspace' -s h -l help -d 'display help for command'
 # ---------- workspace list ----------
 complete -c postman -n '__fish_seen_subcommand_from workspace; and __fish_seen_subcommand_from list' -s f -l filter -d 'Filter workspaces by name.' -x
@@ -1299,6 +1343,13 @@ complete -c postman -n '__fish_seen_subcommand_from workspace; and __fish_seen_s
 complete -c postman -n '__fish_seen_subcommand_from workspace; and __fish_seen_subcommand_from delete' -l verbose -d 'Show detailed logging'
 complete -c postman -n '__fish_seen_subcommand_from workspace; and __fish_seen_subcommand_from delete' -l timeout -d 'Abort the run after this many milliseconds. Defaults to 30000.' -x
 complete -c postman -n '__fish_seen_subcommand_from workspace; and __fish_seen_subcommand_from delete' -s h -l help -d 'display help for command'
+# ---------- workspace share ----------
+complete -c postman -n '__fish_seen_subcommand_from workspace; and __fish_seen_subcommand_from share' -l user -d 'Who to share with. Repeatable, and each value may be a comma-separated list. A value containing @ is treated as an email address, anything else as a Postman user id.' -x
+complete -c postman -n '__fish_seen_subcommand_from workspace; and __fish_seen_subcommand_from share' -l role -d 'The role to grant. (default: "viewer")' -x
+complete -c postman -n '__fish_seen_subcommand_from workspace; and __fish_seen_subcommand_from share' -l json -d 'Print the outcome as machine-readable JSON.'
+complete -c postman -n '__fish_seen_subcommand_from workspace; and __fish_seen_subcommand_from share' -l timeout -d 'Milliseconds to wait for Postman. Defaults to 30000.' -x
+complete -c postman -n '__fish_seen_subcommand_from workspace; and __fish_seen_subcommand_from share' -l api-key -d 'Postman API key (defaults to your `postman login` session)' -r
+complete -c postman -n '__fish_seen_subcommand_from workspace; and __fish_seen_subcommand_from share' -s h -l help -d 'display help for command'
 # ---------- workspace pull ----------
 complete -c postman -n '__fish_seen_subcommand_from workspace; and __fish_seen_subcommand_from pull' -s y -l yes -d 'Skip all confirmation prompts'
 complete -c postman -n '__fish_seen_subcommand_from workspace; and __fish_seen_subcommand_from pull' -l source-workspace -d 'Pull from a different source workspace.' -x
@@ -1334,7 +1385,6 @@ complete -c postman -n '__fish_seen_subcommand_from context-graph; and __fish_se
 complete -c postman -n '__fish_seen_subcommand_from context-graph; and __fish_seen_subcommand_from ask' -l api-key -d 'Postman API key (falls back to POSTMAN_API_KEY, then a `postman login` session)' -r
 complete -c postman -n '__fish_seen_subcommand_from context-graph; and __fish_seen_subcommand_from ask' -l json -d 'Output the ask record as JSON'
 complete -c postman -n '__fish_seen_subcommand_from context-graph; and __fish_seen_subcommand_from ask' -l no-include-answer -d 'Do not ask the service to include the answer inline'
-complete -c postman -n '__fish_seen_subcommand_from context-graph; and __fish_seen_subcommand_from ask' -l max-steps -d 'Cap the reasoning steps the service may take (its default applies when omitted)' -x
 complete -c postman -n '__fish_seen_subcommand_from context-graph; and __fish_seen_subcommand_from ask' -l interval -d 'With --wait, seconds between polls (default: 2)' -x
 complete -c postman -n '__fish_seen_subcommand_from context-graph; and __fish_seen_subcommand_from ask' -l timeout -d 'With --wait, seconds to wait before giving up (default: 300)' -x
 complete -c postman -n '__fish_seen_subcommand_from context-graph; and __fish_seen_subcommand_from ask' -s h -l help -d 'display help for command'
@@ -1427,7 +1477,6 @@ complete -c postman -n '__fish_seen_subcommand_from describe; and __fish_seen_su
 # ---------- init ----------
 complete -c postman -n '__fish_seen_subcommand_from init' -l json -d 'Emit machine-readable output for agents'
 complete -c postman -n '__fish_seen_subcommand_from init' -l dry-run -d 'Report what would happen without writing anything'
-complete -c postman -n '__fish_seen_subcommand_from init' -l no-fetch -d 'Use the skills bundled with this CLI instead of fetching the latest'
 complete -c postman -n '__fish_seen_subcommand_from init' -l spec -d 'Which spec is authoritative, when more than one could be' -r
 complete -c postman -n '__fish_seen_subcommand_from init' -l visibility -d 'Create and bind a workspace non-interactively (personal, team)' -x
 complete -c postman -n '__fish_seen_subcommand_from init' -s y -l yes -d 'Accept the default for every question instead of asking or stopping'
@@ -1640,6 +1689,7 @@ complete -c postman -n '__fish_seen_subcommand_from secret; and __fish_seen_subc
 complete -c postman -n '__fish_seen_subcommand_from secret; and __fish_seen_subcommand_from create' -l terminal -d 'Enter one secret value through the terminal instead of the default browser form'
 complete -c postman -n '__fish_seen_subcommand_from secret; and __fish_seen_subcommand_from create' -l value-stdin -d 'Read the secret value from stdin instead of prompting; implies --terminal'
 complete -c postman -n '__fish_seen_subcommand_from secret; and __fish_seen_subcommand_from create' -l timeout -d 'Seconds to wait for the browser form (default 300)' -x
+complete -c postman -n '__fish_seen_subcommand_from secret; and __fish_seen_subcommand_from create' -l json -d 'Print the created secrets as machine-readable JSON (never the values)'
 complete -c postman -n '__fish_seen_subcommand_from secret; and __fish_seen_subcommand_from create' -s h -l help -d 'display help for command'
 complete -c postman -n '__fish_seen_subcommand_from secret; and __fish_seen_subcommand_from create' -r -k -a '(__fish_complete_suffix .json)'
 # ---------- secret list ----------
@@ -1649,7 +1699,7 @@ complete -c postman -n '__fish_seen_subcommand_from secret; and __fish_seen_subc
 complete -c postman -n '__fish_seen_subcommand_from secret; and __fish_seen_subcommand_from list' -s h -l help -d 'display help for command'
 
 # ---------- simulation ----------
-complete -c postman -n '__postman_using_subcommand simulation create list get run push deploy update log delete' -a create -d 'Create a simulation that serves several mocks behind one address'
+complete -c postman -n '__postman_using_subcommand simulation create list get run push deploy update log delete' -a create -d 'Create a simulation that serves several mocks behind one address. Add --deploy to also make it a live mock server.'
 complete -c postman -n '__postman_using_subcommand simulation create list get run push deploy update log delete' -a list -d 'List the simulations in your repository or Postman cloud workspace'
 complete -c postman -n '__postman_using_subcommand simulation create list get run push deploy update log delete' -a get -d 'Show a simulation\'s details using its .sim.yaml path if it lives in your repository, or its id if it lives in Postman cloud.'
 complete -c postman -n '__postman_using_subcommand simulation create list get run push deploy update log delete' -a run -d 'Serve a simulation\'s mocks on one local port, routing each by its routeKey. Pass a .sim.yaml path (local) or a Postman simulation id (fetched and run locally).'
@@ -1665,7 +1715,11 @@ complete -c postman -n '__fish_seen_subcommand_from simulation; and __fish_seen_
 complete -c postman -n '__fish_seen_subcommand_from simulation; and __fish_seen_subcommand_from create' -l routing -d 'How callers reach each mock: header or path (default path)' -x
 complete -c postman -n '__fish_seen_subcommand_from simulation; and __fish_seen_subcommand_from create' -s o -l output -d 'Where to save the simulation file in your repository, a file or folder (defaults to postman/simulations)' -r
 complete -c postman -n '__fish_seen_subcommand_from simulation; and __fish_seen_subcommand_from create' -l force -d 'Overwrite the simulation file if it already exists'
-complete -c postman -n '__fish_seen_subcommand_from simulation; and __fish_seen_subcommand_from create' -s w -l workspace -d 'Postman cloud workspace to create the simulation in, by id (defaults to the workspace already linked to this project)' -x
+complete -c postman -n '__fish_seen_subcommand_from simulation; and __fish_seen_subcommand_from create' -s w -l workspace -d 'Postman cloud workspace to create the simulation in (or deploy it to, with --deploy), by id (defaults to the workspace already linked to this project)' -x
+complete -c postman -n '__fish_seen_subcommand_from simulation; and __fish_seen_subcommand_from create' -l deploy -d 'After creating, upload the simulation (and its mocks) to Postman cloud and deploy it to a live mock server (private by default).'
+complete -c postman -n '__fish_seen_subcommand_from simulation; and __fish_seen_subcommand_from create' -l public -d 'With --deploy, let anyone with the link reach the server (default: callers need an API key)'
+complete -c postman -n '__fish_seen_subcommand_from simulation; and __fish_seen_subcommand_from create' -s s -l slug -d 'With --deploy, the short label used in the server\'s web address' -x
+complete -c postman -n '__fish_seen_subcommand_from simulation; and __fish_seen_subcommand_from create' -l json -d 'Print the result (with --deploy, the live server details) as machine-readable data instead of a summary'
 complete -c postman -n '__fish_seen_subcommand_from simulation; and __fish_seen_subcommand_from create' -l api-key -d 'Postman API key (defaults to your `postman login` session)' -r
 complete -c postman -n '__fish_seen_subcommand_from simulation; and __fish_seen_subcommand_from create' -s h -l help -d 'display help for command'
 # ---------- simulation list ----------
@@ -1676,7 +1730,7 @@ complete -c postman -n '__fish_seen_subcommand_from simulation; and __fish_seen_
 complete -c postman -n '__fish_seen_subcommand_from simulation; and __fish_seen_subcommand_from list' -r -k -a '(__fish_complete_suffix .json)'
 # ---------- simulation get ----------
 complete -c postman -n '__fish_seen_subcommand_from simulation; and __fish_seen_subcommand_from get' -l api-key -d 'Postman API key (defaults to your `postman login` session)' -r
-complete -c postman -n '__fish_seen_subcommand_from simulation; and __fish_seen_subcommand_from get' -l json -d 'Print the details as machine-readable data instead of a table'
+complete -c postman -n '__fish_seen_subcommand_from simulation; and __fish_seen_subcommand_from get' -l json -d 'Print the details as machine-readable data instead of a summary'
 complete -c postman -n '__fish_seen_subcommand_from simulation; and __fish_seen_subcommand_from get' -s h -l help -d 'display help for command'
 # ---------- simulation run ----------
 complete -c postman -n '__fish_seen_subcommand_from simulation; and __fish_seen_subcommand_from run' -s e -l environment -d 'Path to a file of environment variables for the mocks (relative or absolute)' -r
@@ -1689,7 +1743,7 @@ complete -c postman -n '__fish_seen_subcommand_from simulation; and __fish_seen_
 complete -c postman -n '__fish_seen_subcommand_from simulation; and __fish_seen_subcommand_from run' -l no-history -d 'Do not record this run in the simulation\'s start history'
 complete -c postman -n '__fish_seen_subcommand_from simulation; and __fish_seen_subcommand_from run' -l output -d 'Live output format: auto (default, human-readable logs) or ndjson (one JSON event per line on stdout, ending with a "summary" event — for CI or other non-interactive use) (default: "auto")' -x
 complete -c postman -n '__fish_seen_subcommand_from simulation; and __fish_seen_subcommand_from run' -l verbose -d 'Show request and response headers and bodies for each request. By default each request prints one line, plus any applied scenario or error.'
-complete -c postman -n '__fish_seen_subcommand_from simulation; and __fish_seen_subcommand_from run' -l proxy -d 'Serve the mocks behind a local HTTP(S) forward proxy instead of one routed port, so a repo under test can point HTTP_PROXY/HTTPS_PROXY at it and reach each mock by hostname without code changes. Requires a simulation.yaml (routing config), not a .sim.yaml.'
+complete -c postman -n '__fish_seen_subcommand_from simulation; and __fish_seen_subcommand_from run' -l proxy -d 'Serve the mocks behind a local HTTP(S) forward proxy instead of one routed port, so a repo under test can point HTTP_PROXY/HTTPS_PROXY at it and reach each mock by hostname without code changes. Each mock is reached on the hostnames its `origin:` declares; a request to any other host reaches the real host unchanged.'
 complete -c postman -n '__fish_seen_subcommand_from simulation; and __fish_seen_subcommand_from run' -l proxy-port -d 'Port for the proxy server. Distinct from --port, which is the one-port run\'s own port. (default: 7001)' -x
 complete -c postman -n '__fish_seen_subcommand_from simulation; and __fish_seen_subcommand_from run' -l scenario -d 'Scenario each mock serves, sent as both pm-mock-scenario and x-mock-scenario. (default: "default")' -x
 complete -c postman -n '__fish_seen_subcommand_from simulation; and __fish_seen_subcommand_from run' -l session -d 'Session id to select via the x-mock-session header (default: a generated id).' -x
@@ -1700,14 +1754,17 @@ complete -c postman -n '__fish_seen_subcommand_from simulation; and __fish_seen_
 # ---------- simulation push ----------
 complete -c postman -n '__fish_seen_subcommand_from simulation; and __fish_seen_subcommand_from push' -s w -l workspace -d 'Postman cloud workspace to upload to, by id (defaults to the workspace already linked to this project)' -x
 complete -c postman -n '__fish_seen_subcommand_from simulation; and __fish_seen_subcommand_from push' -l api-key -d 'Postman API key (defaults to your `postman login` session)' -r
+complete -c postman -n '__fish_seen_subcommand_from simulation; and __fish_seen_subcommand_from push' -l json -d 'Print the result as machine-readable data'
 complete -c postman -n '__fish_seen_subcommand_from simulation; and __fish_seen_subcommand_from push' -s h -l help -d 'display help for command'
 # ---------- simulation deploy ----------
 complete -c postman -n '__fish_seen_subcommand_from simulation; and __fish_seen_subcommand_from deploy' -s w -l workspace -d 'Postman cloud workspace that will own the server, by id (defaults to the workspace already linked to this project)' -x
 complete -c postman -n '__fish_seen_subcommand_from simulation; and __fish_seen_subcommand_from deploy' -s n -l name -d 'Name for the mock server (you are asked for one if you skip this)' -x
 complete -c postman -n '__fish_seen_subcommand_from simulation; and __fish_seen_subcommand_from deploy' -s s -l slug -d 'Short label used in the server\'s web address, e.g. "my-sim" (you are asked for one if you skip this)' -x
-complete -c postman -n '__fish_seen_subcommand_from simulation; and __fish_seen_subcommand_from deploy' -l private -d 'Require a Postman API key to reach the server. Public by default.'
-complete -c postman -n '__fish_seen_subcommand_from simulation; and __fish_seen_subcommand_from deploy' -s y -l yes -d 'Use the defaults and skip all questions (public)'
+complete -c postman -n '__fish_seen_subcommand_from simulation; and __fish_seen_subcommand_from deploy' -l public -d 'Let anyone with the link reach the server. Private by default (callers must send a Postman API key).'
+complete -c postman -n '__fish_seen_subcommand_from simulation; and __fish_seen_subcommand_from deploy' -l private -d 'Require a Postman API key to reach the server (the default; kept for compatibility).'
+complete -c postman -n '__fish_seen_subcommand_from simulation; and __fish_seen_subcommand_from deploy' -s y -l yes -d 'Use the defaults and skip all questions (private)'
 complete -c postman -n '__fish_seen_subcommand_from simulation; and __fish_seen_subcommand_from deploy' -l api-key -d 'Postman API key (defaults to your `postman login` session)' -r
+complete -c postman -n '__fish_seen_subcommand_from simulation; and __fish_seen_subcommand_from deploy' -l json -d 'Print the live server details as machine-readable data instead of a summary (asks no questions)'
 complete -c postman -n '__fish_seen_subcommand_from simulation; and __fish_seen_subcommand_from deploy' -s h -l help -d 'display help for command'
 # ---------- simulation update ----------
 complete -c postman -n '__fish_seen_subcommand_from simulation; and __fish_seen_subcommand_from update' -s n -l name -d 'Rename the simulation' -x
@@ -1732,6 +1789,7 @@ complete -c postman -n '__fish_seen_subcommand_from simulation; and __fish_seen_
 # ---------- simulation delete ----------
 complete -c postman -n '__fish_seen_subcommand_from simulation; and __fish_seen_subcommand_from delete' -s y -l yes -d 'Delete without asking for confirmation first'
 complete -c postman -n '__fish_seen_subcommand_from simulation; and __fish_seen_subcommand_from delete' -l api-key -d 'Postman API key, used with a Postman cloud id (defaults to your `postman login` session)' -r
+complete -c postman -n '__fish_seen_subcommand_from simulation; and __fish_seen_subcommand_from delete' -l json -d 'Print the result as machine-readable data (requires --yes)'
 complete -c postman -n '__fish_seen_subcommand_from simulation; and __fish_seen_subcommand_from delete' -s h -l help -d 'display help for command'
 
 # ---------- team ----------