rulemux 0.2.2 → 0.2.4

package/README.md

@@ -75,9 +75,14 @@ There is **no auto-update**. Upgrades are manual and handled by your package man
 (`go install …@latest`, Homebrew/Scoop/apt later on). This is a deliberate decision — see
 [design/requirements.md](docs/design/requirements.md) §五.
 
-**An upgrade keeps your hooks current.** A hook command can change between releases (0.2.0 added
-`--hook`), so after `npm i -g rulemux@latest` the npm `postinstall` step rewrites the SessionStart
-hooks rulemux itself had installed — and touches nothing else. For non-npm upgrades, run it yourself:
+**An upgrade keeps your hooks current — by itself, with no npm install scripts.** A hook command can
+change between releases (0.2.0 added `--hook`), so rulemux fixes its own stale hook the next time an
+agent runs it: the first `rulemux sync` after an upgrade rewrites rulemux's own SessionStart entry
+into the current format. Nothing else is touched — other tools' hooks and every other key stay as they
+were, and nothing is ever created. Because this lives in the binary, it works no matter how rulemux was
+installed and needs no `postinstall` allow-list from npm.
+
+You can also do it on demand:
 
 ```bash
 rulemux init --refresh   # rewrite rulemux's OWN hooks only: never installs, never creates files
@@ -224,7 +229,7 @@ shown the list of workspaces before anything is deleted.
 | `rulemux sync --all [--config <path>]` | Manually re-align every workspace recorded in the ledger (never reads cwd, never creates dirs, prunes ledger entries whose directory is gone). Mutually exclusive with `--hook` / `--agent` / `--workspace` |
 | `rulemux inject --agent <id> [--config <path>]` | Tier-2: print rules to stdout for hook injection |
 | `rulemux init --agent <id[,id...]> [--config <path>] [--workspace <dir>]` | Write a sample config and install the SessionStart hook |
-| `rulemux init --refresh [--agent <id[,id...]>] [--workspace <dir>]` | Refresh **only** the hooks rulemux already installed (npm `postinstall` calls this). Never adds a hook, never creates a file or directory, preserves every other entry and key in the host config |
+| `rulemux init --refresh [--agent <id[,id...]>] [--workspace <dir>]` | Refresh **only** the hooks rulemux already installed. This also happens by itself on the first sync after an upgrade; use this to force it. Never adds a hook, never creates a file or directory, preserves every other entry and key in the host config |
 | `rulemux doctor [--config <path>] [--workspace <dir>]` | Environment self-check |
 | `rulemux verify --agent <id> [--clean] [--workspace <dir>]` | Canary acceptance test |
 | `rulemux uninstall --agent <id[,id...]> \| --off \| --all [--yes]` | Remove hooks and delivered files |

package/README.zh-CN.md

@@ -67,9 +67,10 @@ npm i -g rulemux
 **没有自动更新**。升级手动、交给包管理器（`go install …@latest`，将来 Homebrew / Scoop / apt）。
 这是刻意决策，见 [`docs/design/requirements.md`](docs/design/requirements.md) §五。
 
-**升级会自动把你的钩子刷新到当前格式。** 钩子命令会随版本变化（0.2.0 起加了 `--hook`），所以
-`npm i -g rulemux@latest` 之后，npm 的 `postinstall` 会**只重写 rulemux 自己装过的那条** SessionStart
-钩子 —— 别的条目、别的键一个字节都不动。非 npm 方式升级的，自己跑一条即可：
+**升级后钩子会自己跟上当前格式——不依赖 npm 的安装脚本。** 钩子命令会随版本变化（0.2.0 起加了
+`--hook`），所以升级后**首次**有 Agent 调起 `rulemux sync` 时，它会**只重写 rulemux 自己装过的那条**
+SessionStart 钩子为当前格式 —— 别的条目、别的键一个字节都不动，也绝不创建任何文件。这段逻辑在二进制
+里，因此**任何安装方式都生效**，也不需要 npm 放行任何安装脚本。想立刻手动做一次：
 
 ```bash
 rulemux init --refresh   # 只刷新「我们自己装过的」钩子：不新增、不创建任何文件或目录
@@ -209,7 +210,7 @@ rulemux uninstall --agent codebuddy --yes    # 跳过交互确认
 | `rulemux sync --all [--config <path>]` | 手动把账本里记录过的所有工作区重新对齐（不读 cwd、绝不创建目录、顺手 GC 掉目录已不在的条目）。与 `--hook` / `--agent` / `--workspace` 互斥 |
 | `rulemux inject --agent <id> [--config <path>]` | Tier-2：把规则输出到 stdout 供钩子注入 |
 | `rulemux init --agent <id[,id...]> [--config <path>] [--workspace <dir>]` | 生成示例配置并安装 SessionStart 钩子 |
