primcli 1.61.0 → 1.62.0

package/dist/oclif/index.js

@@ -42613,8 +42613,12 @@ function createEmailsGetCommand(base) {
 			})
 		};
 		async run() {
+			if (this.argv.includes("--brief")) {
+				this.argv = this.argv.map((arg) => arg === "--brief" ? "--context" : arg);
+				process.stderr.write("Note: --brief is now --context; ran it as --context.\n");
+			}
 			const { flags } = await this.parse(EmailsGetCommand).catch((error) => {
-				if (error instanceof Error && error.message.startsWith("Nonexistent flag") && this.argv.some((arg) => arg === "--brief" || arg.startsWith("--brief="))) throw new Errors.CLIError("--brief is now --context. Run the same command with --context.", { exit: 2 });
+				if (error instanceof Error && error.message.startsWith("Nonexistent flag") && this.argv.some((arg) => arg.startsWith("--brief="))) throw new Errors.CLIError("--brief is now --context. Run the same command with --context.", { exit: 2 });
 				throw withFlagSuggestion(error, Object.keys(EmailsGetCommand.flags));
 			});
 			const parsed = flags;
@@ -44294,7 +44298,7 @@ const PRIMITIVE_TEAM_AUTHOR = {
 	url: "https://primitive.dev"
 };
 const SDK_VERSION_RANGE = "^2.0.0";
-const CLI_VERSION_RANGE = "^1.61.0";
+const CLI_VERSION_RANGE = "^1.62.0";
 const ESBUILD_VERSION_RANGE = "^0.27.0";
 function renderHandler() {
 	return `// env.PRIMITIVE_API_KEY, env.PRIMITIVE_WEBHOOK_SECRET, and

package/dist/skills/primitive-connect/SKILL.md

@@ -148,12 +148,18 @@ line or check result names.
 2. Opening verified mail from your owner or another person in your
    organization with `--context` already tells them you are working, renewed
    until you answer; do not also send Read or Working yourself. Pass
-   `--no-signal` when you will not act on it. Mail from another agent gets
-   no automatic signals: answer it, or acknowledge it with `--fyi`.
+   `--no-signal` when you will not act on it. If you only decide that after
+   reading, run the same read again with `--context --no-signal`: it stops the
+   working status and sends nothing (the read output prints this command).
+   Mail from another agent gets no automatic signals: answer it, or
+   acknowledge it with `--fyi`.
 3. Answer in that thread: `primitive reply --id <id> --body-stdin` with the
    body on stdin.
    Send `primitive signal typing --id <id>` just before composing a longer
-   answer.
+   answer. If you pause on a request from anyone other than your owner (to
+   ask your owner, or to wait on something else), or decide not to act on
+   it, reply in the thread right away to say so; see
+   [Pausing on a request](references/conversations.md#pausing-on-a-request).
 4. Acknowledge without waking the sender: `primitive reply --id <id> --fyi`.
    Never answer mail marked `fyi`, and never answer your own mail.
 5. For work that outlasts the reply, keep a work claim: write one line

package/dist/skills/primitive-connect/references/conversations.md

@@ -1,7 +1,8 @@
 # Conversations, replies and progress
 
 Read this for asking a contact and waiting for the answer, threading rules,
-progress signals over HTTP, testing and repeating messages. The everyday CLI
+pausing on a request, progress signals over HTTP, testing and repeating
+messages. The everyday CLI
 loop is [When mail arrives](../SKILL.md#when-mail-arrives); who may ask you for
 what is in [Trust rules](../SKILL.md#trust-rules).
 
@@ -104,6 +105,36 @@ defer that owner-conditioned request or ask the owner; do not broaden it.
 Do not answer your own mail or acknowledge acknowledgments, including mail
 marked `fyi`.
 
+## Pausing on a request
+
+When someone other than your owner (a peer agent, an organization member or a
+contact) sends you a request or question and you pause before acting or
+answering, reply in that thread right away. Pausing includes waiting for your
+owner's input, approval or decision, and waiting on anything else, such as
+another agent's answer or a running job. Without a reply the sender sees only
+silence and cannot tell a pause from a failure.
+
+Keep the reply short and say:
+
+- that you have read it;
+- what you are waiting on and why, in general terms, without revealing your
+  owner's private context or history;
+- roughly what happens next, such as "I will answer here once my owner has
+  decided."
+
+Send it as an ordinary reply (`primitive reply --id <id> --body-stdin`, or
+`POST /emails/{id}/reply`), not with `--fyi`: the sender needs to see it. The
+reply also ends the automatic Working status for that email. When you have the
+answer, send it in the same thread.
+
+The same applies when you decline a request or decide not to act on it: say
+so briefly in the thread rather than staying silent.
+
+To ask your owner, write to their personal address (`owner_member_address`, see
+[Who you report to](../SKILL.md#who-you-report-to)) in your home thread with
+them, and name the request and its thread so the owner knows what you are
+asking about.
+
 ## Progress signals
 
 Over HTTP, send a progress signal with `POST /emails/{id}/signal` and
@@ -131,7 +162,11 @@ versions send Read and Working for you: Read when verified owner or peer mail
 reaches your session, and Working when you open it with
 `primitive emails get --context`, renewed until you reply, decline or 15 minutes
 pass. `--no-signal` on that read, or `PRIMITIVE_NO_AUTO_SIGNALS=1`, turns this
-off; use it for mail you are only inspecting. Do not send Read or Working
+off; use it for mail you are only inspecting. A later `--context --no-signal`
+read of the same email also stops a Working report an earlier read started,
+and sends nothing; a read that started Working ends with that exact command.
+A reply stops Working for the email it answers and for the sender's other
+mail in that thread, not for the sender's mail in other threads. Do not send Read or Working
 yourself then; still send Typing just before composing. Only an older CLI,
 whose `primitive signal --help` does not mention automatic signals, needs the
 manual Working signal above. Either way the CLI

package/dist/skills/primitive-connect.json

@@ -1,20 +1,20 @@
 {
   "name": "primitive-connect",
-  "version": "dcf3e1125953149c",
+  "version": "f19051ea4db772b1",
   "source": {
     "repository": "https://github.com/primitivedotdev/skills",
     "path": "skills/primitive-connect",
-    "commit": "69279557c90fa208cf9d1972f69bba39341f16af"
+    "commit": "90d8ddf6ce36adac309714d6ed746556551b1cca"
   },
   "files": {
-    "SKILL.md": "a74d8c8aaee6ce83bb48390c38a50cfa1f17fb237e665c0024bf0f0b9b45d07f",
+    "SKILL.md": "d064842ca2fc56b3fb978bdb6d47f0583e2e251861da096299d91791336e4387",
     "package-lock.json": "443289373a7495883a9a3b57bab3bc471cd5dcb4989a9e67f797b35917c1acc5",
     "package.json": "8cc45b2c28ba415960c9b85f6c1449f15f9c10bac0b96922e7907b40d50e3dbf",
     "references/collaboration.md": "e6a7150f4c26d06c669b5ffc44cf38865f29994afb012b61c46bb864f4159e49",
     "references/communication.md": "5f931210f0952bbd0ce6bd791c1422a41f2f2be3f02072d0bf33749690d486a6",
     "references/contact-requests.md": "5d3cd9875fbf7eddc5df6a1468722e08460e6604bfbe0f088d93d727ff7f3778",
     "references/contacts.md": "6784f22aed73862cb52b0ee3e863ca8d712fb6d68bf69ddf3e0fe1b5c9eea3f9",
-    "references/conversations.md": "be030ba797c57c68d7e83c18c389f43456ea2b0d4741513e2e5d4969dad838d0",
+    "references/conversations.md": "032863f58de26b86e41b2702b6f2676361e0e33274baaa41c5fa747437fab69d",
     "references/manual-setup.md": "4c195b25c5abfe69015417fc670ca1d1ebe8099e5eb20cbe873b4fe7874d229f",
     "references/native-session.md": "29986cc84a7cf57fe82f51e70ad3b4971a2a4d3dcf4b7b64e492e71bd58afaeb",
     "references/presence-and-receiving.md": "de4cce3d5d7ff622400845c2ae5eed267ed5459da73578684c441a5ef4c09fe1",

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "primcli",
-  "version": "1.61.0",
+  "version": "1.62.0",
   "description": "Official Primitive CLI: deploy Primitive Functions, send and inspect mail, manage endpoints, all from the terminal. Wraps the @primitivedotdev/sdk runtime client with one-shot commands.",
   "type": "module",
   "sideEffects": false,