@geohar/un-bien 0.7.0

package/dist/daemon/id.d.ts

@@ -0,0 +1,24 @@
+/**
+ * Stable 8-character hex id for a daemon, derived from the cwd it manages.
+ *
+ * Derivation: `sha256(realpath(cwd))` truncated to 8 hex chars (32 bits ≈
+ * 4 billion). Collision risk is negligible at fleet sizes a single user
+ * will ever have (<1000 daemons), and 8 hex characters are short enough
+ * to type on the CLI (`/unbien send a1b2c3d4 "..."`).
+ *
+ * Same scheme as `roomIdForCwd` in `src/rooms.ts` — but we use hex
+ * instead of base64url so the id has no `_`/`-` (cleaner double-click
+ * selection in terminals).
+ *
+ * Symlinks resolve to a single canonical id via `realpath`, so
+ * `/Users/x/Movies` and `/Users/x/link-to-Movies` map to the same daemon.
+ * Falls back to the raw path when realpath fails (cwd doesn't exist —
+ * shouldn't happen in production but covers test sandboxes).
+ *
+ * plan/41 audit (2026-06-08): this stays **per-cwd** (no name axis). The
+ * multiagent-per-folder model (plan/38/41) applies to the App↔Pi room and the
+ * mesh address; a *supervisor daemon* is **one per cwd** by design — the
+ * registry keys exactly one entry per cwd (`registry.ts`), so a daemon id never
+ * needs the name to disambiguate. Decision: leave `daemonIdForCwd` cwd-only.
+ */
+export declare function daemonIdForCwd(cwd: string): string;

package/dist/daemon/id.js

@@ -0,0 +1,36 @@
+import { createHash } from "node:crypto";
+import { realpathSync } from "node:fs";
+/**
+ * Stable 8-character hex id for a daemon, derived from the cwd it manages.
+ *
+ * Derivation: `sha256(realpath(cwd))` truncated to 8 hex chars (32 bits ≈
+ * 4 billion). Collision risk is negligible at fleet sizes a single user
+ * will ever have (<1000 daemons), and 8 hex characters are short enough
+ * to type on the CLI (`/unbien send a1b2c3d4 "..."`).
+ *
+ * Same scheme as `roomIdForCwd` in `src/rooms.ts` — but we use hex
+ * instead of base64url so the id has no `_`/`-` (cleaner double-click
+ * selection in terminals).
+ *
+ * Symlinks resolve to a single canonical id via `realpath`, so
+ * `/Users/x/Movies` and `/Users/x/link-to-Movies` map to the same daemon.
+ * Falls back to the raw path when realpath fails (cwd doesn't exist —
+ * shouldn't happen in production but covers test sandboxes).
+ *
+ * plan/41 audit (2026-06-08): this stays **per-cwd** (no name axis). The
+ * multiagent-per-folder model (plan/38/41) applies to the App↔Pi room and the
+ * mesh address; a *supervisor daemon* is **one per cwd** by design — the
+ * registry keys exactly one entry per cwd (`registry.ts`), so a daemon id never
+ * needs the name to disambiguate. Decision: leave `daemonIdForCwd` cwd-only.
+ */
+export function daemonIdForCwd(cwd) {
+    let target;
+    try {
+        target = realpathSync(cwd);
+    }
+    catch {
+        target = cwd;
+    }
+    return createHash("sha256").update(target).digest("hex").slice(0, 8);
+}
+//# sourceMappingURL=id.js.map

package/dist/daemon/id.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"id.js","sourceRoot":"","sources":["../../src/daemon/id.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,UAAU,EAAE,MAAM,aAAa,CAAC;AACzC,OAAO,EAAE,YAAY,EAAE,MAAM,SAAS,CAAC;AAEvC;;;;;;;;;;;;;;;;;;;;;;GAsBG;AACH,MAAM,UAAU,cAAc,CAAC,GAAW;IACxC,IAAI,MAAc,CAAC;IACnB,IAAI,CAAC;QACH,MAAM,GAAG,YAAY,CAAC,GAAG,CAAC,CAAC;IAC7B,CAAC;IAAC,MAAM,CAAC;QACP,MAAM,GAAG,GAAG,CAAC;IACf,CAAC;IACD,OAAO,UAAU,CAAC,QAAQ,CAAC,CAAC,MAAM,CAAC,MAAM,CAAC,CAAC,MAAM,CAAC,KAAK,CAAC,CAAC,KAAK,CAAC,CAAC,EAAE,CAAC,CAAC,CAAC;AACvE,CAAC"}

