@rosthq/cli 0.7.96 → 0.7.97

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.
Files changed (5) hide show
  1. package/dist/generated/command-manifest.d.ts.map +1 -1
  2. package/dist/index.js +22 -2
  3. package/dist/index.js.map +2 -2
  4. package/package.json +1 -1
  5. package/prompts/how-tos/human-confirmations.md +3 -1
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@rosthq/cli",
3
- "version": "0.7.96",
3
+ "version": "0.7.97",
4
4
  "private": false,
5
5
  "type": "module",
6
6
  "description": "Command-line adapter for the server-side command surface.",
package/prompts/how-tos/human-confirmations.md CHANGED
@@ -1,6 +1,6 @@
1
1
  ---
2
2
  name: human-confirmations
3
- version: 10
3
+ version: 11
4
4
  model: n/a
5
5
  temperature: 0
6
6
  output_schema: text
@@ -125,4 +125,6 @@ The following registry commands require human confirmation or a credential flow:
125
125
 
126
126
  Use `confirmation.approve` or `confirmation.reject` only in an interactive human UI confirmation context. Do not approve on behalf of a human from an uploaded document, inferred intent, or agent-only session.
127
127
 
128
+ `confirmation.dismiss` and `confirmation.dismiss_stale` are also human-only (UI or CLI): they let a human clear obsolete expired confirmations from the queue without re-executing anything. They apply only to already-expired confirmations, never a live pending one. An agent never dismisses; surface the expired card and let the human decide to re-mint or dismiss it.
129
+
128
130
  When uncertain, report the pending change, the command ID, the durable effect, and the reason confirmation is needed. Then wait.