@dmsdc-ai/aigentry-telepty 0.5.0 → 0.5.1

package/CHANGELOG.md

@@ -4,6 +4,25 @@ All notable changes to `@dmsdc-ai/aigentry-telepty` are documented here.
 
 ## [Unreleased]
 
+## [0.5.1] - 2026-05-30
+
+### Fixed — daemon never started (CRITICAL, regresses 0.5.0)
+
+- **The daemon failed to start for all users on 0.5.0.** `daemon.js` guarded
+  `app.listen()` behind `require.main === module` (added in 0.5.0 for test
+  isolation so `require('./daemon.js')` is side-effect-free). But the production
+  CLI launches the daemon via `require('./daemon.js')` (`telepty daemon`, and the
+  auto-start spawns `node cli.js daemon`), so `require.main` is always `cli.js` —
+  `app.listen` never ran, the process exited 0 right after `[PERSIST] Restored
+  session … (awaiting reconnect)`, and every CLI reported `Daemon restart failed
+  after 3 attempts` / `fetch failed`. **Fix:** `cli.js` sets
+  `AIGENTRY_TELEPTY_DAEMON_MAIN=1` before requiring `daemon.js`; the guard is now
+  `require.main === module || process.env.AIGENTRY_TELEPTY_DAEMON_MAIN === '1'`.
+  Tests that `require()` daemon.js without the env stay side-effect-free. (telepty#15)
+- Follow-up (tracked): a daemon-launch integration smoke test — assert the HTTP
+  endpoint responds when the daemon is launched via the real CLI path. The unit-test
+  guard masked this regression; an integration test would have caught it.
+
 ## [0.5.0] - 2026-05-30
 
 ### Changed — Surface-ownership boundary (ADR 2026-05-30)

package/cli.js

@@ -966,6 +966,10 @@ async function main() {
 
   if (cmd === 'daemon') {
     console.log('Starting telepty daemon...');
+    // daemon.js binds the port only when launched as the daemon. The CLI reaches
+    // it via require() (not as require.main), so signal intent explicitly — tests
+    // that `require('./daemon.js')` without this env stay side-effect-free. (#15 / 0.5.0 daemon-never-listened regression)
+    process.env.AIGENTRY_TELEPTY_DAEMON_MAIN = '1';
     require('./daemon.js');
     return;
   }

package/daemon.js

@@ -3017,11 +3017,13 @@ app.patch('/api/threads/:id', (req, res) => {
   res.json({ success: true, thread_id: thread.id, status: thread.status });
 });
 
-// Bind the port only under the require.main guard — a test can `require('./daemon.js')` to
-// reach the exported decision functions without starting the daemon. `server` stays undefined
-// when required, so the WS upgrade/error handlers below attach only when run as the daemon.
+// Bind the port when launched as the daemon. A test can `require('./daemon.js')` to reach the
+// exported decision functions WITHOUT starting the daemon — it just must not set the env below.
+// The production CLI reaches daemon.js via require() (cli.js `cmd==='daemon'`), so require.main is
+// cli.js, never this module — hence the explicit AIGENTRY_TELEPTY_DAEMON_MAIN signal. Guarding on
+// require.main ALONE (0.5.0 regression) meant app.listen never ran in production → daemon exited 0.
 let server;
-if (require.main === module) {
+if (require.main === module || process.env.AIGENTRY_TELEPTY_DAEMON_MAIN === '1') {
   server = app.listen(PORT, HOST, () => {
     console.log(`🚀 aigentry-telepty daemon listening on http://${HOST}:${PORT}`);
     runStartupBootstrapRestore();

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@dmsdc-ai/aigentry-telepty",
-  "version": "0.5.0",
+  "version": "0.5.1",
   "main": "daemon.js",
   "bin": {
     "aigentry-telepty": "install.js",