create-booboo 0.3.0 → 0.4.0

package/dist/cli.js

@@ -3,7 +3,7 @@
 // src/cli.ts
 import { mkdirSync, writeFileSync, existsSync, readdirSync, readFileSync } from "fs";
 import path from "path";
-var BOOBOO_VERSION = "^0.4.0";
+var BOOBOO_VERSION = "^0.5.0";
 var VERSION = JSON.parse(readFileSync(new URL("../package.json", import.meta.url), "utf8")).version;
 var args = process.argv.slice(2);
 var flags = new Set(args.filter((a) => a.startsWith("--")));
@@ -180,11 +180,17 @@ your conventions evolve \u2014 it IS your system's constitution.
 ## MCP
 
 \`npm run mcp\` exposes \`booboo_stats \xB7 booboo_search \xB7 booboo_node \xB7 booboo_neighbors \xB7 booboo_path\`
-(+ \`booboo_boot \xB7 booboo_org\` with \`--org\`) so an AI client can query the brain. See the Booboo repo for client config.
+(+ \`booboo_boot \xB7 booboo_org\` with \`--org\`) so an AI client can query the brain, plus the LIVE
+memory verbs \`booboo_remember\` and \`booboo_report\` \u2014 durable writes that append to the journal
+beside the snapshot and are queryable the same session (pass \`--no-write\` for a read-only server).
+See the Booboo repo for client config.
 `;
 var gitignore = `node_modules/
 # the built snapshot can contain real/private data \u2014 don't commit it
 brain.json
+# the LIVE MEMORY journal \u2014 durable agent writes (remember/report). Private,
+# and NOT regenerated by build, so it's never deleted \u2014 just don't commit it.
+*.journal.jsonl
 # the vault is derived from the snapshot \u2014 regenerate, never commit
 vault/
 *.log
@@ -203,9 +209,10 @@ operating doctrine for this brain \u2014 the conventions match the setup.*
 1. **ORIENT** \u2014 never assume what the brain knows: boot as your agent (\`booboo_boot('<agent-id>')\` over MCP) for your identity, inherited rules and buckets; then \`booboo_search\`/\`booboo_neighbors\` for the facts you need. *Assumption is not recall.*
 2. **ACT** \u2014 the smallest correct change.
 3. **VERIFY against reality** \u2014 \`npm run build\` and read the \`quality\` line; open \`npm run view\` or \`npm run panel\` when the change is visual. Introspection is not verification.
-4. **RECORD** \u2014 write what you learned into your source data as a memory node.
+4. **RECORD** \u2014 write what you learned: call \`booboo_remember\` (a durable memory) and \`booboo_report\` (what you closed) over MCP. These are LIVE \u2014 they append to the journal beside the snapshot and are queryable the same session; no rebuild needed. Close every substantial task with a \`booboo_report\`.
 
 ## Writing memories (the conventions that keep the brain curated)
+- **Use \`booboo_remember\`** \u2014 pass \`agent\` (who it belongs to), \`text\` (the fact), and optionally \`kind\` / \`bucket\`. It writes to the durable journal (survives every rebuild) and is instantly searchable. \`booboo_report\` files what you closed; it lands on the panel's Reports timeline.
 - **One atomic fact per note**, written for the future reader. Never dump a transcript \u2014 the quality gate counts \`dump-suspects\` and they are a smell.
 - **Author your links**: put \`[[node-id]]\` (or \`[[exact label]]\`) refs in the note text where you KNOW the connection. \`wikilinks: true\` turns them into first-class \`authored\` edges that outrank any harvested relation.
 - **Corrections replace**: when a note corrects an earlier fact, remove or supersede the old one in the same act. A brain that only accumulates is not curated \u2014 stale truth next to live truth is worse than either.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "create-booboo",
-  "version": "0.3.0",
+  "version": "0.4.0",
   "description": "Scaffold a new Booboo brain — `npx create-booboo my-brain`. Zero deps.",
   "license": "MIT",
   "repository": {