docs(cipher): store skill — /api/memory routes landed, 401 not 404 - #2204
Conversation
The 2026-04-01 known-issue note claimed Pmoves-cipher lacks /api/memory routes. Operator flagged it stale and live verification agrees: fork PR #5 (2026-07-14 wave, with the Qdrant embedding sidecar, BM25+dense RRF hybrid search, and Ollama fallback) implemented the CRUD routes; the live API returns 401 (auth required), not 404. Note updated to point callers at the API key instead of assuming the routes are absent. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
|
Warning Review limit reached
Next review available in: 14 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the 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 configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
✨ Finishing Touches🧪 Generate unit tests (beta)
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 |
Operator-flagged stale note, live-verified: Pmoves-cipher PR #5 (2026-07-14 wave — Qdrant embedding sidecar, BM25 sparse + dense RRF hybrid search, Ollama fallback, A2A discovery) implemented the
/api/memoryCRUD routes. Live :8105 probe returns 401 (auth required), not 404. The skill's 2026-04-01 known-issue block told agents the routes don't exist and to always fall back — now it points them at the API key requirement instead.Remaining tracked separately: monorepo gitlink promotion for Pmoves-cipher is non-FF (hardened branch was rebased upstream — no common ancestor with pin
cb3d3bed); needs a deliberate diverged-history promotion verifying the overlay survived.🤖 Generated with Claude Code