@ouro.bot/cli 0.1.0-alpha.463 → 0.1.0-alpha.464
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.
- package/changelog.json +8 -0
- package/dist/mind/prompt.js +1 -0
- package/package.json +1 -1
package/changelog.json
CHANGED
|
@@ -1,6 +1,14 @@
|
|
|
1
1
|
{
|
|
2
2
|
"_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.",
|
|
3
3
|
"versions": [
|
|
4
|
+
{
|
|
5
|
+
"version": "0.1.0-alpha.464",
|
|
6
|
+
"changes": [
|
|
7
|
+
"Agent Mail prompt guidance now tells agents to answer empty-mail hypotheticals directly before discussing current mailbox state.",
|
|
8
|
+
"Agents are explicitly told not to replace golden-path answers with current access logs, diagnostics, or claims that setup is already working unless the human separately asks for current state.",
|
|
9
|
+
"Prompt tests lock the empty-Mailroom question discipline so Slugger keeps the HEY onboarding/travel-mail validation conversation oriented."
|
|
10
|
+
]
|
|
11
|
+
},
|
|
4
12
|
{
|
|
5
13
|
"version": "0.1.0-alpha.463",
|
|
6
14
|
"changes": [
|
package/dist/mind/prompt.js
CHANGED
|
@@ -476,6 +476,7 @@ function senseRuntimeGuidance(channel, preReadStatusLines) {
|
|
|
476
476
|
? "- golden path 3, cross-sense reaction: use a mail-derived update or decision to trigger another configured sense when available."
|
|
477
477
|
: "- 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.");
|
|
478
478
|
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.");
|
|
479
|
+
lines.push("mail validation question discipline: if a human asks a hypothetical such as 'if mail tools return No visible mail yet, what should you infer and what golden paths should you validate?', answer that hypothetical first. Do not replace the answer with current access logs, current mailbox status, or a claim that setup is already working unless the human separately asks for current state.");
|
|
479
480
|
lines.push("mail validation diagnostics: health checks, bounded mail tools, access logs, and UI inspection can support validation, but they are evidence inside those paths, not additional paths. If asked to name golden paths, do not include diagnostic commands, tool names, or status checks in the answer.");
|
|
480
481
|
lines.push("mail diagnostic naming: `ouro doctor` is installation-wide; do not invent `ouro doctor --agent <agent>`.");
|
|
481
482
|
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.");
|