@staff0rd/assist 0.660.0 → 0.660.2

package/dist/index.js

@@ -6,7 +6,7 @@ import { Command } from "commander";
 // package.json
 var package_default = {
   name: "@staff0rd/assist",
-  version: "0.660.0",
+  version: "0.660.2",
   type: "module",
   main: "dist/index.js",
   bin: {
@@ -23278,7 +23278,7 @@ function registerCreateIssue(issueCommand) {
     []
   ).addHelpText(
     "after",
-    "\nThere is no What/Why/How template: an issue reports a problem, and the target repo's own issue template is unknowable from here. Write the body as the repo's maintainers would expect.\nIn an assist web session the title and body are previewed for approve/reject first (with inline comments); nothing is created until it is approved.\nThe reviewer may also drop or paste screenshots or video into the pane; on approval these are appended to the issue body under a ## Screenshots section automatically, and on rejection they are discarded \u2014 so never author that section yourself.\n--type, --parent, --project, --status and --label are all resolved before the preview, so an unknown name, an unreadable parent, a missing project scope or --status without --project creates nothing.\nA bare --parent number is read against --repo, or the current repo; a parent in another repository is allowed.\nThe project scope is needed for --project: gh auth refresh -h github.com -s project"
+    "\nThere is no What/Why/How template: an issue reports a problem, and the target repo's own issue template is unknowable from here. Write the body as the repo's maintainers would expect.\nIn an assist web session the title and body are previewed for approve/reject first (with inline comments); nothing is created until it is approved.\nThe reviewer may also drop or paste screenshots or video into the pane; on approval these are appended to the issue body under a ## Screenshots section automatically, and on rejection they stay attached and reappear in the preview you re-propose \u2014 so never author that section yourself.\n--type, --parent, --project, --status and --label are all resolved before the preview, so an unknown name, an unreadable parent, a missing project scope or --status without --project creates nothing.\nA bare --parent number is read against --repo, or the current repo; a parent in another repository is allowed.\nThe project scope is needed for --project: gh auth refresh -h github.com -s project"
   ).action(createIssue);
 }
 
@@ -27734,8 +27734,9 @@ as numbered quoted-span + note pairs on stderr. Address every comment (and the
 reason), then run the command again to re-preview the revised PR. Repeat until it
 is approved. The reviewer may also drop or paste screenshots or video into the
 pane; on approval these are appended to the PR body under a ## Screenshots section
-automatically (they are discarded on rejection), so you never author that section
-yourself. Just compose the sections and run the command.`;
+automatically; on rejection they stay attached and reappear in the preview you
+re-propose, so you never author that section yourself. Just compose the sections
+and run the command.`;
 function raiseHelpText(promptJira, promptGithub, draft) {
   const config = loadConfig().prs;
   const jira = promptJira ?? config?.promptJira ?? false;

package/package.json

@@ -1,6 +1,6 @@
 {
 	"name": "@staff0rd/assist",
-	"version": "0.660.0",
+	"version": "0.660.2",
 	"type": "module",
 	"main": "dist/index.js",
 	"bin": {