@agfpd/iapeer 0.2.65 → 0.2.66

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@agfpd/iapeer",
-  "version": "0.2.65",
+  "version": "0.2.66",
   "description": "Foundation core for the iapeer multi-agent ecosystem: identity, registry, storage, codec.",
   "type": "module",
   "bin": {

package/src/supervisor/index.ts

@@ -66,7 +66,23 @@ export interface StartDaemonResult {
   detail?: string
 }
 
-const selfArgv = (): string[] => [process.execPath, fileURLToPath(import.meta.url)]
+/**
+ * Re-invoke THIS module as the detached daemon (spawn-flip Ф1 serving-wiring). From SOURCE (bun) the
+ * module is a real file on disk → run it directly (`bun <self> daemon …` → import.meta.main →
+ * runSupervisorCli). In a `bun build --compile` STANDALONE the module is EMBEDDED at a `/$bunfs`
+ * virtual path that is NOT on disk; a bare `<binary> <bunfs-path> daemon …` invocation mis-routes
+ * through the CLI (the path becomes an unknown verb → usage, daemon never comes up — and a hosted
+ * launch then silently falls back to tmux). Detect that (the resolved self path is absent on disk) and
+ * re-invoke the installed binary through its `supervisor` verb instead. The caller appends
+ * `daemon <session> <runtime> --run-dir <dir>`, so runSupervisorCli is reached either way.
+ */
+export function resolveDaemonSelfArgv(execPath: string, selfPath: string, selfOnDisk: boolean): string[] {
+  return selfOnDisk ? [execPath, selfPath] : [execPath, 'supervisor']
+}
+const selfArgv = (): string[] => {
+  const self = fileURLToPath(import.meta.url)
+  return resolveDaemonSelfArgv(process.execPath, self, existsSync(self))
+}
 
 /** Start a detached supervisor daemon and wait until its socket is live. Idempotent. */
 export function startSupervisorDaemon(opts: StartDaemonOptions): StartDaemonResult {

package/src/supervisor/selfargv.test.ts

@@ -0,0 +1,21 @@
+// Spawn-flip Ф1 serving-wiring — resolveDaemonSelfArgv picks the right re-invocation for the detached
+// supervisor daemon: a real on-disk module (bun/source) runs directly; an EMBEDDED module (a compiled
+// `bun build --compile` standalone, whose self path is NOT on disk) re-invokes the installed binary
+// through its `supervisor` verb. The bug this guards: a bare bunfs-path invocation mis-routes through
+// the CLI (unknown verb → usage), the daemon never comes up, and a hosted launch falls back to tmux.
+import { describe, expect, test } from 'bun:test'
+import { resolveDaemonSelfArgv } from './index.ts'
+
+describe('resolveDaemonSelfArgv', () => {
+  test('source (self on disk) → re-run the module directly with the runtime (bun)', () => {
+    expect(resolveDaemonSelfArgv('/opt/homebrew/bin/bun', '/Users/x/iapeer/src/supervisor/index.ts', true))
+      .toEqual(['/opt/homebrew/bin/bun', '/Users/x/iapeer/src/supervisor/index.ts'])
+  })
+
+  test('compiled standalone (self NOT on disk = embedded /$bunfs) → installed binary + `supervisor` verb', () => {
+    expect(resolveDaemonSelfArgv('/Users/x/.local/bin/iapeer', '/$bunfs/root/src/supervisor/index.ts', false))
+      .toEqual(['/Users/x/.local/bin/iapeer', 'supervisor'])
+    // The caller appends `daemon <session> <runtime> --run-dir <dir>` → `iapeer supervisor daemon …`,
+    // which the CLI routes to runSupervisorCli('daemon', …). NOT a bare bunfs-path (→ usage).
+  })
+})