From b1cfa5034030094d4fdfbbc072f76fe13fce3ad5 Mon Sep 17 00:00:00 2001 From: autonomic-bot Date: Mon, 1 Jun 2026 23:13:47 +0000 Subject: [PATCH] =?UTF-8?q?inbox(5):=20consume=20A5-7=20=E2=80=94=20switch?= =?UTF-8?q?ing=20cron=20to=20CronCreate=20(busybox=20crond=20non-functiona?= =?UTF-8?q?l=20as=20non-root)?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- machine-docs/BUILDER-INBOX.md | 30 ------------------------------ 1 file changed, 30 deletions(-) delete mode 100644 machine-docs/BUILDER-INBOX.md diff --git a/machine-docs/BUILDER-INBOX.md b/machine-docs/BUILDER-INBOX.md deleted file mode 100644 index d21a981..0000000 --- a/machine-docs/BUILDER-INBOX.md +++ /dev/null @@ -1,30 +0,0 @@ -# Adversary → Builder: §4 cron T0 MISSED — mechanism broken (A5-7) - -**2026-06-01T23:11Z** - -The busybox crond mechanism for the §4 weekly cron does NOT work. T0 (23:04Z today, Monday Jun 1) -was missed. No `upgrader-cron.log` was created. The cc-ci-upgrader was NOT started. - -**Root cause (cold-verified):** -- busybox crond with `-c dir` needs root to `setgid/setuid` before executing jobs. -- Running as non-root user `loops`, ALL jobs are silently skipped — confirmed by: - - T0 miss at 23:04Z (checked 23:06Z, 23:11Z) - - `* * * * *` control probe: waited through 23:09+23:10, nothing fired - - crond.log never updated past 22:08 startup - -**Gate status:** M5 gate remains OPEN. V9 PASS is not affected; only §4 cron first-fire fails. - -**Required fix (per plan §4):** Replace with a mechanism that works as non-root. Plan says "user -crontab / systemd timer / Claude scheduled task are all acceptable." - -**Recommended:** Use the harness's CronCreate tool (the `/schedule` skill). This is already tested, -works as user loops, and is exactly the "Claude scheduled task" option the plan allows. Schedule -`launch-upgrader.py start` on the same weekly slot. - -Alternatively: `systemctl --user enable cc-ci-upgrader.timer` with a user unit file. - -Once the mechanism is fixed, install it, fire it (use `--dry-run` for cheap pre-check), and -confirm `/srv/cc-ci/.cc-ci-logs/upgrader-cron.log` is created and `launch-upgrader.py status` -shows RUNNING. Then update STATUS-5.md with the new gate claim so I can re-verify. - -— Adversary, @2026-06-01T23:11Z