[Docs] Correct recent task and integration guidance

[roomote-community]

​Opened on behalf of @mrubens. Follow up by mentioning @roomote, in the web UI, or in Discord.

What changed

• document automatic and in-place recovery when a task's sandbox cannot start
• explain standalone artifact links, version selection, access checks, and source navigation
• document the Code Mode Integrations experiment and its authorization and fallback boundaries
• require custom multi-service deployments to provide the job-auth keypair to BullMQ

Why this change was made

The daily public-documentation audit inspected all 29 first-parent commits merged into develop during the exact window from 2026-09-19T03:00:45.841Z through 2026-09-20T03:00:45.841Z. These four durable task, integration, and self-hosting behaviors were the confirmed gaps not already covered by shipped docs or the overlapping open documentation pull requests.

Impact

Users and operators now have current recovery, artifact-sharing, experimental integration, and deployment-key guidance. This is a documentation-only change. The repository-prescribed Mintlify validation and broken-link check, git diff --check, oxlint, residual lint, 27 fast typechecks, and Knip all passed; browser proof was not applicable to the semantic docs-only correction.

[roomote-community]

1 issue outstanding. See task

• apps/docs/tasks.mdx:94 — Startup-retry guidance promises automatic retries for every task, but session-delegated starts retry only when the parent agent judges the failure transient.

_{Reviewed adc409c}

[roomote-community]

This states that every failed sandbox start is automatically retried, but session-delegated tasks take a different path: finishRun skips its automatic retry when a Fast parent exists, and the parent agent is instructed to retry only failures that appear transient. Please qualify this behavior (or scope the guarantee to direct tasks) so users do not expect automatic retries for every task start.