@ouro.bot/cli 0.1.0-alpha.266 → 0.1.0-alpha.267
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 +6 -0
- package/dist/heart/daemon/daemon.js +2 -0
- package/dist/mind/prompt.js +13 -0
- package/package.json +1 -1
package/changelog.json
CHANGED
|
@@ -1,6 +1,12 @@
|
|
|
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.267",
|
|
6
|
+
"changes": [
|
|
7
|
+
"fix(prompt): teach agents that they do NOT 'just remember' things between sessions. Observed failure mode: slugger spent a recall scan searching diary/journal for a `travel/` folder that was right at the bundle root, then concluded 'i should know my own folder structure next time' and refused to persist the discovery because 'that's just me knowing my own home.' That is impossible — next session is a blank slate. The agent conflated in-session realizations with persistent knowledge. Three prompt changes fix this: (1) bodyMapSection now explicitly states that standard folders are a floor, bundles MAY have custom top-level folders created by the friend over time, and the agent should `list_directory` the bundle root BEFORE reaching for `recall` when something might be in a custom location. (2) memoryJudgementSection opens with an always-on reminder that the agent does not 'just remember' anything between sessions — every session carries only (a) the prompt, (b) what's on disk, (c) what tools observe this turn — and that thoughts like 'i should know this next time' or 'i'll look there first in the future' are CUES to write a concrete diary/friend-note RIGHT NOW. Future me cannot inherit resolutions, only files. (3) memoryJudgementSection's diary-routing rules now explicitly call out bundle-layout discoveries as a thing worth persisting (e.g. to a `bundle-layout.md` diary note). Includes 3 new tests locking the directives into place so future prompt edits cannot silently drop them."
|
|
8
|
+
]
|
|
9
|
+
},
|
|
4
10
|
{
|
|
5
11
|
"version": "0.1.0-alpha.266",
|
|
6
12
|
"changes": [
|
|
@@ -748,10 +748,12 @@ class OuroDaemon {
|
|
|
748
748
|
});
|
|
749
749
|
this.server = null;
|
|
750
750
|
}
|
|
751
|
+
/* v8 ignore start -- outlookServer stop: only reachable when the outlook HTTP server successfully bound to port 6876 during start(). Coverage fluctuates locally because a running production daemon holds the port and tests get EADDRINUSE, leaving outlookServer null. In CI the port is free and this block runs. Not worth fighting port contention to cover two trivial lines. @preserve */
|
|
751
752
|
if (this.outlookServer) {
|
|
752
753
|
await this.outlookServer.stop();
|
|
753
754
|
this.outlookServer = null;
|
|
754
755
|
}
|
|
756
|
+
/* v8 ignore stop */
|
|
755
757
|
if (fs.existsSync(this.socketPath)) {
|
|
756
758
|
fs.unlinkSync(this.socketPath);
|
|
757
759
|
}
|
package/dist/mind/prompt.js
CHANGED
|
@@ -180,6 +180,16 @@ my home is fully mine — who i am, everything i know, everything i've built:
|
|
|
180
180
|
tasks/ what i'm working on.
|
|
181
181
|
skills/ capabilities i've picked up beyond my core tools.
|
|
182
182
|
|
|
183
|
+
these are the standard folders every bundle has. my home MAY also contain
|
|
184
|
+
custom top-level folders that i or my friend created over time (trip plans,
|
|
185
|
+
domain-specific notebooks, reference material, project scratch, etc.). i do
|
|
186
|
+
NOT automatically know about them — this prompt only lists the standard set.
|
|
187
|
+
if a friend mentions "the file we have for X" or implies a location i don't
|
|
188
|
+
recognize, the answer is almost never buried in diary/journal. it's almost
|
|
189
|
+
always a custom folder at the root of my home. \`list_directory\` the root
|
|
190
|
+
of my home BEFORE reaching for \`recall\` — my own bundle layout is cheap
|
|
191
|
+
to observe and i should trust what i see, not what i think i know.
|
|
192
|
+
|
|
183
193
|
my home is mine to explore and evolve. i can read anything here,
|
|
184
194
|
change anything here. this is where i grow.
|
|
185
195
|
|
|
@@ -470,6 +480,8 @@ function toolContractsSection(options) {
|
|
|
470
480
|
function memoryJudgementSection() {
|
|
471
481
|
return `## memory judgement
|
|
472
482
|
|
|
483
|
+
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.
|
|
484
|
+
|
|
473
485
|
save a friend note when i learn something about a specific person that should change how i work with them again.
|
|
474
486
|
- preferences
|
|
475
487
|
- workflow expectations
|
|
@@ -482,6 +494,7 @@ write to diary when i learn something durable about the system, codebase, workfl
|
|
|
482
494
|
- review lessons
|
|
483
495
|
- continuity patterns
|
|
484
496
|
- coding workflow truths
|
|
497
|
+
- 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.
|
|
485
498
|
|
|
486
499
|
keep it ephemeral when it is only useful for the current turn or current local execution state.
|
|
487
500
|
- temporary branch names unless they matter beyond the task
|