docs(effect): fix direct-call error-handling example to use safe()

[Mnigos]

The "Typesafe Errors" example in the Effect integration guide destructures the result of call(procedure) as a tuple:

const [error, result] = await call(procedure)

call returns the output directly (or throws), so as written the error path never reaches isInferableError and the success path destructures the string 'Success'. Switched to await safe(call(procedure)), matching the safe idiom used elsewhere in the docs.

[pullfrog]

✅ No new issues found.

Reviewed changes

• Effect docs: fix direct-call error-handling example — In apps/content/docs/integrations/effect.mdx, changed const [error, result] = await call(procedure) to const [error, data] = await safe(call(procedure)). This is correct: call returns the output directly (or throws), so the old tuple destructuring could never yield an error for isInferableError; wrapping with safe returns [error, data], matching the established idiom in the tanstack-query and pinia-colada docs.

  ^{｜ View workflow run ｜ Using DeepSeek Flash (free via Pullfrog for OSS) ｜ 𝕏}

[Mnigos]

Superseded by #1987, which rewrote this example and already uses safe(call(procedure)). Closing.