Added PACKAGE_SPLIT_EVAL.md

[jonathanMLDev]

• close Core/alliance package split evaluation #121

Summary by CodeRabbit

• Documentation
  • Added evaluation document detailing technical assessment and recommendations for future package organization.

[coderabbitai]

Warning

Review limit reached

@jonathanMLDev, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 42 minutes and 51 seconds. Learn how PR review limits work.

Your organization has run out of usage credits. Purchase more credits in the billing tab to continue.

⌛ How to resolve this issue?

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.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 6555e1ab-dbe2-4934-b470-54a2b1bd527e

📥 Commits

Reviewing files that changed from the base of the PR and between 0d669bf and d14b1c6.

📒 Files selected for processing (1)

• docs/PACKAGE_SPLIT_EVAL.md

📝 Walkthrough

Walkthrough

A decision document evaluates splitting the pinecone-read-only-mcp package into separate core and alliance npm packages. It describes the current single-package dual-export architecture, assesses technical feasibility and consumer impact, proposes a monorepo workspace structure, and recommends deferring the split until phase 5 deprecations are complete and one deprecation window elapses.

Changes

Package Split Evaluation Document

Layer / File(s)

Summary

Complete evaluation: recommendation through references docs/PACKAGE_SPLIT_EVAL.md

Top-level recommendation to defer the core/alliance package split until after phase 5 legacy-getter deprecation. Captures current architecture (single package, dual-export, existing source boundary in src/core/ vs src/alliance/). Evaluates technical feasibility, including module ownership, required tooling, and public API blockers (legacy facades still exported from core). Assesses consumer impact through a usage matrix and migration scenarios. Proposes monorepo workspace as the target structure and lists alternatives with tradeoffs. Defines decision rationale tied to published API readiness and tooling cost. Includes prerequisites and trigger checklist for proceeding with a split in the future, plus reference links to migration docs and deprecation policy.

🎯 1 (Trivial) | ⏱️ ~3 minutes

🐰 A document so clear and true,
The package split—defer it through and through!
Phase five must finish, facades fade away,
Then core and alliance go separate someday. 📦✨

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately summarizes the primary change—adding the PACKAGE_SPLIT_EVAL.md documentation file.
Linked Issues check	✅ Passed	The pull request fulfills all acceptance criteria from issue #121: it delivers a technical feasibility document evaluating core/alliance package separation, assesses dependencies and current coupling, proposes a monorepo workspace structure, and provides a clear decision recommendation.
Out of Scope Changes check	✅ Passed	The pull request contains only a documentation file directly addressing the technical evaluation requested in issue #121, with no out-of-scope changes.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

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 and usage tips.}

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
⚠️ Please upload report for BASE (main@61605dd). Learn more about missing BASE report.

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #152   +/-   ##
=======================================
  Coverage        ?   86.73%           
=======================================
  Files           ?       39           
  Lines           ?     1598           
  Branches        ?      544           
=======================================
  Hits            ?     1386           
  Misses          ?      210           
  Partials        ?        2           

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@docs/PACKAGE_SPLIT_EVAL.md`:
- Around line 235-255: The markdown fenced directory tree is missing a language
tag (triggering MD040); edit the fenced block that shows the project tree (the
triple backticks surrounding the tree) and add the `text` language tag so the
opening fence becomes ```text, leaving the contents unchanged.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: e72aeb1f-4408-44b1-91ea-9807ebf9bc1d

📥 Commits

Reviewing files that changed from the base of the PR and between 61605dd and 0d669bf.

📒 Files selected for processing (1)

• docs/PACKAGE_SPLIT_EVAL.md