From 31db07780f266b51f074e9a7d36d5e9243a58670 Mon Sep 17 00:00:00 2001
From: wassname <1103714+wassname@users.noreply.github.com>
Date: Thu, 17 Sep 2026 10:13:53 +0800
Subject: [PATCH] Classify Nano failure as wrapper regression

Co-Authored-By: PI[gpt-5.6-terra] <288921227+claudypoo@users.noreply.github.com>
---
 ...60917_wvs_gpt5_nano_task_1622_mandatory_reasoning_failure.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/slop/audits/20260917_wvs_gpt5_nano_task_1622_mandatory_reasoning_failure.md b/slop/audits/20260917_wvs_gpt5_nano_task_1622_mandatory_reasoning_failure.md
index 4861c41..083755e 100644
--- a/slop/audits/20260917_wvs_gpt5_nano_task_1622_mandatory_reasoning_failure.md
+++ b/slop/audits/20260917_wvs_gpt5_nano_task_1622_mandatory_reasoning_failure.md
@@ -32,7 +32,7 @@ The priority manifest required the cheapest new model to establish whether a 12
 
 ## Chronology and raw evidence
 
-The saved catalog entry for `openai/gpt-5-nano` includes `reasoning`, `reasoning_effort`, and `structured_outputs` support. The task instead selected the prior optional-reasoning setting. The provider repeatedly returned:
+The saved catalog entry for `openai/gpt-5-nano` includes `reasoning`, `reasoning_effort`, and `structured_outputs` support. The task instead selected the prior optional-reasoning setting. This is a wrapper/config regression, not a newly discovered mandatory-reasoning model-class issue: the ledger's Astra run `20260916T154406Z_95bb4d3939e9` used `reasoning: {"effort": "low"}` and strict schema, completed 144/144 samples with zero rescue starts, and recorded USD 0.69797. The provider repeatedly returned:
 
 > `HTTP error for model openai/gpt-5-nano: {"error":{"message":"Reasoning is mandatory for this endpoint and cannot be disabled.","code":400,...}}`
 >