[flows-tinyflows] cron bug: stdout println in store, unpaired run events, stale flow-subscriber config #57

Moved from tinyhumansai#8035, which is closed in favour of this issue. Part of tinyhumansai#8055.

• cron/store.rs:178: println!("✅ Removed cron job {id}") in library code (boot prune, RPC, tools). Injects a non-protocol line into stdout-framed transports (mcp/server/stdio.rs). Use tracing.
• CronJobTriggered is published only on Execute (cron/scheduler/executor.rs:101-108) but CronJobCompleted for every delivery (run_delivery.rs:46-51), so flow/system runs emit Completed without Triggered.
• cron/bus_host.rs:141-144: FlowTriggerSubscriber is built with the first tick's config; set_config (:96-101) never refreshes it.

Regression tests for each (stdout capture, event pairing, config refresh).

Done when: each defect above has a regression test that fails on the unfixed code and passes after the fix. Gates: cargo check (root + crates/openhuman-app), pnpm rust:layout, node scripts/ci/check-feature-forwarding.mjs, pnpm debug rust cron, and the touched crates' tests. RPC namespace strings, model-facing tool names and DomainEvent variant names stay unchanged unless the issue says otherwise.

Agent brief

• Files to consider (paths under crates/openhuman-core/src/ unless rooted): cron/store.rs, cron/scheduler/executor.rs, cron/scheduler/run_delivery.rs, cron/bus_host.rs
• Research: None.
• Workflow: an implementing-an-epic step.
• Subagent: systematic-debugger.
• Dependencies: none.

Parent: tinyhumansai#8055