Feature request: ship a curated `.obsidian/graph.json` with the scaffold (filter structural files + color groups matching vault-colors.css)

Loving the plugin so far — thanks for putting it together.

One small papercut on my end: after /wiki scaffold, the first time I opened the Graph View it was kind of unreadable. The structural files (index, log, hot, overview, every _index) back-link to almost everything, so they show up as huge hub nodes and visually drown the actual paper ↔ concept ↔ entity backbone. Add the gray ghost nodes from the _templates/ placeholders (paper-1, subject-a, broader-concept, …) and the graph looks busier than the knowledge actually is.

I noticed the scaffold already drops .obsidian/snippets/vault-colors.css with a clean per-folder palette, but it doesn't drop a .obsidian/graph.json. So I ended up hand-crafting one that:

• filters by the type: frontmatter the plugin already enforces — -["type":"meta"] -["type":"overview"]
• excludes the template placeholders — -path:"_templates"
• turns on hideUnresolved so the gray ghosts disappear
• color-codes content nodes using the same hex values already in vault-colors.css, so the file-explorer sidebar and the graph share one palette

Roughly:

{
  "search": "-[\"type\":\"meta\"] -[\"type\":\"overview\"] -path:\"_templates\"",
  "hideUnresolved": true,
  "showOrphans": false,
  "colorGroups": [
    { "query": "[\"type\":\"paper\"]",      "color": { "a": 1, "rgb": 13537656 } },
    { "query": "[\"type\":\"concept\"]",    "color": { "a": 1, "rgb": 14474410 } },
    { "query": "[\"type\":\"entity\"]",     "color": { "a": 1, "rgb": 12945088 } },
    { "query": "[\"type\":\"domain\"]",     "color": { "a": 1, "rgb":  5227007 } },
    { "query": "[\"type\":\"question\"]",   "color": { "a": 1, "rgb":  6986069 } }
  ]
}

(rgb integers are just the decimal form of the existing --wiki-* hex codes — so if someone tweaks the CSS, the graph stays in sync as long as they mirror the same number.)

Here are before and after comparison images: