Detect #sym references and fix diagnostics logging

[Copilot]

The extension now detects #sym aliases in addition to #symbol references, and the diagnostics panel's DEBUG console.log statements were interfering with the logging guidelines.

Changes

Symbol Detection

• Added /#sym\b/gi pattern matching to detect short-form symbol references
• Extract symbols from contentReferences entries with kind='reference' and name field
• Store symbols in byPath with #sym: prefix for display differentiation

Log Viewer Display

• Render symbols with 🔤 icon (vs 📄 for files)
• Separate symbols and files in detailed context view:

  Files: extension.ts: 2, main.ts: 1
  Symbols: MyFunction: 1, MyClass: 2
  

Diagnostics Logging

• Removed DEBUG-prefixed console.log statements that violated logging guidelines
• Documented architecture: extension uses outputChannel.appendLine() → Output panel, webviews use console.log() → DevTools (separate systems)

Example Detection

// Text pattern matching
"Look at #sym:MyFunction" → refs.symbol++

// contentReferences extraction
{
  "kind": "reference",
  "reference": { "name": "MyFunction" }
} → refs.symbol++, refs.byPath['#sym:MyFunction']++

Original prompt

We detect #file already in the example below, detect #sym the same way and show it as a context ref as well in the file viewer.

the debug messages in the diagnostics view, especially when clearing the cache completely clear the output window and then other messages do not show up anymore after. is there a difference between the way we log in the #file:extension.js vs #sym:diagnostics somwhow? define where this comes from, then add a fix, and document it in the #file:copilot-instructions.md for later reference

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.