docs(provider-integration): mark perplexity-decider verified-live - #1900
Conversation
The manifests README lets manualTestStatus be verified-live, and laya and typesafe already carry it. The review-docs pass set perplexity-decider to ci-mocked-only as the conservative value and said its owner could upgrade it if the live probe counted. It does count. Live evidence, against the real API with a real key: - test:decide with only PERPLEXITY_API_KEY set: 130 passed, 0 failed, 12 skipped. The skips are the XOR, Laya and gateway live sections. The seven live Perplexity cases, 18.28 to 18.34, passed. - Probes through the published @juspay/neurolink 12.44.1 in an isolated install: batching, the credentials slices, the 262,144-token ceiling and the 2,048-tile image rule. verify:provider-onboarding still reports every provider onboarded.
✅ Single Commit Policy - COMPLIANTStatus: Policy requirements met • 1 commit • Valid format • Ready for merge 📊 View validation details📝 Commit Details
✅ Validation Results
🤖 Automated validation by NeuroLink Single Commit Enforcement |
|
Navigate logical layers of code changes, visualize relationships, and explore their blast radius. No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configuration
📒 Files selected for processing (1)
Included review availability: This review used your included allowance. Your plan provides up to 2 included reviews per hour; 1 remain after this review. 📝 WalkthroughWalkthroughThe Perplexity decider manifest’s ChangesProvider manifest
Priority: ⬇️ Low Estimated code review effort: 1 (Trivial) | ~2 minutes Change: Other Merge Risk: ⚪ Minimal · up to This change records the reported Perplexity live-verification status and does not affect runtime behavior. No material merge risk is established. Architecture SummaryArchitecture risk: 🔵 Low · up to The change affects 1 system. Changed systems: Architecture concerns Review detailsSystems and components
Before / after behavior
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches 💡 1🧪 Generate unit tests (beta)
🛠️ Fix failing CI checks 💡
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. Comment |
Documentation Validation Results🚀 Documentation validation passed!
📦 Build artifact uploaded successfully. Ready for deployment preview. Commit: |
|
🎉 This PR is included in version 12.46.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
1 participant
Why
#1894 set
perplexity-decidertoci-mocked-onlyas the conservative value, and its description said the owner could upgrade it if the live probe counted. It does count, andlayaandtypesafealready carryverified-live. I asked for the change on that PR (#1894 (comment)); it merged with the old value, so this makes it.The change
One value in
docs/provider-integration/manifests/perplexity-decider.json:manualTestStatusgoes fromci-mocked-onlytoverified-live. The README listsverified-liveas one of the four documented values, and the onboarding gate only requires a string.Live evidence
test:decidewith onlyPERPLEXITY_API_KEYset, against the real API: 130 passed, 0 failed, 12 skipped. The skips are the XOR, Laya and gateway live sections, which need other keys or servers. The seven live Perplexity cases (18.28 to 18.34) passed.@juspay/neurolink12.44.1 in an isolated install: 300 questions sent as 128, 128 and 44, and 640 as five requests of 128; the credentials slices; the 262,144-token ceiling; the 2,048-tile image rule.Checks run
verify:provider-onboardingexits 0 withperplexity-decideronboarded. Prettier passes on the file. The search index anddocs/apido not index this manifest, so nothing needed regenerating.Not changed
addedInPRstill sayspendinghere, as it does on the sibling manifests; that is outside this change.Summary by CodeRabbit