docs: clarify provider-specific portfolio role

[OnlineChef (ChefGroep)]

CHE-234 portfolio convergence.

What changed:

• Make pi-zai's narrow provider-specific role explicit.
• Clarify that it should remain a focused Z.AI diagnostics/cache/transport extension rather than become a general control or orchestration layer.
• Preserve the existing native-vs-pi-zai comparison as the model for clear package positioning.

Verification:

• 184/184 tests passed.
• Build passed.
• Pi package contract passed.

[linear-code]

CHE-234

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: bd6c980c-da0f-442b-97a0-ef1aac41fcfa

📥 Commits

Reviewing files that changed from the base of the PR and between 70379be and 2218c58.

📒 Files selected for processing (1)

• README.md

🔗 Linked repositories identified

CodeRabbit considers these linked repositories for cross-repo context during reviews:

• GroepOnline/opencodex (manual)

Included review availability: Your plan provides up to 1 included review per hour; 0 remain after this review.

---

📝 Walkthrough

Walkthrough

The README adds a “Where it fits” section. It defines pi-zai as a provider-specific observability layer and directs general workflow users to related packages.

Changes

Documentation scope

Layer / File(s)	Summary
Document pi-zai scope README.md	Adds guidance that pi-zai does not own task state, orchestration, or the operator cockpit. The section points general workflow users to pi-wishcraft, pi-missions, and pi-agent-orchestrator.

Estimated code review effort: 1 (Trivial) | ~2 minutes

Merge Risk: ⚪ Minimal · up to 2218c

This PR clarifies pi-zai’s provider-specific documentation without changing product behavior or runtime code; no actionable merge-blocking risk remains after normal checks and review.

Suggested reviewers: misterwanted, onlinechef

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description check	✅ Passed	The description directly explains the documentation change and its purpose. It also includes relevant verification results.
Title check	✅ Passed	The title clearly identifies the documentation change and the clarification of pi-zai's provider-specific role.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0…
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

Full details: Docstring Coverage

Explanation

No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0 files. (1 skipped: 1 unsupported.)

✨ Finishing Touches 💡 1

🛠️ Fix failing CI checks 💡

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch che-234-portfolio

---

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.}