@forge/cli-shared

Index: package/out/ui/text.js
===================================================================
--- package/out/ui/text.js
+++ package/out/ui/text.js
@@ -1103,8 +1103,9 @@
     tunnel: {
         cmd: 'start a tunnel to connect your local code with the app running in the development environment',
         optionDebugger: 'enable debugger mode',
         debuggerPort: 'starting port to use for debugging, multiple handlers will get subsequent ports. It is only used for Node runtime debugger',
+        debuggerHost: 'host to bind the Node runtime debuggers to, default is 127.0.0.1',
         functionHandlers: 'list of function handlers declared on manifest to debug, separated by space. This option must be specified if debug mode is enabled.  It is only used for Node runtime debugger',
         preamble: 'Tunnel redirects requests you make to your local machine. This occurs for any Atlassian site where your app is installed in the specific development environment. You will not see requests from other users.',
         startingTunnel: (environmentKey, envType) => `Tunnelling to: ${exports.Text.env.displayEnvironment(environmentKey, envType)}`,
         startedServer: (port) => `Listening for requests on local port ${port}...`,
@@ -1117,8 +1118,9 @@
         startingContainerService: (serviceKey) => `Starting containers for service: ${serviceKey}`,
         functionHandlersMustBeDefined: `${chalk_1.default.bold('--debugFunctionHandlers')} flag must be defined in debug mode.`,
         debugArgumentNameMismatch: (arg) => `Arguments of ${chalk_1.default.bold('--debugFunctionHandlers')}, namely '${arg}', must be function handlers defined in the manifest.`,
         invalidDebugStartingPortNumber: (port) => `${chalk_1.default.bold('--debugStartingPort')} ${port} must be a valid port number.`,
+        invalidDebugHost: (host) => `${chalk_1.default.bold('--debugHost')} ${host} must be a valid IPv4 or IPv6 address.`,
         unableToAuthenticateDocker: (errCode) => `Docker authentication process exited with code: ${errCode}.`,
         unableToPullProxySidecarImage: (errMessage) => `Unable to pull the proxy sidecar image. Make sure to run 'forge containers docker-login' first. Full error: ${errMessage}`,
         unableToStartDockerComposeStack: (errMessage) => `Cannot start Docker Compose stack. This usually happens when Docker isn't running or the provided manifest config is incorrect (e.g. configured Docker image doesn't exist). To fix this: Start a Docker engine, ensure the manifest config is correct, then retry the command. Full error: ${errMessage}`,
         UnableToParseDockerComposeFileError: (serviceKey, errMessage) => `Unable to parse the Docker Compose file for service: ${serviceKey}. Please ensure that the manifest tunnel config is correct. Full error: ${errMessage}`,
@@ -1549,11 +1551,11 @@
             description: 'Commands for managing modules in your app'
         },
         add: {
             description: 'add a module to your Forge App',
-            optionModuleType: 'module type to add (e.g. jira:issuePanel, confluence:macro, etc.)',
+            optionModuleType: 'module type to add (e.g. jira:issuePanel, jiraServiceManagement:portalFooter, confluence:macro, etc.)',
             optionUiType: 'UI framework (ui-kit, custom-ui)',
-            optionProduct: 'target product (Jira, Confluence, etc.)',
+            optionProduct: 'target product (Jira, Jira Service Management, Confluence, etc.)',
             optionDryRun: 'show what would be generated',
             optionForce: 'overwrite existing files and upgrade conflicting dependencies to template versions',
             optionNoInstall: 'skip installing dependencies',
             promptSelectProduct: 'select a product',
@@ -1613,15 +1615,15 @@
             errorResourcePathConflict: (resourceKey, existing, incoming) => `Resource '${resourceKey}' already declares path '${existing}', but the new module wants '${incoming}'. Resources sharing a key must share a path.`
         },
         list: {
             description: 'list available module templates',
-            optionProduct: 'filter by product (Jira, Confluence, etc.)',
+            optionProduct: 'filter by product (Jira, Jira Service Management, Confluence, etc.)',
             optionUiType: 'filter by UI framework (ui-kit, custom-ui)'
         },
         info: {
             description: 'show details about a module template',
             optionModuleType: 'module key or template name, (e.g. jira:issuePanel, confluence:macro, etc.)',
-            optionProduct: 'filter by product (Jira, Confluence, etc.)',
+            optionProduct: 'filter by product (Jira, Jira Service Management, Confluence, etc.)',
             optionUiType: 'filter by UI framework (ui-kit, custom-ui)'
         },
         errors: {
             bifrostIndexInvalid: 'Error: expected array of templates',