memgineering 0.4.2 → 0.5.0

package/package.json

@@ -1,8 +1,8 @@
 {
   "name": "memgineering",
-  "version": "0.4.2",
+  "version": "0.5.0",
   "private": false,
-  "description": "One memory for the AI you connect. Recall, remember, and revise a brain your agents share — stored in your own folder.",
+  "description": "One memory for the AI you connect. Recall, remember, and revise a brain your agents share \u2014 stored in your own folder.",
   "license": "Apache-2.0",
   "homepage": "https://memgineering.com",
   "repository": {

package/scripts/postinstall.mjs

@@ -1,16 +1,65 @@
 #!/usr/bin/env node
 /**
- * One line after install, and nothing else.
+ * The one thing an AGENT has to be told after a global install.
  *
- * Deliberately not `setup --silent`, the way the kordis CLI does it. Setup
- * here asks which tools to install into and whether the tool may update
- * itself — questions that belong to the person, not to a package manager
- * running unattended. Doing it from postinstall would answer them by
- * default and call that consent.
+ * This used to print `memgineering installed. Next: memgineering setup` and
+ * gate it on `process.stdout.isTTY`. Both were wrong, and a first-run test with
+ * Codex showed exactly how: the agent installed the package and then reported
+ * to its user "초기 설정 명령: memgineering setup" — handing a terminal command
+ * to a non-developer and stopping. The person is left holding an instruction
+ * they did not ask for and cannot act on, in a product whose entire premise is
+ * that their agent does this for them.
  *
- * Silent for local installs and for anything non-interactive: a dependency
- * being pulled into someone's project has no business printing instructions.
+ * The TTY gate made it worse. An agent running `npm i -g` has a PIPE, not a
+ * terminal, so the guidance was suppressed in precisely the case it exists for
+ * and printed only for the developer who least needed it.
+ *
+ * So: speak to the agent, and speak when the agent is listening. The global
+ * check stays — a dependency pulled into somebody's project still has no
+ * business printing instructions.
+ *
+ * Setup is NOT run from here. It asks which tools to install into and whether
+ * the tool may update itself, and answering those from a package manager
+ * running unattended would be inventing consent. The agent asks the one
+ * question that decides it, then runs setup itself — which is the same
+ * division of labour every other verb in this product uses.
+ *
+ * English, per the CLI-output rule: the agent re-renders it in whatever
+ * language its user speaks.
  */
-if (process.stdout.isTTY && process.env['npm_config_global'] === 'true') {
-  process.stdout.write('\nmemgineering installed. Next:  memgineering setup\n\n');
+if (process.env['npm_config_global'] === 'true') {
+  process.stdout.write(
+    [
+      '',
+      'memgineering is installed. It is NOT set up yet.',
+      '',
+      'TO THE AGENT READING THIS — finish it now, in this same turn. Do not',
+      'print these commands for your user and stop: they are yours to run.',
+      '',
+      'Ask them TWO short questions, in their language, then run setup yourself.',
+      '',
+      '  1. Where should the memory live?',
+      '       "Just on this machine, or synced to an account so every device',
+      '        and every tool you use sees the same brain?"',
+      '',
+      '       this machine  ->  no extra flag',
+      '       synced        ->  add  --login',
+      '',
+      '  2. Who picks the rest of the settings?',
+      '       "Shall I set it up, or would you rather choose on a screen?"',
+      '',
+      '       you do it     ->  memgineering setup --agent',
+      '       they choose   ->  memgineering setup --web',
+      '',
+      'So: `memgineering setup --agent --login`, or `--agent`, or `--web',
+      '--login`, or `--web`. Question 1 matters most — WITHOUT `--login`,',
+      'setup makes a folder on this machine and never mentions accounts, and',
+      'the user finds out later that their memory does not follow them.',
+      '',
+      '`--login` prints a short code: show it to them and they approve it in',
+      'the browser. Setup does not wait, and the next command collects the',
+      'token, so you keep going in the same turn.',
+      '',
+    ].join('\n'),
+  );
 }