From 3d8c492baf53ba9fdca9a55a3e851f68b0863098 Mon Sep 17 00:00:00 2001
From: Teknium <127238744+teknium1@users.noreply.github.com>
Date: Mon, 7 Sep 2026 03:57:50 -0700
Subject: [PATCH] docs: record native output-cap save validation

---
 evals/output_caps_scope.md | 10 +++++++---
 1 file changed, 7 insertions(+), 3 deletions(-)

diff --git a/evals/output_caps_scope.md b/evals/output_caps_scope.md
index 1e6f39b15d..c337bec8cc 100644
--- a/evals/output_caps_scope.md
+++ b/evals/output_caps_scope.md
@@ -63,6 +63,10 @@ Preserved:
 | Explicit internal task budget | 43 | 43 |
 
 The initial capture also covers real gateway/API/custom-provider resolvers and
-the registered custom provider profile. It does not prove remote provider
-behavior, billing, a native Desktop interaction, or curator/review scheduling.
-Those surfaces must be validated separately rather than inferred from builders.
+the registered custom provider profile, completed curator and review forks, and
+a review fork preserving an explicit internal budget of 43. Scheduling itself
+is not exercised. Separate native Electron A/B opened Model settings against
+isolated real backends and toggled the fixture MoA preset: both saved `enabled:
+false`; baseline retained preset caps 29/31 while fixed removed them. Desktop
+and dashboard TypeScript checks and the production Desktop build also passed.
+No local fixture proves remote provider behavior or billing.