@ouro.bot/cli 0.1.0-alpha.267 → 0.1.0-alpha.269

package/changelog.json

@@ -1,6 +1,18 @@
 {
   "_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.269",
+      "changes": [
+        "fix(prompt): revert alpha.267 over-engineering and correct the two targeted additions. The existing contextSection already contained the 'save to disk or lose it' teaching ('my conversation memory is ephemeral -- it resets between sessions. anything i learn about my friend, i save with save_friend_note so future me remembers.'), and toolContractsSection already told agents to call save_friend_note/diary_write before responding. alpha.267 added a third block in memoryJudgementSection about 'not just remembering between sessions' which was redundant and misplaced (memoryJudgementSection sits under 'my tools & capabilities' alongside tool routing heuristics, not nature-of-self content). That block is reverted. What alpha.267 got right and this PR keeps: (a) bodyMapSection guidance that standard folders are a floor, not a ceiling — bundles can have custom top-level folders (slugger's travel/ was the motivating example) — with a nudge to try the file-listing tool on the bundle root BEFORE falling back to recall, and (b) a diary-routing bullet that flags bundle-layout discoveries as worth persisting. Both had errors corrected here: alpha.267 told agents to use `list_directory` but the actual tool is `glob` (with a pattern like `*/`), and it said 'write a diary note like bundle-layout.md' but diary/ is a jsonl fact store queried via recall, not a directory of .md files — the corrected bullet says 'save the fact with diary_write'."
+      ]
+    },
+    {
+      "version": "0.1.0-alpha.268",
+      "changes": [
+        "fix(identity): `loadAgentConfig` now preserves the `sync` block from agent.json. The hand-rolled object literal that constructs the typed `AgentConfig` was missing `sync` from its field list, so `agentConfig.sync` was always `undefined`, `getSyncConfig()` always returned `enabled: false`, and the entire sync code path (`preTurnPull` / `postTurnPush` in `pipeline.ts`) was dead from the moment the field was added to the type. The bug hid for weeks because `ouro status` reads `agent.json` directly via `listBundleSyncRows`, not through `loadAgentConfig` — so the per-agent Git Sync display correctly showed `enabled origin → ...` while sync did literally nothing. Slugger accumulated 5+ days of dirty files and zero `sync: post-turn update` commits before this surfaced. Also adds 3 regression tests asserting the sync block round-trips through `loadAgentConfig` (full block, partial block, missing block). The first two would have caught the original bug; without them future field additions to `AgentConfig` could repeat the pattern."
+      ]
+    },
     {
       "version": "0.1.0-alpha.267",
       "changes": [

package/dist/heart/identity.js

@@ -416,6 +416,14 @@ function loadAgentConfig() {
         mcpServers: parsed.mcpServers,
         phrases: parsed.phrases,
         vault: parsed.vault,
+        // The sync block was missing from this hand-rolled object literal since
+        // it was added to AgentConfig. Result: `getSyncConfig()` always read
+        // `agentConfig.sync?.enabled ?? false` and always saw undefined, so the
+        // entire sync code path (preTurnPull / postTurnPush in pipeline.ts) was
+        // dead. The `ouro status` per-agent Git Sync display kept reporting
+        // "enabled" because it reads agent.json directly via `listBundleSyncRows`,
+        // not through loadAgentConfig — so the bug hid in plain sight for weeks.
+        sync: parsed.sync,
     };
     (0, runtime_1.emitNervesEvent)({
         event: "identity.resolve",

package/dist/mind/prompt.js

@@ -186,9 +186,10 @@ domain-specific notebooks, reference material, project scratch, etc.). i do
 NOT automatically know about them — this prompt only lists the standard set.
 if a friend mentions "the file we have for X" or implies a location i don't
 recognize, the answer is almost never buried in diary/journal. it's almost
-always a custom folder at the root of my home. \`list_directory\` the root
-of my home BEFORE reaching for \`recall\` — my own bundle layout is cheap
-to observe and i should trust what i see, not what i think i know.
+always a custom folder at the root of my home. use \`glob\` with a pattern
+like \`*/\` against the root of my home BEFORE reaching for \`recall\` — my
+own bundle layout is cheap to observe and i should trust what i see, not
+what i think i know.
 
 my home is mine to explore and evolve. i can read anything here,
 change anything here. this is where i grow.
@@ -480,8 +481,6 @@ function toolContractsSection(options) {
 function memoryJudgementSection() {
     return `## memory judgement
 
-i do not "just remember" anything between sessions -- not conversations, not facts about my friend, not the layout of my own bundle, not "lessons learned" in the current turn. next session i will be a blank slate carrying only (a) this prompt, (b) what's written to disk, (c) what i observe via tools this turn. when i catch myself thinking "i should know this next time" or "i'll look there first in the future" or "i won't make that mistake again", that is a CUE to write something concrete to disk RIGHT NOW -- a diary entry, a friend note, a pointer file future me will actually read. a resolution to "be more careful next time" changes nothing. future me cannot inherit resolutions, only files.
-
 save a friend note when i learn something about a specific person that should change how i work with them again.
 - preferences
 - workflow expectations
@@ -494,7 +493,7 @@ write to diary when i learn something durable about the system, codebase, workfl
 - review lessons
 - continuity patterns
 - coding workflow truths
-- the shape of my own bundle -- custom folders, where specific kinds of notes live, any layout that differs from the standard home map. if i just discovered that "X lives in folder Y" and i'd be likely to re-search for it next session, write a diary note like "bundle-layout.md" so future me can recall it instead of re-deriving it.
+- facts about my own bundle layout -- custom folders, where specific kinds of notes live, anything that differs from the standard home map. if i just discovered that "X lives in folder Y" and i'd be likely to re-search for it later, save the fact with diary_write so recall can surface it later instead of re-deriving it.
 
 keep it ephemeral when it is only useful for the current turn or current local execution state.
 - temporary branch names unless they matter beyond the task

package/package.json

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