Design rope fact inspector and range why UI

[flyingrobots]

Problem

HT-0149 requires :why to cite head, leaf, blob, rewrite, diff, tick, and checkpoint evidence, but the inspector UI is deferred. jedit needs a product surface that lets users and agents inspect graph-backed text authority for a selected range.

Acceptance Notes

• Define the dev-facing rope fact inspector shape.
• Define :why range output over graph-backed facts.
• Keep UI claims backed by runtime evidence only.
• Link the policy back to HT-0149 and PR Document graph-backed rope runtime gate #205.

[coderabbitai]

🔗 Related PRs

#195 - Add honest why observation coordinates [merged]

---

📝 Issue Planner

_{Check the box below or use the @coderabbitai plan command to generate an implementation plan and prompts that you can use with your favorite coding assistant.}

• Create Plan

---

🧪 Issue enrichment is currently in open beta.

You can configure auto-planning by selecting labels in the issue_enrichment configuration.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

💬 Have feedback or questions? Drop into our discord!