You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
cron/ops.rsrun_and_record and cron/tools/run.rs:105-127 → RunJobNow.
Delete MANUAL_RUNS/RunGuard (cron/scheduler.rs:94-119) and LoopSlot (:68-92) if the module takes SchedulerSlot.
cron/scheduler/executor.rs:26-97 per-run state map → Attempt detail.
cron/scheduler/run_delivery.rs:68-131stand_in and the success recompute (:38-42) → job on ScheduleTrigger, success on Deliver.
Bump the tinyflows gitlink and re-pin the registry record (modules/registry/records_flows.rs, digests verbatim from the release checksum.toml); delete the host copy and its tests in the same PR.
Done when: the rows above are gone from crates/openhuman-core/src/cron/ (moved, deleted or reduced to the stated host adapter), with their tests moved alongside. 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.
Agent brief
Files to consider (paths under crates/openhuman-core/src/ unless rooted): cron/ops.rs, cron/tools/run.rs, cron/scheduler.rs, cron/scheduler/executor.rs, cron/scheduler/run_delivery.rs
The Schedule v6 adoption now has a verified external storage prerequisite: tinyhumansai#8064 (epic tinyhumansai#7973), currently open. Canonical OpenHuman main still pins TinyStorageDrivers v0.11.0. The owning TinyFlows schema-v2 store requires TSD v1 record metadata; an isolated host pin would also break the TinyAgents StorageBackend trait boundary and existing module wire clients. PR tinyhumansai#8064 already implements that coordinated host/module cutover, so this leaf will consume it after canonical merge rather than duplicate the separate epic.
The existing #74/#75 integration and all original scope are preserved. Cron tests compile; the caller-cancellation regression has a genuine one-test RED at 559ad32; the per-store scheduler regression has a historical RED and restored GREEN. Copilot focused tests, strict baseline comparison, and a locked desktop build pass at 2aa9f78 (strict lint itself retains the documented inherited diagnostics). The owning module follow-up is tinyhumansai/tinyflows#160, where review fixes and explicit module-owned migration operations are still being completed. No unreleased TinyFlows or TSD host pin has been introduced.
Next: merge the storage prerequisite through its own upstream process, integrate current upstream into the flows epic with a normal merge, then adopt the actual published TinyFlows module and complete this leaf's callback ownership and migration-before-use gates. This is a dependency update, not a partial completion of #75.
Activity
senamakel commentedon Oct 17, 2026
The Schedule v6 adoption now has a verified external storage prerequisite: tinyhumansai#8064 (epic tinyhumansai#7973), currently open. Canonical OpenHuman main still pins TinyStorageDrivers v0.11.0. The owning TinyFlows schema-v2 store requires TSD v1 record metadata; an isolated host pin would also break the TinyAgents StorageBackend trait boundary and existing module wire clients. PR tinyhumansai#8064 already implements that coordinated host/module cutover, so this leaf will consume it after canonical merge rather than duplicate the separate epic.
The existing #74/#75 integration and all original scope are preserved. Cron tests compile; the caller-cancellation regression has a genuine one-test RED at 559ad32; the per-store scheduler regression has a historical RED and restored GREEN. Copilot focused tests, strict baseline comparison, and a locked desktop build pass at 2aa9f78 (strict lint itself retains the documented inherited diagnostics). The owning module follow-up is tinyhumansai/tinyflows#160, where review fixes and explicit module-owned migration operations are still being completed. No unreleased TinyFlows or TSD host pin has been introduced.
Next: merge the storage prerequisite through its own upstream process, integrate current upstream into the flows epic with a normal merge, then adopt the actual published TinyFlows module and complete this leaf's callback ownership and migration-before-use gates. This is a dependency update, not a partial completion of #75.
senamakel commentedon Oct 18, 2026
Merged in #189 (d8717e4), completing the atomic #74/#75 cohort.