Pre-flight checks
Problem
@effectify/hatchet exposes an alpha workflow-centric API that does not provide the intended Effect v4 task-first model, typed boundaries, scoped resources, or deterministic in-memory execution.
Proposed solution
Modernize the package through a feature-branch chain:
- Introduce the typed task core and deterministic direct execution.
- Add the verified live Hatchet SDK boundary and scoped worker lifecycle.
- Add scheduling, cron, cancellation, and complete consumer migration.
Acceptance boundaries
- Preserve Effect v4 conventions and typed error/cause channels.
- Keep live SDK adaptation behind the package boundary.
- Verify every slice independently with Nx targets and bounded review.
- Remove the legacy workflow/effectifier surface as a deliberate breaking change.
Delivery
Tracker branch: feat/hatchet-v4-modernization
PR 1 branch: feat/hatchet-v4-core
Pre-flight checks
Problem
@effectify/hatchetexposes an alpha workflow-centric API that does not provide the intended Effect v4 task-first model, typed boundaries, scoped resources, or deterministic in-memory execution.Proposed solution
Modernize the package through a feature-branch chain:
Acceptance boundaries
Delivery
Tracker branch:
feat/hatchet-v4-modernizationPR 1 branch:
feat/hatchet-v4-core