docs: document aworkflow() loop-task pre-expansion parity (Gap 1)

[praisonai-triage-agent]

Fixes #2432

Documents Gap 1 from PR MervinPraison/PraisonAI#3326 — aworkflow() now pre-expands task_type="loop" start tasks per input-file row, matching the sync workflow() engine.

Changes

• docs/best-practices/task-orchestration.mdx — new Async Loop Expansion subsection next to the existing task_type="loop" example: a <Note> crediting PR #3326 with before/after behaviour, a copy-paste aworkflow() example (one subtask per CSV row), and a standard-palette Mermaid diagram showing sync/async parity.
• docs/features/thread-safety.mdx — one extra bullet under the existing aworkflow() state-lock note covering per-turn tool tracking (_turn_tools_used) now being lock-guarded. No internals taught.

Compliance

• Nothing touched under docs/concepts/, docs/js/, docs/rust/.
• docs.json unchanged — no new sidebar entry.
• Gap 3 (MCP skill-gate) not duplicated.
• API surface verified against synced praisonaiagents/process/process.py (sync loop pre-expansion block confirms the API and behaviour).

Generated with Claude Code

[MervinPraison]

@coderabbitai review

[MervinPraison]

/review

[MervinPraison]

@gemini review this PR

[gemini-code-assist]

Caution

The consumer version of Gemini Code Assist on GitHub has been sunset. All code review activity has officially ceased.

[coderabbitai]

✅ Action performed

Review finished.

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: 48 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

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: 5b79bf9e-649d-4614-b20e-cdfac8f55550

📥 Commits

Reviewing files that changed from the base of the PR and between c576060 and 5418ce1.

📒 Files selected for processing (2)

• docs/best-practices/task-orchestration.mdx
• docs/features/thread-safety.mdx

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch claude/issue-2432-20260727-1036

---

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 if MERGE_GATE_VERDICT: APPROVE.

[MervinPraison]

Merge gate scan — eligible for assessment. Claude merge gate will assess and may auto-merge if MERGE_GATE_VERDICT: APPROVE.

[praisonai-triage-agent]

MERGE_GATE_VERDICT: APPROVE

Checklist results:

• Labels: Only claude-merge-gate-active — no blocking labels (security, breaking-change, needs-manual-review, release). ✅
• Sensitive paths: No changes to .github/workflows/, mint.json, or docs.json. ✅
• File placement: docs/best-practices/task-orchestration.mdx and docs/features/thread-safety.mdx — both allowed locations. No docs/concepts/ changes. ✅
• Size: 2 files, 67 additions, 0 deletions — well within docs-primary limits (1200 lines / 40 files). ✅
• CI on HEAD 5418ce1c: bot-pr-trigger-reviews ✅, pipeline-sync ✅, scan-conflicts ✅, CodeRabbit ✅ (rate-limited, not blocking). ✅
• Reviews: No CHANGES_REQUESTED reviews. ✅
• Documentation quality: New "Async Loop Expansion" subsection is copy-paste ready, SDK-verified against praisonaiagents/process/process.py, beginner-friendly with <Note> callout and Mermaid parity diagram. Thread-safety bullet is concise and accurate. ✅

[MervinPraison]

Merged by Claude PR merge gate (claude-merge-gate.yml).
Verdict: MERGE_GATE_VERDICT: APPROVE
SHA: 5418ce1
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.