Community surface: ROADMAP, issue/PR templates, troubleshooting (addresses #18)

[vornicx]

Implements the cheap, high-signal in-repo items from the outside review in #18 (P1.2 community surface + the P2 troubleshooting ask). All additive — no product code touched, based on current main (1.0.0).

What's here

• ROADMAP.md — the semver contract made visible (as Feedback from a happy user: pre-1.0 credibility gaps + a distribution plan (Midas deserves way more visibility) #18 suggested), the design invariants stated as non-negotiable (no-LLM / local / source-traceable / governed), what shipped in 1.0.0, a help-wanted near-term list, and — on brand — an explicit "not planned" section tied to the measured ceilings (naive distillation 0.37→0.08, whole-conversation aggregation). It admits the trade in the same place it states the plan.
• .github/ISSUE_TEMPLATE/ — a bug report that pre-fills the midas doctor block (config paths + versions only, safe to paste), a feature request that asks up front whether the idea adds an LLM to the ingest/query path (so the eval-first bar is set before the discussion starts), and a config.yml routing questions to Discussions and to the benchmark-repro invitation.
• .github/PULL_REQUEST_TEMPLATE.md — a checklist that separates the measure-everything core bar from the lighter docs/examples path.
• README "Troubleshooting" — surfaces midas doctor as the one-command diagnosis with a symptom→fix table (the Feedback from a happy user: pre-1.0 credibility gaps + a distribution plan (Midas deserves way more visibility) #18 P2 ask).
• CONTRIBUTING "A lighter bar for docs & examples" — explicitly relaxes the eval-first bar for docs/guides/examples, so a first contribution isn't gated by the retrieval-core rigor (the Feedback from a happy user: pre-1.0 credibility gaps + a distribution plan (Midas deserves way more visibility) #18 P1.2 ask).

Deliberately not here

• The README comparison table — that's docs(readme): add a skimmable 'How Midas compares' table #19, already open from @L4s4rt3. I verified its numbers against BENCHMARKS.md (all check out); no reason to duplicate it.
• Anything that needs a maintainer action or a decision: enabling Discussions, submitting to MCP directories, the paid Mem0/Letta head-to-head and n≥200 judged benchmarks, the docs site, and the "Midas Memory" branding / repo rename. These are the strategic items from Feedback from a happy user: pre-1.0 credibility gaps + a distribution plan (Midas deserves way more visibility) #18 — noted here so the roadmap and templates (which link to Discussions) light up once you flip those on.

Note: the issue-template config.yml and several links point at a Discussions tab; those links 404 until Discussions is enabled in repo settings.

🤖 Generated with Claude Code

https://claude.ai/code/session_01Deray2qcPRy1hZVQnboHp4

---

Generated by Claude Code