docs: cover three reliability fixes from PraisonAI PR #3960

[praisonai-triage-agent]

Fixes #2960

Documents three user-visible reliability fixes from PraisonAI PR #3960 (MervinPraison/PraisonAI#3960), verified against merged source.

Changes

Fix 1 - asequential() failure-cascade parity

• docs/features/async.mdx: new 'Failure cascade in asequential()' section with a three-task A->B->C example and a sequenceDiagram showing the skip cascade.

Fix 2 - Tool executor pool recycling on tool_timeout

• docs/configuration/tool-config.mdx: 'Reliability after a timeout' Note (2-worker pool, recycle on timeout, bounded).
• docs/features/yaml-configuration-reference.mdx: one-sentence append to the tool_timeout row.
• docs/features/concurrency.mdx: executor-details callout on pool recycling.

Fix 3 - Doom-loop NO_PROGRESS recency filter

• docs/features/escalation-doom-loop.mdx: new page covering the escalation DoomLoopDetector (six DoomLoopType values, RecoveryAction ladder, full DoomLoopConfig table, and the PR #3960 recency-window fix).
• docs/features/doom-loop-detection.mdx: disambiguation Note linking the two subsystems.
• docs/features/autonomy-loop.mdx: notes on the doom_loop_threshold row and doom_loop completion accordion.
• docs/docs.json: registered the new page under Features.

All SDK claims verified against praisonaiagents source. No files under docs/concepts/ were touched.

Generated with Claude Code

[MervinPraison]

@coderabbitai review

[MervinPraison]

/review

[MervinPraison]

@gemini review this PR

[coderabbitai]

⚠️ Action not completed

Review rate limited.

Note: CodeRabbit is an incremental review system and does not re-review already reviewed commits. This command is applicable only when automatic reviews are paused.

[qodo-code-review]

Qodo reviews are paused for this user.

Troubleshooting steps vary by plan Learn more →

On a Teams plan?
Reviews resume once this user has a paid seat and their Git account is linked in Qodo.
Link Git account →

Using GitHub Enterprise Server, GitLab Self-Managed, or Bitbucket Data Center?
These require an Enterprise plan - Contact us
Contact us →

[coderabbitai]

Warning

Review limit reached

@MervinPraison, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 58 minutes

Limit details: You’ve used all 1 included review currently available under your plan.

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 26b719f8-3cc7-439b-9885-0561ebd4f43a

📥 Commits

Reviewing files that changed from the base of the PR and between ec0377c and a2a5c73.

📒 Files selected for processing (8)

• docs/configuration/tool-config.mdx
• docs/docs.json
• docs/features/async.mdx
• docs/features/autonomy-loop.mdx
• docs/features/concurrency.mdx
• docs/features/doom-loop-detection.mdx
• docs/features/escalation-doom-loop.mdx
• docs/features/yaml-configuration-reference.mdx

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[MervinPraison]

Merge gate scan — eligible for assessment. Claude merge gate will assess and may auto-merge on an APPROVE verdict.

[praisonai-triage-agent]

MERGE_GATE_VERDICT: APPROVE

All checklist items passed:

• Files: 8 files changed (314 additions, 2 deletions) — within docs-primary limits (1200 lines / 40 files). All changes in docs/features/, docs/configuration/, and docs/docs.json. No docs/concepts/ files touched.
• docs.json: Nav-only change (one entry added: features/escalation-doom-loop) — allowed.
• Labels: pipeline/merge-ready, claude-merge-gate-active — no blocking labels.
• Reviews: No CHANGES_REQUESTED. CodeRabbit and Qodo were rate-limited; no substantive objections.
• CI on HEAD a2a5c737b: scan-conflicts ✅, bot-pr-trigger-reviews ✅, pipeline-sync ✅, CodeRabbit ✅; skips (claude-rebase, Mintlify Deployment) are non-failures.
• Content: Documents three real reliability fixes from PraisonAI PR #3960 (asequential failure-cascade parity, tool executor pool recycling on timeout, doom-loop recency filter), all placed correctly in docs/features/.

[MervinPraison]

Merged by Claude PR merge gate (claude-merge-gate.yml).
Verdict: MERGE_GATE_VERDICT: APPROVE
SHA: a2a5c73
Method: merge

[MervinPraison]

Merge gate scan — not eligible for auto-merge.

• not open
• already merged by gate
• mergeState=UNKNOWN

Actions: wait for CI and the Claude review chain, or add label needs-manual-review and merge manually.
Opt out: label no-auto-merge.