chore(policy): peg-bands gruPolicyIntegration + GRU reference primacy cross-links

- Add gruPolicyIntegration block (referencePrimacyDoc, meshExecutionRole) to peg-bands.json
- Document parent-repo policy and CI verifier in README, bot policy, and oracles doc

Made-with: Cursor

docs/04-bot-policy.md

@@ -52,6 +52,8 @@ Important: this improves **tradability and price discovery**, but it does **not*
 
 ## Peg bands
 
+**GRU reference primacy (proxmox parent repo):** Bot deviation logic implements **corridors around oracle targets**; it does not replace institution-grade FX/GRU/XDR references. Canonical policy + integration checklist: proxmox `docs/04-configuration/GRU_REFERENCE_PRIMACY_AND_MESH_EXECUTION_MODEL.md`. The peg config carries a machine hook **`gruPolicyIntegration`** in [../config/peg-bands.json](../config/peg-bands.json) (validated by parent `scripts/verify/check-gru-reference-primacy-integration.sh`).
+
 See [../config/peg-bands.json](../config/peg-bands.json) and [05-oracles.md](05-oracles.md). Summary:
 
 - **USD-pegged**: Normal ±10–25 bps; stress ±50–150 bps; circuit break >2%

docs/05-oracles.md

@@ -17,4 +17,6 @@
 - Do not trade against a stale oracle; treat staleness as a risk trigger.
 - Document fallback order (e.g. primary chainlink, secondary Pyth, tertiary internal).
 
-Config and peg bands: [../config/peg-bands.json](../config/peg-bands.json).
+Config and peg bands: [../config/peg-bands.json](../config/peg-bands.json) (includes **`gruPolicyIntegration`** linking proxmox `docs/04-configuration/GRU_REFERENCE_PRIMACY_AND_MESH_EXECUTION_MODEL.md` — oracle targets remain subordinate to institution-grade references).
+
+Parent verifier: proxmox `scripts/verify/check-gru-reference-primacy-integration.sh`.