palmier 0.6.3 → 0.6.5

package/README.md

@@ -113,36 +113,6 @@ The daemon automatically recovers existing tasks by reinstalling their system ti
 
 Agents are re-detected on every daemon start. Run `palmier restart` after installing or removing a CLI.
 
-### Verifying the Service
-
-After `palmier init`, verify the host is running:
-
-**Linux:**
-
-```bash
-# Check service status
-systemctl --user status palmier.service
-
-# View recent logs
-journalctl --user -u palmier.service -n 50 --no-pager
-
-# Follow logs in real time
-journalctl --user -u palmier.service -f
-```
-
-**Windows (PowerShell):**
-
-```powershell
-# Check if the daemon is running
-Get-Process -Name node -ErrorAction SilentlyContinue | Where-Object { $_.CommandLine -like '*palmier*serve*' }
-```
-
-**Restarting the daemon (both platforms):**
-
-```bash
-palmier restart
-```
-
 ## CLI Reference
 
 | Command | Description |

package/dist/commands/plan-generation.md

@@ -14,8 +14,8 @@ task_name: <concise label, 3-6 words>
 
 - Write a numbered sequence of concrete, actionable steps.
 - If the task produces formatted output (report, email, summary, etc.), specify the structure, sections, and tone.
-- When a step requires user input, simply state what information is needed from the user. Do not specify how to obtain it — the agent has its own tool for requesting user input.
-- Relative times in the task description (e.g., "today", "yesterday", "last week") refer to execution time, not plan generation time. Keep them as-is in the plan — do not convert them to specific dates.
+- When a step requires user input, simply state what information is needed from the user. Do **not** specify how to obtain it — the agent has its own tool for requesting user input.
+- Preserve relative time expressions (e.g., "today", "yesterday", "last week") exactly as written — do **not** resolve them to specific dates. The plan may be executed on a different day than it was generated.
 
 ## Task Description
 

package/dist/commands/run.js

@@ -342,7 +342,12 @@ async function runCommandTriggeredMode(ctx) {
             invocationsFailed++;
         });
     });
-    child.stderr?.on("data", (d) => process.stderr.write(d));
+    let stderrBuf = "";
+    child.stderr?.on("data", (d) => {
+        const chunk = d.toString();
+        stderrBuf += chunk;
+        process.stderr.write(d);
+    });
     // Wait for command to exit
     const exitCode = await new Promise((resolve) => {
         child.on("close", (code) => {
@@ -352,6 +357,7 @@ async function runCommandTriggeredMode(ctx) {
         });
         child.on("error", (err) => {
             console.error(`[command-triggered] Command error:`, err);
+            stderrBuf += err.message;
             commandExited = true;
             rl.close();
             resolve(1);
@@ -365,6 +371,17 @@ async function runCommandTriggeredMode(ctx) {
         });
     }
     const endTime = Date.now();
+    if (exitCode !== 0) {
+        const errorDetail = stderrBuf.trim() || `Command exited with code ${exitCode}`;
+        appendRunMessage(ctx.taskDir, ctx.runId, {
+            role: "status",
+            time: endTime,
+            content: errorDetail,
+            type: "error",
+        });
+        await publishHostEvent(ctx.nc, ctx.config.hostId, ctx.taskId, { event_type: "result-updated", run_id: ctx.runId });
+        return { outcome: "failed", endTime };
+    }
     return { outcome: "finished", endTime };
 }
 async function publishTaskEvent(nc, config, taskDir, taskId, eventType, taskName, runId) {