@openduo/duoduo 0.2.10 → 0.2.12

package/bootstrap/subconscious/cadence-executor/CLAUDE.md

@@ -37,7 +37,7 @@ When a queue item contains `trigger job:<id>`:
 
 1. Use `ManageJob` (action: read) to verify the job exists.
 2. Read the job's `.state.json` sidecar file (path shown in job info).
-3. Set `last_run_at` to `null` in that file and write it back.
+3. Set `last_scheduled_at` to `null` in that file and write it back.
 4. The job scheduler (60-second cycle) will see it as due and spawn it.
 
 If the job doesn't exist or is already running, note the error and

package/bootstrap/var/cadence/DUODUO.md

@@ -34,11 +34,11 @@ To make the job scheduler pick up a job on its next 60-second scan,
 queue a state reset:
 
 ```
-- [ ] (cadence:fast) trigger job:<job-id> — reset last_run_at in its .state.json so the scheduler treats it as due
+- [ ] (cadence:fast) trigger job:<job-id> — reset last_scheduled_at in its .state.json so the scheduler treats it as due
 ```
 
 The cadence-executor will read the job's `.state.json` sidecar
-(in `~/.aladuo/var/jobs/active/<job-id>.state.json`), set `last_run_at`
+(in `~/.aladuo/var/jobs/active/<job-id>.state.json`), set `last_scheduled_at`
 to null, and the job scheduler spawns it within 60 seconds.
 
 ### Example: Memory Compression

package/bootstrap/var/jobs/DUODUO.md

@@ -32,7 +32,8 @@ created_at: 2026-02-17T10:00:00Z
 
 ```json
 {
-  "last_run_at": "2026-02-17T12:00:00Z",
+  "last_scheduled_at": "2026-02-17T12:00:00Z",
+  "last_run_at": "2026-02-17T12:01:30Z",
   "last_result": "success",
   "run_count": 42
 }
@@ -42,27 +43,27 @@ created_at: 2026-02-17T10:00:00Z
 
 1. **Created** via `ManageJob` tool (action: create)
 2. **Scanned** by job scheduler every 60 seconds
-3. **Spawned** as a session when `isJobDue(cron, last_run_at)` is true
+3. **Spawned** as a session when `isJobDue(cron, last_scheduled_at)` is true
 4. **Completed/Failed** — state updated, results routed to `notify` targets
 5. **Archived** via `ManageJob` tool (action: archive)
 
 ## How to Trigger a Job Immediately
 
 The job scheduler determines "due" by comparing `cron` against
-`last_run_at` in the state file. To force immediate execution:
+`last_scheduled_at` in the state file. To force immediate execution:
 
 **Option A — Via cadence queue (recommended):**
 
 Drop a `.pending` file in `~/.aladuo/var/cadence/inbox/`:
 
 ```
-- [ ] (cadence:fast) trigger job:<job-id> — reset last_run_at so scheduler treats it as due
+- [ ] (cadence:fast) trigger job:<job-id> — reset last_scheduled_at so scheduler treats it as due
 ```
 
 **Option B — Direct state edit (if you understand the implications):**
 
-Set `last_run_at` to `null` in `<job-id>.state.json`. The scheduler
-will see it as never-run and spawn it within 60 seconds.
+Set `last_scheduled_at` to `null` in `<job-id>.state.json`. The scheduler
+will see it as never-scheduled and spawn it within 60 seconds.
 
 Note: Option A is preferred because the cadence-executor can handle
 edge cases (check if job exists, verify it's not already running).