@ouro.bot/cli 0.1.0-alpha.460 → 0.1.0-alpha.461

package/changelog.json

@@ -1,6 +1,14 @@
 {
   "_note": "This changelog is maintained as part of the PR/version-bump workflow. Agent-curated, not auto-generated. Agents read this file directly via read_file to understand what changed between versions.",
   "versions": [
+    {
+      "version": "0.1.0-alpha.461",
+      "changes": [
+        "Agent Mail golden paths are now an explicit numbered system-prompt contract, so agents can name and validate HEY archive import, native Screener mail, cross-sense reaction, and Ouro Outlook audit instead of collapsing them into generic diagnostics.",
+        "Empty Mailroom tool guidance now repeats that same four-path checklist before claiming setup works, including the HEY-to-work-object path that catches unimported travel mail.",
+        "Prompt and Mailroom tests now lock the canonical golden-path language so future agents keep the setup conversation oriented without asking the human to remember the checklist."
+      ]
+    },
     {
       "version": "0.1.0-alpha.460",
       "changes": [

package/dist/mind/prompt.js

@@ -470,7 +470,13 @@ function senseRuntimeGuidance(channel, preReadStatusLines) {
     lines.push("mail setup truth: HEY archive bootstrap is human-exported MBOX only. I ask for the browser-downloaded MBOX path, then I run `ouro mail import-mbox --file <path> --owner-email <email> --source hey --agent <agent>` myself and verify the import.");
     lines.push("mail setup truth: an empty Mailroom result is not proof the human's HEY inbox is empty. If `mail_recent`/`mail_search` reports no visible mail or no delegated mail, I treat onboarding/import/forwarding as unverified and guide the setup/import flow before reasoning from the absence of messages.");
     lines.push("mail setup truth: verify with `ouro status`, `ouro doctor`, bounded mail tools (`mail_recent`, `mail_search`, `mail_thread`, `mail_access_log`), and the read-only Outlook Mailbox tab. `ouro doctor` is installation-wide; do not invent `ouro doctor --agent <agent>`.");
-    lines.push("mail validation golden paths: HEY import updates a real work object; native send/receive exercises Screener allow/discard and recovery; mail can trigger another configured sense; Ouro Outlook audits imports, decisions, sends, and access logs.");
+    lines.push("mail validation contract: when a human asks for Agent Mail golden paths, I mean these exact four checks before claiming setup works:");
+    lines.push("- golden path 1, HEY archive to work object: import the human-provided HEY MBOX and use delegated mail to update a real work object, such as travel plans.");
+    lines.push("- golden path 2, native mail and Screener: send and receive agent-native mail, confirm unknown senders enter Screener, get family authorization for allow/discard, verify sender policy, and confirm discarded mail is recoverable.");
+    lines.push(channel === "mcp"
+        ? "- golden path 3, cross-sense reaction: use a mail-derived update or decision to trigger another configured sense when available."
+        : "- golden path 3, cross-sense reaction: use a mail-derived update or decision to trigger another configured sense, such as texting the family member on iMessage when BlueBubbles is available.");
+    lines.push("- golden path 4, Ouro Outlook audit: inspect the read-only mailbox UI for imported mail, native inbound, Screener decisions, outbound draft/send records, and mail access logs.");
     lines.push("mail setup boundaries: do not invent `ouro auth verify --provider mail`, HEY OAuth, HEY IMAP, `ouro mcp call mail ...`, policy flags, autonomous sending, destructive mail actions, or production MX/DNS/forwarding changes. HEY export, HEY forwarding, DNS, MX cutover, sending, and destructive actions require explicit human confirmation.");
     if (channel === "cli") {
         lines.push("cli is interactive: it is available when the user opens it, not something `ouro up` daemonizes.");

package/dist/repertoire/tools-mail.js

@@ -166,7 +166,11 @@ async function renderEmptyMailResult(input) {
             ...renderSourceGrantStatus(input.config, input.agentId),
             "interpretation: this is not evidence that the human's HEY inbox is empty; Agent Mail has not yet received or imported mail visible to this agent.",
             `agent next move: guide setup from docs/agent-mail-setup.md. If HEY mail is needed, ensure the delegated hey alias exists, ask the human for the exported MBOX file path, run ouro mail import-mbox --agent ${input.agentId} --owner-email <human-email> --source hey --file <mbox-path>, then verify with mail_recent/mail_search/Ouro Outlook.`,
-            "validation golden paths: HEY import updates a real work object; native send/receive goes through Screener; email can trigger another sense such as iMessage; Ouro Outlook audits the full story.",
+            "validation golden paths before claiming setup works:",
+            "1. HEY archive to work object: import the human-provided HEY MBOX and use delegated mail to update a real work object, such as travel plans.",
+            "2. Native mail and Screener: send and receive agent-native mail, confirm unknown senders enter Screener, get family authorization for allow/discard, verify sender policy, and confirm discarded mail is recoverable.",
+            "3. Cross-sense reaction: use a mail-derived update or decision to trigger another configured sense, such as texting the family member on iMessage when BlueBubbles is available.",
+            "4. Ouro Outlook audit: inspect the read-only mailbox UI for imported mail, native inbound, Screener decisions, outbound draft/send records, and mail access logs.",
         ].join("\n");
     }
     if (input.scope === "delegated" || input.source) {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@ouro.bot/cli",
-  "version": "0.1.0-alpha.460",
+  "version": "0.1.0-alpha.461",
   "main": "dist/heart/daemon/ouro-entry.js",
   "bin": {
     "cli": "dist/heart/daemon/ouro-bot-entry.js",