@staff0rd/assist 0.1043.0 → 0.1044.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -3,4 +3,4 @@ title: Asking for a manual check
3
3
  when: askQuestion
4
4
  ---
5
5
 
6
- In an assist session (`ASSIST_SESSION=1`), when you need the user to test something by hand, don't write the check up in chat. Write it as JSON (`{"title": ..., "steps": [...], "before": [...], "changed": ...}`: `title` is the expected outcome in at most 60 characters, `steps` are 1-4 steps of at most 90 characters each, optional `before` lists at most 4 short setup or restart chips, and optional `changed` is one sentence of at most 160 characters) to a scratch file and run `assist ask-check --json - < <file>` as a background task, doing no other work until it returns. It opens in the session's preview pane and blocks until the user answers Works or Doesn't work, printing the result and any note they added. Dismissing exits non-zero, meaning the user gave no result; don't assume it passed. Raise one check per thing to test, and keep any chat summary to a few lines. If it exits non-zero before opening (not in an assist session, disabled, or the session isn't live), ask in chat instead.
6
+ When you need the user to test something by hand, don't write the check up in chat. Write it as JSON (`{"title": ..., "steps": [...], "before": [...], "changed": ...}`: `title` is the expected outcome in at most 60 characters, `steps` are 1-4 steps of at most 90 characters each, optional `before` lists at most 4 short setup or restart chips, and optional `changed` is one sentence of at most 160 characters) to a scratch file and run `assist ask-check --json - < <file>` as a background task, doing no other work until it returns. It opens in the session's preview pane and blocks until the user answers Works or Doesn't work, printing the result and any note they added. Dismissing exits non-zero, meaning the user gave no result; don't assume it passed. Raise one check per thing to test, and keep any chat summary to a few lines. If it exits non-zero before opening (disabled, or the session isn't live), ask in chat instead.
@@ -3,4 +3,4 @@ title: Asking questions
3
3
  when: askQuestion
4
4
  ---
5
5
 
6
- In an assist session (`ASSIST_SESSION=1`), don't use the built-in AskUserQuestion tool; the user answers from the session's web preview pane, which can't drive the terminal prompt. Write the same AskUserQuestion input as JSON (`{"questions": [...]}`, 1-4 questions each with `question`, `header`, `multiSelect` and 2-4 `options` of `label`, `description` and optional `preview`) to a scratch file and run `assist ask-question --json - < <file>` as a background task, doing no other work until it returns. It opens as a form in the preview pane and blocks until answered. Answering exits 0 and prints the same answer text AskUserQuestion returns; dismissing exits non-zero, meaning the user declined to answer. To revise a still-pending question, re-run it directly; the earlier task then exits 0 as superseded — ignore its result. Outside an assist session it exits non-zero, so use AskUserQuestion.
6
+ Don't use the built-in AskUserQuestion tool; the user answers from the session's web preview pane, which can't drive the terminal prompt. Write the same AskUserQuestion input as JSON (`{"questions": [...]}`, 1-4 questions each with `question`, `header`, `multiSelect` and 2-4 `options` of `label`, `description` and optional `preview`) to a scratch file and run `assist ask-question --json - < <file>` as a background task, doing no other work until it returns. It opens as a form in the preview pane and blocks until answered. Answering exits 0 and prints the same answer text AskUserQuestion returns; dismissing exits non-zero, meaning the user declined to answer. To revise a still-pending question, re-run it directly; the earlier task then exits 0 as superseded — ignore its result.
@@ -1,6 +1,6 @@
1
1
  ---
2
2
  title: Asking for sign-off
3
- when: always
3
+ when: assistSession
4
4
  ---
5
5
 
6
- When a plan, summary or proposed decision needs the user's sign-off before you act on it, don't ask in chat. Write it as markdown to a scratch file and run `assist ask --title '<title>' --body - < <file>` as a background task, doing no other work until it returns. It opens in the session's web preview pane with approve, reject and inline comments, and blocks until the user decides. Approval exits 0 and prints any comments to fold in; rejection exits non-zero with the reason and comments — revise and re-run. To revise a still-pending preview, re-run it directly without stopping the earlier task; that task then exits 0 as superseded — ignore its result. Outside a web session it just prints the markdown, so ask in chat.
6
+ When a plan, summary or proposed decision needs the user's sign-off before you act on it, don't ask in chat. Write it as markdown to a scratch file and run `assist ask --title '<title>' --body - < <file>` as a background task, doing no other work until it returns. It opens in the session's web preview pane with approve, reject and inline comments, and blocks until the user decides. Approval exits 0 and prints any comments to fold in; rejection exits non-zero with the reason and comments — revise and re-run. To revise a still-pending preview, re-run it directly without stopping the earlier task; that task then exits 0 as superseded — ignore its result.
@@ -3,8 +3,8 @@
3
3
  "assist@staff0rd.github.io": {
4
4
  "updates": [
5
5
  {
6
- "version": "0.1042.1",
7
- "update_link": "https://github.com/staff0rd/assist/releases/download/v0.1042.1/assist-extension.xpi"
6
+ "version": "0.1043.0",
7
+ "update_link": "https://github.com/staff0rd/assist/releases/download/v0.1043.0/assist-extension.xpi"
8
8
  }
9
9
  ]
10
10
  }