@coworker-jp/aidr 0.1.4 → 0.1.6

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@coworker-jp/aidr",
-  "version": "0.1.4",
+  "version": "0.1.6",
   "description": "AIDR setup CLI - installs ai-scanner hooks for 19+ AI coding agents",
   "type": "module",
   "bin": {

package/src/cli.mjs

@@ -589,7 +589,7 @@ export async function run(argv) {
   program
     .name("aidr")
     .description("AIDR setup CLI — installs ai-scanner hooks for AI coding agents")
-    .version("0.1.4");
+    .version("0.1.5");
 
   program
     .command("install")

package/src/scheduled.mjs

@@ -252,11 +252,13 @@ exec ${binaryPath} scan endpoint-info
 }
 
 async function installCronDir({ binaryPath, dryRun, interval = 4 }) {
-  // /etc/cron.d entries run as the user named in the line. We embed the env
-  // file source via a small inline script. stdout + stderr are appended to
-  // the world-readable log so non-root users can read recent runs without
-  // sudo.
-  const entry = `0 */${interval} * * * root . ${SYSTEM_ENV_FILE} && ${binaryPath} scan endpoint-info >> ${SCHEDULED_LOG_FILE} 2>&1 # aidr-scheduled
+  // The aidr.env file is plain `KEY=VALUE` lines (no `export` prefix —
+  // systemd's EnvironmentFile= used by the sentinel service requires that
+  // form). Plain `. file` sets shell-local variables that don't propagate
+  // to the spawned ai-scanner process; `set -a` flips on auto-export so
+  // every assignment becomes an environment variable. Same pattern as the
+  // launchd wrapper on macOS.
+  const entry = `0 */${interval} * * * root set -a; . ${SYSTEM_ENV_FILE}; set +a; ${binaryPath} scan endpoint-info >> ${SCHEDULED_LOG_FILE} 2>&1
 `;
   if (dryRun) {
     console.log("[dry-run] Would create:", CRON_FILE);