@hasna/loops 0.2.0 → 0.3.1

package/dist/types.d.ts

@@ -58,8 +58,8 @@ export interface WorkflowTarget {
 export type ExecutableTarget = CommandTarget | AgentTarget;
 export type LoopTarget = ExecutableTarget | WorkflowTarget;
 export type WorkflowStatus = "active" | "archived";
-export type WorkflowRunStatus = "running" | "succeeded" | "failed" | "timed_out";
-export type WorkflowStepRunStatus = "pending" | "running" | "succeeded" | "failed" | "timed_out" | "skipped";
+export type WorkflowRunStatus = "running" | "succeeded" | "failed" | "timed_out" | "cancelled";
+export type WorkflowStepRunStatus = "pending" | "running" | "succeeded" | "failed" | "timed_out" | "skipped" | "cancelled";
 export interface WorkflowStep {
     id: string;
     name?: string;
@@ -111,6 +111,7 @@ export interface WorkflowStepRun {
     startedAt?: string;
     finishedAt?: string;
     exitCode?: number;
+    pid?: number;
     durationMs?: number;
     stdout?: string;
     stderr?: string;

package/docs/USAGE.md

@@ -95,7 +95,8 @@ Create a workflow JSON file:
       "id": "status",
       "target": {
         "type": "command",
-        "command": "git status --short",
+        "command": "git",
+        "args": ["status", "--short"],
         "cwd": "/path/to/repo"
       }
     },
@@ -117,15 +118,32 @@ Create a workflow JSON file:
 Save, run, inspect, and schedule it:
 
 ```bash
+loops workflows validate repo-morning.json
+loops workflows validate repo-morning.json --preflight
 loops workflows create repo-morning.json
 loops workflows run repo-morning --show-output
 loops workflows runs repo-morning
+loops workflows inspect <workflow-run-id>
 loops workflows events <workflow-run-id>
+loops workflows cancel <workflow-run-id> --reason "no longer needed"
+loops workflows recover <workflow-run-id>
 loops create workflow repo-morning-loop --workflow repo-morning --cron "0 8 * * *"
 ```
 
 Workflow specs are stored separately from loops. A loop can schedule a workflow, but workflow runs and step runs have their own durable rows and events. Steps run in dependency order and a scheduled workflow run is idempotent per loop slot.
 
+For command steps, `command` is the executable when `shell` is not true. Put flags in `args`:
+
+```json
+{ "type": "command", "command": "git", "args": ["status", "--short"] }
+```
+
+Use `shell: true` only when you intentionally want shell parsing:
+
+```json
+{ "type": "command", "command": "git status --short", "shell": true }
+```
+
 ## Manage
 
 ```bash
@@ -148,6 +166,7 @@ loops daemon start
 loops daemon status
 loops daemon logs
 loops daemon stop
+loops doctor
 ```
 
 Run in the foreground for supervised environments:
@@ -160,9 +179,10 @@ Install startup integration:
 
 ```bash
 loops daemon install
+loops daemon install --enable
 ```
 
-On Linux this writes a user systemd service. On macOS it writes a LaunchAgent plist. The command prints the exact enable/load commands to run.
+On Linux this writes a user systemd service. On macOS it writes a LaunchAgent plist. The command prints the exact enable/load commands to run. `--enable` runs the user-service enable/start command when supported.
 
 ## Scheduling Contract
 
@@ -183,10 +203,11 @@ On Linux this writes a user systemd service. On macOS it writes a LaunchAgent pl
 The adapters intentionally use provider command surfaces instead of pretending every agent has one SDK:
 
 - Claude uses `claude -p --output-format json` and safe-mode/local setting sources by default.
-- Codewith uses `codewith exec --json --ephemeral --ask-for-approval never`.
+- Codewith uses `codewith --ask-for-approval never exec --json --ephemeral --skip-git-repo-check`.
 - AI Copilot and OpenCode use `run --format json --pure`.
 - Cursor is CLI-first for now via `cursor-agent -p`; treat output as less stable until a stronger public SDK contract is selected.
 - Codex uses `codex exec --json --ephemeral --ask-for-approval never`.
-- When `--account` or a step `account` is set, OpenLoops resolves `accounts env <profile> --tool <tool>` before spawning the target, strips inherited tool home/API-key variables, and applies the selected profile only to that process.
+- When `--account` or a step `account` is set, OpenLoops resolves `accounts env <profile> --tool <tool>` before spawning the target, strips inherited tool home/API-key variables, and applies the selected profile only to that process. Missing account profiles fail before the provider binary receives the prompt.
+- Daemon and scheduled runs prepend common user executable directories such as `~/.local/bin` and `~/.bun/bin` before resolving provider CLIs.
 
 For production loops that can mutate repos, prefer disposable worktrees and explicit prompts that name allowed write scope.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@hasna/loops",
-  "version": "0.2.0",
+  "version": "0.3.1",
   "description": "Persistent local loop and workflow runner for deterministic commands and headless AI coding agents",
   "type": "module",
   "main": "dist/index.js",