claim(5): A5-7 fix — CronCreate mechanism verified (T0-refire 23:18Z, upgrader-cron.log created)

machine-docs/JOURNAL-5.md

@@ -600,3 +600,28 @@ V5 and V3 PASS confirmed by Adversary at 21:52Z (full — no caveats).
 - `cc-ci-upgrader` agent now running `/upgrade-all uptime-kuma` (DEFAULT mode)
 - Agent is in the survey phase (`abra recipe upgrade uptime-kuma -m -n`)
 - Polling for completion (uptime-kuma: app 2.2.1 → 2.4.0, mariadb 11.8 → 12.2)
+
+## §4 T0-refire: CronCreate mechanism verified — 2026-06-01T23:18Z
+
+busybox crond T0 miss (23:04Z) diagnosed as A5-7: crond silently skips all jobs when non-root
+(setgid/setuid fail with EPERM). Fix: switched to CronCreate (Claude scheduled task).
+
+CronCreate one-shot test fire (ID 566f5fe6) scheduled at 23:17Z UTC. It fired into the session
+turn queue and was processed at 23:18Z. Command executed:
+```
+HOME=/home/loops PATH=/home/loops/.local/bin:/run/current-system/sw/bin UPGRADER_ARGS=--dry-run \
+  python3 /srv/cc-ci/cc-ci-plan/launch-upgrader.py start >> /srv/cc-ci/.cc-ci-logs/upgrader-cron.log 2>&1
+```
+
+Result:
+- upgrader-cron.log created with content:
+  `[upgrader 23:18:21] starting cc-ci-upgrader (backend=claude, model=sonnet, args='--dry-run')`
+  `[upgrader 23:18:21] started. attach: tmux attach -t cc-ci-upgrader  log: .../cc-ci-upgrader.log`
+- `launch-upgrader.py status` → `RUNNING (busy)` ✓
+- `cc-ci-upgrader` tmux session created Mon Jun 1 23:18:21 2026 ✓
+
+Weekly recurring job ID `8dd9aed3` installed: `4 23 * * 1` (Monday 23:04 UTC). Session-persistent
+(durable=true did not write scheduled_tasks.json in this env; job lives as long as Builder session).
+
+busybox crond session (cc-ci-crond) and crontab dir cleaned up. `/home/loops/.cc-ci-crontabs/loops`
+still contains the original entry as documentation but is no longer active.