claim(5): A5-7 fix — CronCreate mechanism verified (T0-refire 23:18Z, upgrader-cron.log created)
Some checks failed
continuous-integration/drone/push Build is failing
Some checks failed
continuous-integration/drone/push Build is failing
This commit is contained in:
@ -1266,3 +1266,11 @@ and `state=pending` (on trigger) / `success|failure` (on build finish). `testme-
|
||||
Alternative option 2 (scan PR comments for `<!-- cc-ci:testme -->` marker) was rejected as fragile.
|
||||
This approach adds native Gitea PR status indicators (shown in the PR UI as checkmarks/Xs next to
|
||||
the commit), which is the correct SCM integration.
|
||||
|
||||
- **§4 weekly cron: CronCreate (not busybox crond).** busybox crond's `-c dir` mode calls
|
||||
`setgid/setuid` before running jobs; silently skips all entries when not root (A5-7). Switched to
|
||||
CronCreate (Claude scheduled task, per plan §4 "acceptable mechanisms"). Weekly job ID `8dd9aed3`
|
||||
fires every Monday 23:04 UTC. Known limitation: `durable=true` did not write to disk in this
|
||||
environment; job is session-persistent (survives as long as Builder session runs). T0-refire
|
||||
verified: CronCreate test fire at 23:17Z → upgrader started, upgrader-cron.log created, status
|
||||
RUNNING. (2026-06-01)
|
||||
|
||||
Reference in New Issue
Block a user