memhouse 0.11.0 → 0.11.1

package/README.md

@@ -237,6 +237,27 @@ an old house cannot be corrupted by a new shipper. `memhouse migrate-rooms` rebu
 copy, atomic swap, and the old room kept as `<room>_pre_epoch` for you to drop. The house
 records the move in `house_events`, and `memhouse doctor` reads it back.
 
+## Upgrading
+
+`memhouse update` upgrades the code, restarts the daemons, and — from 0.10.0 onward —
+detects a schema migration the house needs and prompts to run it.
+
+**One exception: upgrading from 0.9.x.** That release predates migrations, and `update`
+runs the *old* version's code (it replaces itself mid-run), so it cannot prompt. After
+the upgrade the first ship refuses (nothing is lost) and tells you the one command to
+run by hand:
+
+```bash
+memhouse update      # installs the new version, refuses to ship the old-schema house
+memhouse migrate     # the one-time rebuild it named — copy + atomic swap, nothing deleted
+memhouse doctor      # every line a check mark
+```
+
+If other machines ship into the same house as the same member, upgrade them too — a
+pre-0.10 shipper still deletes-before-reinsert; `memhouse doctor` flags any that are
+behind, and prints the `REVOKE ALTER DELETE, ALTER UPDATE` fallback that stops them
+destructively until you can.
+
 ## Troubleshooting
 
 ### An editor reads zero sessions

package/bin/memhouse.js

@@ -1607,7 +1607,7 @@ async function cmdDoctor() {
       } else {
         keysCorrect = wrongKeys.length === 0;
         add(keysCorrect, `sorting keys${keysCorrect ? ` carry origin and epoch correctly (${checked}/${ROOM_TYPES.length} rooms)` : `: wrong on ${wrongKeys.join(', ')}`}`,
-          'those rooms predate the epoch key, so the shipper refuses to write into them.\n     rebuild them (nothing is deleted): memhouse migrate-rooms');
+          'those rooms predate the epoch key, so the shipper refuses to write into them.\n     rebuild them (nothing is deleted): memhouse migrate');
       }
     } catch (e) { add(false, 'sorting keys', e.message); }
     // What the house says about ITSELF — its schema generation and whether a rebuild was

package/memhouse/shipper/ship.js

@@ -387,13 +387,15 @@ async function assertRoomKeys(client, rooms) {
   }
   if (wrong.length) {
     throw new Error(
-      'these rooms have the wrong sorting key, so a ship pass would corrupt them:\n'
+      'this house needs a one-time migration before it can be shipped to. Run:\n'
+      + '\n    memhouse migrate\n'
+      + '\n  (an upgrade from a pre-0.10 memhouse cannot prompt for this itself — the old\n'
+      + '  `update` command predates migrations, so run the line above once, by hand.)\n'
+      + '\n  Why: these rooms have the wrong sorting key, so a ship pass would corrupt them:\n'
       + wrong.map((s) => `    ${s}`).join('\n')
-      + '\n  ORDER BY cannot be altered in place — the rooms have to be rebuilt:'
-      + '\n    memhouse migrate-rooms'
-      + '\n  It copies each room into one with the current key, swaps them atomically, and'
-      + '\n  keeps the old one as <room>_pre_epoch for you to drop. Nothing is deleted.'
-      + '\n  A house with no imported rows can also just be re-shipped from scratch.');
+      + '\n  ORDER BY cannot be altered in place, so migrate copies each room into one with\n'
+      + '  the current key, swaps them atomically, and keeps the old one as <room>_pre_epoch\n'
+      + '  for you to drop. Nothing is deleted.');
   }
 }
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "memhouse",
-  "version": "0.11.0",
+  "version": "0.11.1",
   "description": "memhouse — agent conversation memory across 17 editors: parse-on-client shippers, a typed ClickHouse store with one set of rooms per member, kernel-agency install, and the agentlytics dashboard",
   "main": "bin/memhouse.js",
   "bin": {