package/dist/daemon/install.d.ts

@@ -0,0 +1,170 @@
+/**
+ * Generates and activates a system service for `pi-supervisord` so the
+ * daemon fleet survives reboots (plan/26 W3).
+ *
+ * Platform support:
+ *   - **macOS**: writes `~/Library/LaunchAgents/dev.unbien.supervisord.plist`
+ *     and runs `launchctl bootstrap gui/<uid> <plist>` (modern API) with a
+ *     fallback to `launchctl load` for older macOS.
+ *   - **Linux**: writes `~/.config/systemd/user/unbien-supervisord.service`
+ *     and runs `systemctl --user daemon-reload && systemctl --user enable
+ *     --now unbien-supervisord.service`.
+ *
+ * Uninstall reverses both. Idempotent — re-running install over an existing
+ * unit refreshes it (paths could have changed if user moved node_modules).
+ *
+ * **What does NOT happen here**: the actual `npm install -g un-bien` step.
+ * The user has to make the supervisor bin reachable on disk before install
+ * can wire up the service. The `findSupervisorScript` resolver detects
+ * common cases (npm global, pnpm global, local dev clone) and yields a
+ * clear error otherwise.
+ */
+export type SupervisorPlatform = "macos" | "linux" | "windows" | "unsupported";
+export declare function detectPlatform(): SupervisorPlatform;
+/**
+ * Absolute path to the supervisor's compiled entry. We resolve from
+ * `import.meta.url` (this file's location) since wherever the daemon
+ * module lives, `bin/supervisord.js` is a sibling of `daemon/` under
+ * `dist/`.
+ *
+ * After build: `dist/daemon/install.js` → `dist/bin/supervisord.js`.
+ * In dev (`tsx`): same path resolution still lands inside `src/`, which
+ * isn't directly runnable by `node` — dev install isn't expected.
+ */
+export declare function findSupervisorScript(): string;
+/**
+ * Absolute path to the extension's CLI entry (`dist/index.js`). This is
+ * the file we symlink to `~/.local/bin/unbien` so the user can run
+ * `un-bien <subcommand>` from any shell after installing the extension
+ * through Pi (`pi install npm:un-bien`).
+ *
+ * Same resolution strategy as `findSupervisorScript`: from
+ * `dist/daemon/install.js` → `dist/index.js`.
+ */
+export declare function findRemotePiScript(): string;
+export declare function findNodeBinary(): string;
+export declare function findTemplate(name: "systemd" | "launchd" | "taskscheduler" | "vbs-launcher"): string;
+export declare function systemdUnitPath(): string;
+export declare function launchdPlistPath(): string;
+export declare const LAUNCHD_LABEL = "dev.unbien.supervisord";
+/** systemd --user unit name (with `.service`) for the supervisor. */
+export declare const SYSTEMD_UNIT = "unbien-supervisord.service";
+/** Windows Task Scheduler task name (plan/40). */
+export declare const WINDOWS_TASK_NAME = "RemotePiSupervisor";
+/** Path of the rendered Task Scheduler XML (input to `schtasks /Create /XML`). */
+export declare function taskXmlPath(): string;
+/**
+ * Path of the rendered VBScript launcher the Task Scheduler action invokes
+ * via `wscript.exe` (plan/40, Windows). Launching node through this hidden
+ * wrapper is what keeps the supervisor from flashing a console window.
+ */
+export declare function vbsLauncherPath(): string;
+/**
+ * Combined stdout/stderr log for the Windows supervisor. The Task Scheduler
+ * launches it hidden via wscript, so without this redirect its output (and the
+ * forwarded daemon-child stderr) would vanish — mirrors launchd/systemd, which
+ * already log to `~/.pi/un-bien/supervisord.log`.
+ */
+export declare function supervisordLogPath(): string;
+export interface RenderVars {
+    node: string;
+    supervisor: string;
+    home: string;
+    user: string;
+    /** PATH inherited so `pi --mode rpc` resolves the same way it does
+     *  interactively. We snapshot `process.env.PATH` at install time. */
+    path: string;
+    /** Windows only: absolute path of the VBScript launcher the Task Scheduler
+     *  action runs via `wscript.exe`. Empty on POSIX (templates ignore `{VBS}`). */
+    vbs: string;
+    /** Windows only: combined stdout/stderr log the hidden supervisor appends to.
+     *  Empty on POSIX (templates ignore `{LOG}`). */
+    logPath: string;
+}
+export declare function defaultRenderVars(): RenderVars;
+/** Replace `{NODE}` / `{SUPERVISOR}` / `{USER}` / `{HOME}` / `{PATH}` / `{VBS}` / `{LOG}`. */
+export declare function renderTemplate(template: string, vars: RenderVars): string;
+export interface InstallResult {
+    platform: SupervisorPlatform;
+    unitPath: string;
+    /** Lines describing each step taken — surfaced to the user via notify. */
+    log: string[];
+}
+/**
+ * Writes the unit/plist, runs the platform's activation command. Throws
+ * on unsupported OS or when the supervisor script isn't found.
+ *
+ * Idempotent: re-running re-writes the unit (paths could have changed)
+ * and re-activates via the platform tool's idempotent flag.
+ */
+export declare function installService(vars?: RenderVars): InstallResult;
+export interface UninstallResult {
+    platform: SupervisorPlatform;
+    unitPath: string;
+    removed: boolean;
+    log: string[];
+}
+export declare function uninstallService(): UninstallResult;
+/**
+ * Build the batch script run elevated. Each command line redirects its output
+ * to `logFile` so the (separate, elevated) process's output can be read back by
+ * the parent. Control-flow lines (`if`/`exit`/`rem`/`@`) run bare — redirecting
+ * them would swallow the exit code. Pure + exported for tests.
+ */
+export declare function buildElevatedCmd(lines: string[], logFile: string): string;
+export interface LinkBinariesResult {
+    /** `~/.local/bin/`. The two symlinks land here. */
+    binDir: string;
+    /** Paths of the two symlinks we created/refreshed. */
+    links: Array<{
+        name: string;
+        path: string;
+        target: string;
+    }>;
+    /** True when `binDir` is already on `$PATH`. False → caller surfaces the
+     *  "add this line to your shell rc" hint to the user. */
+    onPath: boolean;
+    log: string[];
+}
+export declare function userLocalBinDir(home?: string): string;
+/**
+ * Check whether `dir` is on `process.env.PATH`. Tolerates trailing
+ * slashes and relative entries (which we treat as not matching — `~/.local/bin`
+ * is always absolute on our end).
+ */
+export declare function isOnPath(dir: string, envPath?: string): boolean;
+/**
+ * Create (or refresh) the `un-bien` + `pi-supervisord` symlinks in
+ * `~/.local/bin/`. Idempotent — replaces stale links pointing at old
+ * extension paths (Pi can reinstall the extension to a different hash dir
+ * on upgrades, so this MUST overwrite).
+ *
+ * Returns `onPath: false` when `~/.local/bin` isn't in the user's `$PATH`.
+ * The caller is responsible for surfacing the shell-rc instruction —
+ * we don't edit the user's shell config files automatically.
+ */
+export declare function linkCliBinaries(home?: string, paths?: {
+    remotePi?: string;
+    supervisord?: string;
+}, opts?: {
+    node?: string;
+    mutatePath?: boolean;
+}): LinkBinariesResult;
+/** A Windows `.cmd` shim that forwards all args to `node "<target>"`. Pure. */
+export declare function buildCmdShim(node: string, target: string): string;
+/**
+ * Remove the symlinks `linkCliBinaries` created. Idempotent — missing
+ * links are a no-op. Returns whether each link was actually present so
+ * the caller can render a useful summary. Targets (the extension files)
+ * are NOT touched here — they live outside this dir and belong to Pi.
+ */
+export interface UnlinkBinariesResult {
+    binDir: string;
+    removed: Array<{
+        name: string;
+        path: string;
+        existed: boolean;
+    }>;
+    log: string[];
+}
+export declare function unlinkCliBinaries(home?: string): UnlinkBinariesResult;