Add call graph fixtures for various languages and scenarios

- Introduced `all-edge-reasons.json` to test edge resolution reasons in .NET.
- Added `all-visibility-levels.json` to validate method visibility levels in .NET.
- Created `dotnet-aspnetcore-minimal.json` for a minimal ASP.NET Core application.
- Included `go-gin-api.json` for a Go Gin API application structure.
- Added `java-spring-boot.json` for the Spring PetClinic application in Java.
- Introduced `legacy-no-schema.json` for legacy application structure without schema.
- Created `node-express-api.json` for an Express.js API application structure.

docs/benchmarks/scanner-feature-comparison-grype.md

@@ -2,6 +2,24 @@
 
 _Reference snapshot: Grype commit `6e746a546ecca3e2456316551673357e4a166d77` cloned 2025-11-02._
 
+## Verification Metadata
+
+| Field | Value |
+|-------|-------|
+| **Last Updated** | 2025-12-15 |
+| **Last Verified** | 2025-12-14 |
+| **Next Review** | 2026-03-14 |
+| **Claims Index** | [`docs/market/claims-citation-index.md`](../market/claims-citation-index.md) |
+| **Claim IDs** | COMP-GRYPE-001, COMP-GRYPE-002, COMP-GRYPE-003 |
+| **Verification Method** | Source code audit (OSS), documentation review, feature testing |
+
+**Confidence Levels:**
+- **High (80-100%)**: Verified against source code or authoritative documentation
+- **Medium (50-80%)**: Based on documentation or limited testing; needs deeper verification
+- **Low (<50%)**: Unverified or based on indirect evidence; requires validation
+
+---
+
 ## TL;DR
 - StellaOps runs as a multi-service platform with deterministic SBOM generation, attestation (DSSE + Rekor), and tenant-aware controls, whereas Grype is a single Go CLI that leans on Syft to build SBOMs before vulnerability matching.[1](#sources)[g1](#grype-sources)
 - Grype covers a broad OS and language matrix via Syft catalogers and Anchore’s aggregated vulnerability database, but it lacks attestation, runtime usage context, and secret management features found in StellaOps’ Surface/Policy ecosystem.[1](#sources)[g2](#grype-sources)[g3](#grype-sources)

docs/benchmarks/scanner-feature-comparison-snyk.md

@@ -2,6 +2,24 @@
 
 _Reference snapshot: Snyk CLI commit `7ae3b11642d143b588016d4daef0a6ddaddb792b` cloned 2025-11-02._
 
+## Verification Metadata
+
+| Field | Value |
+|-------|-------|
+| **Last Updated** | 2025-12-15 |
+| **Last Verified** | 2025-12-14 |
+| **Next Review** | 2026-03-14 |
+| **Claims Index** | [`docs/market/claims-citation-index.md`](../market/claims-citation-index.md) |
+| **Claim IDs** | COMP-SNYK-001, COMP-SNYK-002, COMP-SNYK-003 |
+| **Verification Method** | Source code audit (OSS), documentation review, feature testing |
+
+**Confidence Levels:**
+- **High (80-100%)**: Verified against source code or authoritative documentation
+- **Medium (50-80%)**: Based on documentation or limited testing; needs deeper verification
+- **Low (<50%)**: Unverified or based on indirect evidence; requires validation
+
+---
+
 ## TL;DR
 - StellaOps delivers a self-hosted, multi-service scanning plane with deterministic SBOMs, attestation (DSSE + Rekor), and tenant-aware Surface controls, while the Snyk CLI is a Node.js tool that authenticates against Snyk’s SaaS to analyse dependency graphs, containers, IaC, and code.[1](#sources)[s1](#snyk-sources)
 - Snyk’s plugin ecosystem covers many package managers (npm, yarn, pnpm, Maven, Gradle, NuGet, Go modules, Composer, etc.) and routes scans through Snyk’s cloud for policy, reporting, and fix advice; however it lacks offline operation, deterministic evidence, and attestation workflows that StellaOps provides out of the box.[1](#sources)[s1](#snyk-sources)[s2](#snyk-sources)

docs/benchmarks/scanner-feature-comparison-trivy.md

@@ -2,6 +2,24 @@
 
 _Reference snapshot: Trivy commit `012f3d75359e019df1eb2602460146d43cb59715`, cloned 2025-11-02._
 
+## Verification Metadata
+
+| Field | Value |
+|-------|-------|
+| **Last Updated** | 2025-12-15 |
+| **Last Verified** | 2025-12-14 |
+| **Next Review** | 2026-03-14 |
+| **Claims Index** | [`docs/market/claims-citation-index.md`](../market/claims-citation-index.md) |
+| **Claim IDs** | COMP-TRIVY-001, COMP-TRIVY-002, COMP-TRIVY-003 |
+| **Verification Method** | Source code audit (OSS), documentation review, feature testing |
+
+**Confidence Levels:**
+- **High (80-100%)**: Verified against source code or authoritative documentation
+- **Medium (50-80%)**: Based on documentation or limited testing; needs deeper verification
+- **Low (<50%)**: Unverified or based on indirect evidence; requires validation
+
+---
+
 ## TL;DR
 - StellaOps Scanner stays focused on deterministic, tenant-scoped SBOM production with signed evidence, policy hand-offs, and Surface primitives that keep offline deployments first-class.[1](#sources)
 - Trivy delivers broad, single-binary coverage (images, filesystems, repos, VMs, Kubernetes, SBOM input) with multiple scanners (vuln, misconfig, secret, license) and a rich plugin ecosystem, but it leaves provenance, signing, and multi-tenant controls to downstream tooling.[8](#sources)