@ancplua/qyl-api-schema 0.4.0 → 0.5.1

package/otel/otel-conventions.tsp

@@ -10,5 +10,4 @@ import "./enums.tsp";
 import "./resource.tsp";
 import "./span.tsp";
 import "./logs.tsp";
-import "./metrics.tsp";
 import "./profiles.tsp";

package/otel/profiles.tsp

@@ -1,5 +1,5 @@
 // =============================================================================
-// ANcpLua v2.0 - OpenTelemetry Profiles Model (v1development)
+// OpenTelemetry profiles JSON projection (v1development)
 // =============================================================================
 // Continuous profiling signal following OTel Profiles proto specification.
 // Proto package: opentelemetry.proto.profiles.v1development

package/otel/resource.tsp

@@ -1,5 +1,5 @@
 // =============================================================================
-// ANcpLua v2.0 - OpenTelemetry Resource Model
+// OpenTelemetry resource JSON projection
 // =============================================================================
 // Resource attributes identifying the entity producing telemetry.
 // =============================================================================

package/otel/span.tsp

@@ -1,5 +1,5 @@
 // =============================================================================
-// ANcpLua v2.0 - OpenTelemetry Span Model
+// OpenTelemetry span JSON projection
 // =============================================================================
 // Distributed tracing span representation following OTel specification.
 // =============================================================================
