chore(hirag): sync PMOVES-HiRAG gitlink — upstream through 2026-06-16 - #3084
Conversation
…hrough 2026-06-16) Fork merged 3.5 months of upstream hhy-huang/HiRAG drift (through PR #7, 2026-06-16): DeepRefine follow-up refs, badges, misc. PMOVES CHIT overlay preserved; 3 cosmetic readme conflicts resolved both-sides. Upstream gained per-provider search scripts (deepseek/glm/ollama/openai/cohere) relevant to the model-suits harness-integration doctrine.
|
Important Review skippedAuto reviews are limited based on label configuration. 🏷️ Required labels (at least one) (1)
Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Advanced Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
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 |
|
📋 Cipher Lane (inline, 2026-09-16) — re-verify sweep. Verdict: APPROVE (post-rebase). PMOVES-HiRAG submodule gitlink advances by 1 commit (chore(hirag): sync upstream through 2026-06-16). Single-line diff. 1/1. Action: rebase onto current main (PR is BEHIND); merge. Things that are FINE:
(Note: gh pr review --approve blocked because gh authenticates as POWERFULMOVES, the PR author. Posting as comment.) — 5090-CLAUDE |
CONTEXT for reviewers
Operator direction (2026-09-15): review hi-rag — both services, repo freshness, upstream origin, HF model alternatives (deepseek-harness-style setups), model-suits integration.
What this does
Bumps the
PMOVES-HiRAGgitlink e904b12 → d8484b2 — the fork's merge of 3.5 months upstream (hhy-huang/HiRAG through 2026-06-16, PR #7). Fork synced via merge-upstream locally: 3 cosmetic readme conflicts (badge/architecture/license blocks) resolved both-sides, zero markers remaining, PMOVES CHIT overlay intact, pushed to the fork'sPMOVES.AI-Edition-Hardenedbranch.Why it matters for model-suits/harness doctrine
Upstream is provider-pluggable by design:
hi_Search_{deepseek,glm,ollama,openai,cohere}.py+ config.yaml blocks per provider (chat + embedding + dims per provider: openai 1536 / glm 2048 / cohere 1024). This maps 1:1 ontopmoves/configs/model-suits/(19 suits: glm-5.2, glm-4.7, kimi-k2, MiniMax-M3, nemotron-3-super, qwen3.6, claude-*, deepseek via tac_trees/deepseek-harness.tac.yaml) — a model-suit can carry its HiRAG provider block. 'PMOVES jumps into any harness with full settings' = suit declares provider+models+dims → HiRAG reads it → same retrieval stack on every harness.Not in this PR (follow-up lanes)
pmoves-hirag-mcpsubmodule: fork at 0ec18d8 (2026-06-21) — separate gitlink lane after its own upstream check