feat(electron): report custom URL protocol registrations

Expose static Electron protocol call facts through the shared application graph and existing CLI/MCP Evidence views. Preserve canonical case-insensitive scheme identity, original spellings, exact source provenance and explicit unknowns; keep registration success and runtime routing unproven.

Integration fixes also enforce module-only privileged API ownership, reuse the shared finding-key owner, and align the owning type documentation with the Evidence semantics. Validation and bounded real Obsidian CLI/MCP measurements are recorded in the PR.

Co-authored-by: UnknownHacker1 <35694178+UnknownHacker1@users.noreply.github.com>
Co-authored-by: gensokyo-dev <342580529+gensokyo-dev@users.noreply.github.com>

src/domain/javascript/javascriptFeatureTrace.ts

@@ -282,9 +282,14 @@ const pathTo = (
 };
 
 const isTerminal = (node: ApplicationNode): boolean =>
-  ["endpoint", "storage", "native-addon", "native-export", "unknown"].includes(
-    node.kind,
-  ) ||
+  [
+    "endpoint",
+    "storage",
+    "url-scheme",
+    "native-addon",
+    "native-export",
+    "unknown",
+  ].includes(node.kind) ||
   (node.kind === "javascript-expression" &&
     node.observations.some((o) => o.properties.step_kind === "terminal"));