feat(hatchet): track integrated Hatchet branch work

[kattsushi]

Problem Description

We have completed a substantial Hatchet integration track on the hatchet branch, but there is no GitHub issue tracking the approved scope and progress for this work. PRs in this repo are expected to link an issue, and the work now spans multiple related slices that should be reviewed as one coordinated initiative.

Relevant docs / source material:

• docs/prds/PRD-effectify-hatchet.md
• docs/design/hatchet-design.md
• docs/specs/hatchet-spec.md
• docs/proposals/hatchet-integration.md

Proposed Solution

Create a tracking issue for the Hatchet integration initiative that consolidates the completed and near-completed work on the branch so a PR can reference a single source of truth.

Scope covered on the branch includes:

• Hatchet SDK integration baseline for @effectify/hatchet
• SDK upgrade to @hatchet-dev/typescript-sdk@1.21.0
• React Router browser harness for future browser-level validation
• Client/demo/test slices for:
  • events
  • schedules
  • crons
  • observability (logs / metrics / run monitoring)
  • webhooks
  • rate limits
  • filters
  • workflow management
• Coverage hardening for Hatchet bootstrap / logger / mock client / workflow registration / demo orchestration
• Architectural cleanup items such as:
  • direct Data.TaggedError instantiation (no redundant static of(...) factories)
  • Effect-first duration boundaries where appropriate (for example rate limits using Duration.Input)
  • direct yielding of yieldable tagged errors without redundant Effect.fail(...)

Affected Area

Other

Alternatives Considered

• Creating one issue per slice. This is possible later, but right now a single tracking issue is the fastest way to align the branch with the repo workflow and unblock PR creation.
• Opening a PR without an issue. This would conflict with the repository workflow expectations.

Additional Context

Recent branch commits include:

• feat(hatchet): add workflow management demo slice
• refactor(hatchet): normalize client error yielding
• test(hatchet): harden infrastructure coverage

This issue is intended as the umbrella tracking artifact for the current Hatchet branch work, not as a request for new functionality beyond what is already captured in the branch and docs.