cige-product-defect-escalationlisted

# CIGE: ProductDefectAgent Invoked by `cige-failure-classification` when a run is classified as a **Product Defect**: execution reached the system under test, the environment is healthy, execution steps are current — but the outcome does not match `Intent`. ## When to invoke - Execution reached the system under test - Environment is healthy (ruled out by `cige-failure-classification` as Infrastructure Failure) - Execution steps are current (ruled out as Outdated Test Logic) - The observed outcome contradicts `Intent` This is also the escalation target when `cige-stale-execution-repair` (Mode A) cannot find any execution path that satisfies `Intent` within `Guardrails` — that usually means the failure was misclassified as stale execution when it's really a defect. --- ## What it does 1. Read `Intent` (what was expected) and capture actual system behavior (what happened). 2. Fetch `specRef` (the BRD / product spec) and `buildRef` (the tested build's release documentation) to determine ground truth. Four cases: **Case A — `specRef` unchanged, system diverged.** The system broke. This is a confirmed product defect. → File a bug report with: Intent, actual behavior, `specRef` snapshot, execution trace. → Do not modify the test definition. **Case B — `specRef` was recently updated, `buildRef`'s release documentation confirms the tested build actually includes that update, and system behavior matches the new spec.** The product intentionally changed, *and this build actuall