-| `rulemux init --refresh [--agent <id[,id...]>] [--workspace <dir>]` | **只刷新** rulemux 自己装过的钩子（npm `postinstall` 调用的就是它）：不新增、不创建任何文件或目录、文件里其它条目与其它键一律原样保留 |
+| `rulemux init --refresh [--agent <id[,id...]>] [--workspace <dir>]` | **只刷新** rulemux 自己装过的钩子（升级后首次 `sync` 会自动做一次，这条用于手动强制）：不新增、不创建任何文件或目录、文件里其它条目与其它键一律原样保留 |
 | `rulemux doctor [--config <path>] [--workspace <dir>]` | 环境自检 |
 | `rulemux verify --agent <id> [--clean] [--workspace <dir>]` | canary 验收 |
 | `rulemux uninstall --agent <id[,id...]> \| --off \| --all [--yes]` | 移除钩子与已投递文件 |

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "rulemux",
-  "version": "0.2.2",
+  "version": "0.2.4",
   "description": "One set of rules, delivered to every AI coding agent: copies the rule files you declare into each agent's native workspace rules directory, with the same effect and token cost as writing AGENTS.md by hand.",
   "license": "MIT",
   "repository": {
@@ -23,7 +23,6 @@
   ],
   "scripts": {
     "build:dist": "bash scripts/build-dist.sh",
-    "postinstall": "node bin/postinstall.js",
     "prepublishOnly": "npm run build:dist"
   },
   "engines": {

package/bin/postinstall.js

@@ -1,87 +0,0 @@
-#!/usr/bin/env node
-"use strict";
-
-// npm postinstall: bring rulemux's own SessionStart hooks up to date after a
-// global install/upgrade.
-//
-// Why: a hook command can change between releases (0.2.0 added `--hook`). Users
-// who upgraded but never re-ran `init` would silently keep the old behaviour,
-// so the upgrade itself refreshes what it previously wrote.
-//
-// Deliberate limits — this script must never surprise anyone:
-//   - global installs only: a project-local `npm i rulemux` must not touch the
-//     user's host config;
-//   - skipped under CI, sudo and --ignore-scripts: $HOME would point at the
-//     wrong user, or the run is not a real user's machine;
-//   - it never installs anything new: only hooks rulemux itself already wrote;
-//   - it never fails the install: every error path exits 0, silently.
-//
-// Non-npm installs (go install, a binary from GitHub Releases) have no
-// postinstall. Those users run `rulemux init --refresh` themselves, and
-// `rulemux doctor` reports hooks that are installed but outdated.
-
-const fs = require("fs");
-const path = require("path");
-const { spawnSync } = require("child_process");
-
-function platformKey() {
-  const plat = process.platform === "win32" ? "windows" : process.platform;
-  let arch = process.arch;
-  if (arch === "x64") arch = "amd64";
-  else if (arch === "ia32") arch = "386";
-  return `${plat}-${arch}`;
-}
-
-// Same resolution order as bin/rulemux.js: a bundled binary first, then a
-// `rulemux` already on PATH.
-function resolveBinary() {
-  const ext = process.platform === "win32" ? ".exe" : "";
-  const key = platformKey();
-  const candidates = [
-    path.join(__dirname, "..", "dist", `rulemux-${key}${ext}`),
-    path.join(__dirname, "..", "dist", `rulemux-${process.platform}-${process.arch}${ext}`),
-  ];
-  for (const c of candidates) {
-    if (fs.existsSync(c)) return c;
-  }
-  const which = process.platform === "win32" ? "where" : "which";
-  const r = spawnSync(which, ["rulemux"], { stdio: "ignore" });
-  return r.status === 0 ? "rulemux" : null;
-}
-
-function shouldRun() {
-  if (process.env.npm_config_global !== "true") return false;
-  if (process.env.npm_config_ignore_scripts === "true") return false;
-  if (process.env.CI) return false;
-  if (process.env.SUDO_USER) return false;
-  return true;
-}
-
-function main() {
-  if (!shouldRun()) return;
-
-  const bin = resolveBinary();
-  if (!bin) return;
-
-  const r = spawnSync(bin, ["init", "--refresh"], { encoding: "utf8" });
-  if (r.error || r.status !== 0 || !r.stdout) return;
-
-  // Stay quiet unless something actually changed: "refreshed:" marks a rewrite.
-  const changed = r.stdout
-    .split("\n")
-    .map((line) => line.trim())
-    .filter((line) => line.includes("refreshed:"));
-  if (changed.length === 0) return;
-
-  process.stdout.write(
-    "rulemux: upgraded the SessionStart hook(s) rulemux had already installed\n" +
-      changed.map((line) => "  " + line).join("\n") +
-      "\n"
-  );
-}
-
-try {
-  main();
-} catch (_) {
-  // Never let a hook refresh break `npm install`.
-}