@@ -147,16 +147,13 @@ model SpanLink {
 // Trace Model (Collection of Spans)
 // =============================================================================
 
-@doc("Complete trace containing all related spans")
-model Trace {
+@doc("Trace summary without the full span collection")
+model TraceSummary {
   @doc("Trace identifier")
   @key
   @encodedName("application/json", "trace_id")
   traceId: TraceId;
 
-  @doc("All spans in this trace")
-  spans: Span[];
-
   @doc("Root span of the trace")
   @encodedName("application/json", "root_span")
   rootSpan?: Span;
@@ -185,6 +182,12 @@ model Trace {
   hasError: boolean;
 }
 
+@doc("Complete trace containing all related spans")
+model Trace extends TraceSummary {
+  @doc("All spans in this trace")
+  spans: Span[];
+}
+
 // =============================================================================
 // Span Query Filters
 // =============================================================================

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@ancplua/qyl-api-schema",
-  "version": "0.4.0",
+  "version": "0.5.1",
   "description": "TypeSpec source of truth for qyl API contracts. Emits OpenAPI, JSON Schema, Qyl.Api.Contracts DTOs, and TypeScript contract types; not an OpenTelemetry package, storage schema, or server implementation.",
   "license": "Apache-2.0",
   "repository": {
@@ -19,29 +19,57 @@
     "openapi"
   ],
   "type": "module",
+  "tspMain": "index.tsp",
   "exports": {
-    ".": "./index.tsp",
-    "./otel": "./otel/otel-conventions.tsp",
-    "./models/*": "./models/*.tsp",
-    "./models/agent/*": "./models/agent/*.tsp",
-    "./common/*": "./common/*.tsp",
-    "./api/*": "./api/*.tsp",
-    "./intelligence/*": "./intelligence/*.tsp",
-    "./intelligence/seed/*": "./intelligence/seed/*.tsp",
-    "./generated/otel-keys": "./generated/otel-keys.gen.tsp"
+    ".": {
+      "typespec": "./index.tsp",
+      "default": "./index.tsp"
+    },
+    "./otel": {
+      "typespec": "./otel/otel-conventions.tsp",
+      "default": "./otel/otel-conventions.tsp"
+    },
+    "./generated/otel-keys": {
+      "typespec": "./generated/otel-keys.gen.tsp",
+      "default": "./generated/otel-keys.gen.tsp"
+    },
+    "./types": {
+      "types": "./generated/ts-runtime/api.d.ts",
+      "import": "./generated/ts-runtime/api.js",
+      "default": "./generated/ts-runtime/api.js"
+    },
+    "./openapi": {
+      "default": "./generated/openapi/qyl.openapi.json"
+    },
+    "./json-schema": {
+      "default": "./generated/json-schema/qyl-api-schema.json"
+    }
   },
   "files": [
     "index.tsp",
-    "api/**/*.tsp",
-    "common/**/*.tsp",
-    "intelligence/**/*.tsp",
-    "models/**/*.tsp",
-    "otel/**/*.tsp",
-    "generated/**/*.tsp",
-    "generated/README.md",
-    "tspconfig.yaml",
+    "api/routes.tsp",
+    "api/runner.tsp",
+    "api/streaming.tsp",
+    "common/errors.tsp",
+    "common/pagination.tsp",
+    "common/types.tsp",
+    "models/health.tsp",
+    "models/runner-mcp.tsp",
+    "models/runner.tsp",
+    "models/mcp-tools.tsp",
+    "models/session.tsp",
+    "otel/enums.tsp",
+    "otel/logs.tsp",
+    "otel/otel-conventions.tsp",
+    "otel/profiles.tsp",
+    "otel/resource.tsp",
+    "otel/span.tsp",
+    "generated/otel-keys.gen.tsp",
+    "generated/ts-runtime/api.d.ts",
+    "generated/ts-runtime/api.js",
+    "generated/openapi/qyl.openapi.json",
+    "generated/json-schema/qyl-api-schema.json",
     "README.md",
-    "VERSIONING.md",
     "LICENSE"
   ],
   "publishConfig": {
@@ -50,9 +78,13 @@
     "registry": "https://registry.npmjs.org"
   },
   "scripts": {
-    "build:emitters": "tsc -p emitters/telemetry-control-graph && tsc -p emitters/csharp && tsc -p emitters/ts-types && tsc -p emitters/otelconventions-lint",
+    "clean:generated": "node scripts/clean-generated.mjs",
+    "build:emitters": "tsc -p emitters/csharp && tsc -p emitters/ts-types",
+    "build:ts-runtime": "tsc -p tsconfig.contracts.json",
+    "build:json-schema": "node scripts/openapi-to-json-schema.mjs",
     "prepare": "npm run build:emitters",
-    "compile": "npm run build:emitters && tsp compile main.tsp",
+    "prepack": "npm run compile",
+    "compile": "npm run clean:generated && npm run build:emitters && tsp compile main.tsp && npm run build:json-schema && npm run build:ts-runtime",
     "watch": "tsp compile main.tsp --watch",
     "format": "tsp format **/*.tsp",
     "lint": "npm run build:emitters && tsp compile main.tsp --no-emit --warn-as-error",
@@ -62,31 +94,19 @@
     "@typespec/compiler": "^1.13.0 || >=1.13.0-dev.0",
     "@typespec/events": "^0.83.0",
     "@typespec/http": "^1.13.0",
-    "@typespec/json-schema": "^1.13.0",
     "@typespec/openapi": "^1.13.0",
-    "@typespec/openapi3": "^1.13.0",
-    "@typespec/rest": "^0.83.0",
-    "@typespec/sse": "^0.83.0",
-    "@typespec/streams": "^0.83.0",
-    "@typespec/versioning": "^0.83.0"
+    "@typespec/sse": "^0.83.0"
   },
   "devDependencies": {
     "@ancplua/typespec-emit-csharp": "file:./emitters/csharp",
     "@ancplua/typespec-emit-ts-types": "file:./emitters/ts-types",
-    "@ancplua/typespec-otelconventions-lint": "file:./emitters/otelconventions-lint",
-    "@qyl/telemetry-control-graph": "file:./emitters/telemetry-control-graph",
-    "@types/node": "25.9.4",
+    "@types/node": "25.9.5",
     "@typespec/compiler": "1.13.0",
     "@typespec/events": "0.83.0",
     "@typespec/http": "1.13.0",
-    "@typespec/json-schema": "1.13.0",
     "@typespec/openapi": "1.13.0",
     "@typespec/openapi3": "1.13.0",
-    "@typespec/rest": "0.83.0",
     "@typespec/sse": "0.83.0",
-    "@typespec/streams": "0.83.0",
-    "@typespec/versioning": "0.83.0",
-    "typescript": "6.0.3",
-    "vitest": "4.1.9"
+    "typescript": "6.0.3"
   }
 }

package/VERSIONING.md

@@ -1,88 +0,0 @@
-# TypeSpec Versioning In qyl-api-schema
-
-This repository uses `@typespec/versioning` to record when schema elements were added or removed across qyl API versions and OpenTelemetry compatibility-model pins. The annotations live in TypeSpec so schema evolution is reviewable at the contract source.
-
-## Release versioning (the package version)
-
-Separate from the `@typespec/versioning` schema annotations below: the published **package** version
-(npm `@ancplua/qyl-api-schema` and NuGet `Qyl.Api.Contracts`) is **CI-owned and tag-derived** — no
-hand-bumped version lives in any committed file. To cut a release, publish a GitHub Release whose tag
-is `vMAJOR.MINOR.PATCH[-prerelease]`; `publish.yml` strips the leading `v` and stamps that single
-version onto both npm and NuGet (no build metadata — npm rejects it and NuGet strips it), so the two
-registries are lockstep by construction. The committed `package.json` version is the non-authoritative
-placeholder `0.0.0-development`, and `packaging/Qyl.Api.Contracts.csproj` carries no `<Version>`.
-
-## Where it is used
-
-- `models/genai.tsp` for GenAI semantic-convention shaped models
-- `models/db.tsp` for DB semantic-convention shaped models
-- `models/http.tsp` for HTTP semantic-convention shaped models
-- `api/routes.tsp` for API versioning
-
-## Pattern: version registry + annotations
-
-```tsp
-import "@typespec/versioning";
-using TypeSpec.Versioning;
-
-@versioned(GenAiVersions)
-namespace Qyl.Api.Contracts.Domains.AI.GenAi;
-
-enum GenAiVersions {
-  v1_27: "1.27.0",
-  v1_38: "1.38.0",
-  v1_40: "1.40.0",
-}
-```
-
-Keep version enums **minimal**: only the baseline plus versions actually
-referenced by an `@added`/`@removed` annotation. Unreferenced members are
-dead timeline points that rot (an axis with no annotations at all should
-lose `@versioned` entirely — that happened to `HttpVersions`/`DbVersions`
-in 0.4.0).
-
-```tsp
-
-model GenAiSpanAttributes {
-  @encodedName("application/json", ANcpLua.OpenTelemetry.SemanticConventions.Keys.GenAi.UsageInputTokens)
-  usageInputTokens?: TokenCount;
-
-  @encodedName("application/json", "gen_ai.usage.input_tokens.cached")
-  @added(GenAiVersions.v1_38)
-  usageInputTokensCached?: TokenCount;
-}
-```
-
-Note (v0.3.0): the pre-migration `gen_ai.*` fields that carried upstream-deleted
-wire keys (`gen_ai.system`, `gen_ai.prompt`, `gen_ai.completion`,
-`gen_ai.usage.prompt_tokens` / `.completion_tokens`, and the
-`gen_ai.openai.*` vendor keys) were **removed from the contract surface**
-when the OTel 1.42 GenAI-registry split was adopted. Old-key telemetry is a
-collector *ingestion normalization* concern (mapping below), not a contract
-field.
-
-## Ingestion mapping (deprecated -> current)
-
-Consumers can keep ingestion backward-compatible by normalizing deprecated attribute keys. Keep any downstream mapping aligned with the TypeSpec history.
-
-```csharp
-public static readonly FrozenDictionary<string, string> DeprecatedMappings =
-    new Dictionary<string, string>(StringComparer.Ordinal)
-    {
-        ["gen_ai.system"] = "gen_ai.provider.name",
-        ["gen_ai.usage.prompt_tokens"] = "gen_ai.usage.input_tokens",
-        ["gen_ai.usage.completion_tokens"] = "gen_ai.usage.output_tokens",
-        ["agents.tool.call_id"] = "gen_ai.tool.call.id",
-        ["db.system"] = "db.system.name"
-    }.ToFrozenDictionary(StringComparer.Ordinal);
-```
-
-Downstream consumers should cover these mappings in ingestion tests.
-
-## Workflow for schema evolution
-
-- Add a new version entry to the enum in the owning namespace.
-- Mark additions and removals with `@added` and `@removed`.
-- Update downstream normalization mappings to keep ingestion compatibility.
-- Extend downstream ingestion tests to cover the new mapping.
-- Run `npm run compile` after TypeSpec changes.

package/generated/README.md

@@ -1,35 +0,0 @@
-# generated
-
-This directory holds the semconv TypeSpec key projection and the emitter
-outputs. `otel-keys.gen.tsp` is Weaver-generated — **do not edit by hand**.
-
-## Files
-
-| File | Source | Regenerate via |
-| --- | --- | --- |
-| `otel-keys.gen.tsp` | OpenTelemetry semantic-conventions core **v1.43.0** + the GenAI dev registry (`open-telemetry/semantic-conventions-genai`, pinned commit), merged and projected by the `Qyl.OpenTelemetry.SemanticConventions` repo's Weaver pipeline | In that repo: `src/…SourceGeneration/scripts/generate.sh` (refresh `Resources/resolved-registry.json`), then `src/…SourceGeneration/scripts/emit_typespec_keys.py --write <path-to-this-file>` |
-
-## What the key files provide
-
-One TypeSpec namespace per OpenTelemetry root group, each declaring `const <Name>: string = "<dotted.key>"`. Extracted `.tsp` models reference these consts inside `@encodedName(...)` instead of hand-typing dotted attribute keys.
-
-```tsp
-@encodedName("application/json", ANcpLua.OpenTelemetry.SemanticConventions.Keys.GenAi.ProviderName)
-providerName?: string;
-```
-
-Deprecated upstream attributes are emitted with `#deprecated "..."` so models that reference them produce a TypeSpec compiler warning matching upstream's own deprecation notes.
-
-## Pin
-
-The checked-in projection is pinned to core semantic-conventions **v1.43.0**
-(commit in the file header) plus the GenAI dev registry commit pinned in the
-SemanticConventions repo's `generate.sh` (`SEMCONV_GENAI_REF`). The
-`VerifyKeysLockstep` Nuke target asserts the header pin matches the
-`OtelKeysVersion` parameter (`.nuke/parameters.json`).
-
-Bumping the pin: update the refs in that repo's `generate.sh`, re-run it plus
-`emit_typespec_keys.py --write`, replace this checked-in projection, and keep
-`SemConvSchemaVersion` in that repo's `Version.props` in lockstep — the .NET
-constants and this TypeSpec projection must cite the same registry versions.
-Direction is one-way: this repo never invokes Weaver directly.

package/intelligence/causal-rules.tsp

@@ -1,34 +0,0 @@
-// =============================================================================
-// ANcpLua v2.0 - Causal Rules
-// =============================================================================
-// Directed relationship between two diagnostic patterns: if cause is observed,
-// effect is likely. Causal rules build a directed graph. Given matched patterns,
-// the engine traverses causal edges to identify root causes (patterns with no
-// incoming causal edges).
-// =============================================================================
-
-import "@typespec/openapi";
-
-using TypeSpec.OpenAPI;
-
-namespace Qyl.Api.Contracts.Intelligence;
-
-@doc("Directed causal relationship between two diagnostic patterns")
-model CausalRule {
-  @doc("Unique rule identifier")
-  id: string;
-
-  @doc("ID of the cause DiagnosticPattern")
-  causePattern: string;
-
-  @doc("ID of the effect DiagnosticPattern")
-  effectPattern: string;
-
-  @doc("Causal confidence (0.0-1.0)")
-  @minValue(0.0)
-  @maxValue(1.0)
-  strength: float64;
-
-  @doc("Time window for correlation (e.g. 5m, 1h)")
-  temporalWindow?: string;
-}

package/intelligence/diagnostic-patterns.tsp

@@ -1,54 +0,0 @@
-// =============================================================================
-// ANcpLua v2.0 - Diagnostic Patterns
-// =============================================================================
-// A named combination of signals that identifies a known failure mode.
-// All signals in a pattern must match (conjunction). Multiple patterns can
-// match the same telemetry — the engine returns all matches ranked by confidence.
-// =============================================================================
-
-import "@typespec/openapi";
-
-using TypeSpec.OpenAPI;
-
-namespace Qyl.Api.Contracts.Intelligence;
-
-@doc("Classification category for diagnostic patterns")
-enum PatternCategory {
-  @doc("Exception and error patterns")
-  error: "error",
-
-  @doc("Performance degradation")
-  latency: "latency",
-
-  @doc("Token/cost anomalies")
-  cost: "cost",
-
-  @doc("Service health patterns")
-  availability: "availability",
-
-  @doc("GenAI-specific failure modes")
-  genai: "genai",
-
-  @doc("Database and storage patterns")
-  data: "data",
-}
-
-@doc("Named combination of signals identifying a known failure mode")
-model DiagnosticPattern {
-  @doc("Unique pattern identifier (e.g. genai_rate_limit)")
-  id: string;
-
-  @doc("Pattern classification")
-  category: PatternCategory;
-
-  @doc("Signals that must all match (conjunction)")
-  signals: Signal[];
-
-  @doc("What this pattern means diagnostically")
-  hypothesis: string;
-
-  @doc("Base confidence weight (0.0-1.0)")
-  @minValue(0.0)
-  @maxValue(1.0)
-  confidence: float64;
-}

package/intelligence/investigation-strategies.tsp

@@ -1,37 +0,0 @@
-// =============================================================================
-// ANcpLua v2.0 - Investigation Strategies
-// =============================================================================
-// A deterministic sequence of steps to investigate a matched pattern.
-// The LLM does not invent investigation paths — it selects from known
-// strategies and interprets results.
-// =============================================================================
-
-import "@typespec/openapi";
-
-using TypeSpec.OpenAPI;
-
-namespace Qyl.Api.Contracts.Intelligence;
-
-@doc("Single step in an investigation strategy")
-model InvestigationStep {
-  @doc("What to do (e.g. query_traces, get_code_location, compare_deployments)")
-  action: string;
-
-  @doc("Query template or tool name")
-  query: string;
-
-  @doc("Human-readable explanation of this step")
-  description: string;
-}
-
-@doc("Deterministic investigation sequence triggered by a matched pattern")
-model InvestigationStrategy {
-  @doc("Unique strategy identifier")
-  id: string;
-
-  @doc("Trigger — pattern ID or category:X for category-wide triggers")
-  triggerPattern: string;
-
-  @doc("Ordered investigation steps")
-  steps: InvestigationStep[];
-}

package/intelligence/main.tsp

@@ -1,17 +0,0 @@
-// =============================================================================
-// ANcpLua v2.0 - Telemetry Intelligence Model
-// =============================================================================
-// Canonical reasoning model over telemetry data. Schema-driven, generated,
-// deterministic. Defines diagnostic patterns, causal rules, and investigation
-// strategies as typed data consumed by Loom, MCP, and dashboard.
-// =============================================================================
-
-import "@typespec/openapi";
-
-import "./signals.tsp";
-import "./diagnostic-patterns.tsp";
-import "./causal-rules.tsp";
-import "./investigation-strategies.tsp";
-import "./seed/patterns.tsp";
-import "./seed/rules.tsp";
-import "./seed/strategies.tsp";

package/intelligence/seed/patterns.tsp

@@ -1,171 +0,0 @@
-// =============================================================================
-// ANcpLua v2.0 - Seed Diagnostic Patterns (v1)
-// =============================================================================
-// 19 initial diagnostic patterns (10 infra + 9 agent behavioral)
-// Source: Microsoft Research AgentRx (March 2026)
-//
-// Signal attributes reference:
-//   - OTel semantic attributes (status_code, duration_ns, etc.)
-//   - qyl-derived attributes (gen_ai_provider_name, gen_ai_stop_reason, etc.)
-//   - Computed fields (occurrence_rate, span_count_under_parent, etc.)
-// =============================================================================
-
-namespace Qyl.Api.Contracts.Intelligence.Seed;
-
-// ---------------------------------------------------------------------------
-// Pattern: genai_rate_limit
-// Category: genai
-// Signals: status_code=2, gen_ai_provider_name exists, error_type contains rate_limit
-// Hypothesis: Provider throttling. Check quota, reduce concurrency, add backoff.
-// Confidence: 0.9
-// ---------------------------------------------------------------------------
-
-// ---------------------------------------------------------------------------
-// Pattern: genai_token_exhaustion
-// Category: genai
-// Signals: gen_ai_stop_reason=length
-// Hypothesis: Context window exceeded. Reduce prompt size or switch to larger model.
-// Confidence: 0.85
-// ---------------------------------------------------------------------------
-
-// ---------------------------------------------------------------------------
-// Pattern: genai_content_filter
-// Category: genai
-// Signals: gen_ai_stop_reason contains content_filter
-// Hypothesis: Content policy violation. Review prompt content.
-// Confidence: 0.95
-// ---------------------------------------------------------------------------
-
-// ---------------------------------------------------------------------------
-// Pattern: db_timeout
-// Category: data
-// Signals: exception_type=TimeoutException, db.system.name exists, duration_ns > 2000000000
-// Hypothesis: Database query timeout. Check query plan, connection pool, lock contention.
-// Confidence: 0.85
-// ---------------------------------------------------------------------------
-
-// ---------------------------------------------------------------------------
-// Pattern: db_n_plus_one
-// Category: data
-// Signals: db.system.name exists, parent_span_id exists, span_count_under_parent > 10
-// Hypothesis: N+1 query pattern. Batch or prefetch related data.
-// Confidence: 0.80
-// ---------------------------------------------------------------------------
-
-// ---------------------------------------------------------------------------
-// Pattern: http_5xx_cluster
-// Category: error
-// Signals: http.response.status_code gte 500, occurrence_rate > baseline * 3
-// Hypothesis: Server error spike. Check recent deployments and upstream dependencies.
-// Confidence: 0.75
-// ---------------------------------------------------------------------------
-
-// ---------------------------------------------------------------------------
-// Pattern: deployment_regression
-// Category: error
-// Signals: error_type exists, first_seen_at > last_deployment_time
-// Hypothesis: New error class after deployment. Compare with previous version.
-// Confidence: 0.80
-// ---------------------------------------------------------------------------
-
-// ---------------------------------------------------------------------------
-// Pattern: cascading_timeout
-// Category: latency
-// Signals: exception_type contains Timeout, downstream_service_error=true
-// Hypothesis: Upstream failure causing downstream timeouts. Investigate root service first.
-// Confidence: 0.70
-// ---------------------------------------------------------------------------
-
-// ---------------------------------------------------------------------------
-// Pattern: memory_pressure_latency
-// Category: latency
-// Signals: process.runtime.dotnet.gc.duration gt 100, avg_latency > p99_baseline
-// Hypothesis: GC pressure causing latency. Check memory allocation patterns.
-// Confidence: 0.65
-// ---------------------------------------------------------------------------
-
-// ---------------------------------------------------------------------------
-// Pattern: cost_spike
-// Category: cost
-// Signals: gen_ai_cost_usd > daily_average * 3
-// Hypothesis: Abnormal cost increase. Identify the model, service, and session responsible.
-// Confidence: 0.75
-// ---------------------------------------------------------------------------
-
-// =============================================================================
-// Agent behavioral failure patterns (AgentRx taxonomy)
-// Source: Microsoft Research AgentRx, March 2026
-// 9 failure categories from Magentic-One and TAU-Retail benchmarks
-// =============================================================================
-
-// ---------------------------------------------------------------------------
-// Pattern: agent_intent_plan_misalignment
-// Category: agent
-// Signals: gen_ai.agent.name exists, gen_ai.operation.name=invoke_agent, status_code=2
-// Hypothesis: Agent plan diverges from user intent. Review task decomposition.
-// Confidence: 0.70
-// ---------------------------------------------------------------------------
-
-// ---------------------------------------------------------------------------
-// Pattern: agent_misinterpret_tool_info
-// Category: agent
-// Signals: gen_ai.tool.name exists, gen_ai.tool.call.id exists, error_type contains tool
-// Hypothesis: Agent misinterpreted tool output or schema.
-// Confidence: 0.75
-// ---------------------------------------------------------------------------
-
-// ---------------------------------------------------------------------------
-// Pattern: agent_rai_policy_violation
-// Category: agent
-// Signals: gen_ai.agent.name exists, gen_ai.stop_reason contains content_filter
-// Hypothesis: Agent triggered responsible AI policy violation.
-// Confidence: 0.95
-// ---------------------------------------------------------------------------
-
-// ---------------------------------------------------------------------------
-// Pattern: agent_plan_adherence_failure
-// Category: agent
-// Signals: gen_ai.agent.name exists, gen_ai.operation.name=invoke_agent, gen_ai.usage.output_tokens>0, child_span_count>20
-// Hypothesis: Agent deviated from its own plan. Excessive tool calls suggest improvisation.
-// Confidence: 0.65
-// ---------------------------------------------------------------------------
-
-// ---------------------------------------------------------------------------
-// Pattern: agent_invent_new_info
-// Category: agent
-// Signals: gen_ai.agent.name exists, gen_ai.operation.name=invoke_agent
-// Hypothesis: Agent fabricated information not in tool outputs. Cross-reference claims vs results.
-// Confidence: 0.60
-// ---------------------------------------------------------------------------
-
-// ---------------------------------------------------------------------------
-// Pattern: agent_invalid_invocation
-// Category: agent
-// Signals: gen_ai.tool.name exists, error_type contains invalid, gen_ai.agent.name exists
-// Hypothesis: Agent called tool with invalid arguments or nonexistent name.
-// Confidence: 0.85
-// ---------------------------------------------------------------------------
-
-// ---------------------------------------------------------------------------
-// Pattern: agent_hallucination_doubt
-// Category: agent
-// Signals: gen_ai.agent.name exists, gen_ai.usage.output_tokens>500, gen_ai.tool.call.id not_exists
-// Hypothesis: Long response without tool grounding. High hallucination risk.
-// Confidence: 0.55
-// ---------------------------------------------------------------------------
-
-// ---------------------------------------------------------------------------
-// Pattern: agent_instruction_adherence_failure
-// Category: agent
-// Signals: gen_ai.agent.name exists, gen_ai.operation.name=invoke_agent
-// Hypothesis: Agent ignored or contradicted system prompt constraints.
-// Confidence: 0.60
-// ---------------------------------------------------------------------------
-
-// ---------------------------------------------------------------------------
-// Pattern: agent_underspecified_intent
-// Category: agent
-// Signals: gen_ai.agent.name exists, gen_ai.operation.name=invoke_agent, gen_ai.usage.input_tokens<50
-// Hypothesis: Ambiguous request with insufficient context for reliable execution.
-// Confidence: 0.65
-// ---------------------------------------------------------------------------