Direct 'git fetch origin main:refs/heads/main' fails when main is the
currently checked-out branch ('refusing to fetch into branch X checked
out at Y'). Update remote-tracking ref via plain 'git fetch origin main'
and push origin/main directly.

Signed-off-by: Chiliang Yao <[email protected]>
Co-Authored-By: Claude Opus 4.7 <[email protected]>

…ort flow

Cron-triggered TaskFlow extension that drafts a weekly report from the agent's
own session transcript, sends a Feishu confirmation card, loops on user
supplements, and writes the result into a configured Feishu doc using invisible
HTML-comment sentinels for idempotent splicing.

v2 adds an optional git-activity fact source: a clone-on-demand, author-filtered
`git log` runner exposed as `fetch_git_activity`, so completed bullets are
anchored in real commits. SSH-only by default; URL allowlist, name regex,
argv-only invocation, hooks/submodules/file-protocol disabled, per-op and
overall timeout caps, concurrency-bounded parallel ops, and offline tests with
local bare-repo fixtures.

Five tools: submit_weekly_report_draft, respond_to_weekly_report_card,
splice_weekly_report_doc, finalize_weekly_report, fetch_git_activity. CAS-
idempotent timeout sweeper for reminders + fail-on-expiry. Card-action trust
guards (controllerId / sessionKey / status / weekKey match before any flow
mutation). 84 colocated vitest cases.

Co-Authored-By: Claude Opus 4.7 (1M context) <[email protected]>

… partial-rm reporting

…e & speculative exports

…undary lint (P2.1)

…mum, lint coverage, module-load AJV

…2.2)

Introduces the child-side entrypoint for the Phase 2 cron subprocess architecture:
- `src/cli/run-cron-job/runtime.ts`: assertCronRunnerContext, writeRunnerResultFile, emitStdoutMarker
- `src/cli/run-cron-job/main.ts`: runCronJobHandler (injectable deps) + registerRunCronJobCommand
- Result file written atomically before stdout marker per plan I1 ordering invariant
- Verb registered in subcli-descriptors and register.subclis-core

Co-Authored-By: Claude Sonnet 4.6 <[email protected]>

…lication; tighten main.ts (P2.2)

…er lock (P2.3)

Piece 1 — Scheduler lock acquisition: start() acquires scheduler.lock via
acquireSchedulerLock(). When lock is held by another process, the scheduler
goes silent (schedulerLockHeld=true, no timer armed). Lock is released on
stop(). schedulerLockPath=null skips locking in tests.

Piece 2 — Subprocess spawn: executeDetachedCronJob routes isolated-agent jobs
through executeJobInSubprocess() when openClawNode+openClawBin are set.
Spawns: node <openclaw-bin> run-cron-job <jobId> --run-id <uuid>. Reads
result file on exit; falls back to stdout OPENCLAW_CRON_RESULT marker;
SIGTERM→SIGKILL grace on AbortSignal. Inline runIsolatedAgentJob dep is
preserved as fallback when bin paths are not set (tests, isolated modes).

resolveSubprocessBinPaths() only sets openClawBin when process.argv[1]
basename contains "openclaw" — prevents accidental subprocess activation in
vitest environments where argv[1] is vitest.mjs.

Piece 3 — Boot reconcile: loadCronStore() calls reconcileRunningJobStates()
after state merge. Four cases: no running key (no-op), running without runId
(cleared), result file present (terminal state applied), pid dead (cleared),
pid alive with matching start time (left alone). Uses readProcessStartTimeMs()
for pid-recycling detection.

Piece 4 — stopping flag: onTimer() returns early when state.stopping=true.
stop() sets stopping before releasing the lock handle.

New state fields: stopping, openClawNode, openClawBin, pidTable,
schedulerLockHandle, schedulerLockHeld.

New tests: subprocess-spawn.test.ts (6 cases), scheduler-lock-startup.test.ts
(2 cases), boot-reconcile.test.ts (6 cases).

Fixed scheduler-lock.test.ts "returns held" to use child 'spawn' event instead
of setTimeout to avoid fake-timer bleedover in --isolate=false worker.

All 990 cron tests pass.

Co-Authored-By: Claude Sonnet 4.6 <[email protected]>

…yped running field

…P2.5-b)

…mmit protocol)

… model (P2.6)

…dd doctor migrations (P3.2)

Run `openclaw doctor --fix` immediately after upgrade to migrate existing jobs to the new schema. Legacy `kind: "every"` jobs and jobs with non-"isolated" sessionTargets will be skipped at runtime until migrated. The `doctor --fix` command rewrites them to `kind: "cron"` with auto-computed expressions and sessionTarget "isolated".

…erMs (P3.2 gap close)

…ackward-compat

…ze test