docs: record the operational contract review and what it left open

Nineteen findings across release admission, the provider sandbox, removability,
browser and visual evidence, architecture boundaries and documentation, each
named by defect rather than symptom, with the four removal fixtures' before and
after counts.

Three tests stay red and are recorded as such rather than claimed: the live
process-tree observation of a running sandbox, which now loses a race it used to
win only because the sandbox was slow, and two that time out at their 10s budget
under parallel load while passing in isolation. Lab performance produces
evidence for the first time and that evidence misses its budget; no budget was
moved to hide it.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

tests/unit/supply-chain.test.ts

@@ -14,6 +14,7 @@ import {
   validateLicensePolicy,
 } from "../../scripts/lib/supply-chain.ts";
 import { digestReleaseInputFiles } from "../../scripts/lib/release-input-evidence.ts";
+import { isReducedCiContractRun } from "../../scripts/contracts/ci-gates.ts";
 import { findSecretMatches } from "../../scripts/lib/secret-scan.ts";
 import {
   parseSecretScanIncludedPaths,
@@ -535,7 +536,11 @@ describe("supply-chain policy", () => {
     ]);
   });
 
-  it("covers every mandatory release input in the secret scan policy", async () => {
+  // A removal fixture deletes some of these inputs on purpose — removing the
+  // browser file/storage capability takes the whole browser-capability harness
+  // with it — and prunes them from its own policy. This is a claim about the
+  // full repository, so it does not describe a deliberately reduced one.
+  it.skipIf(isReducedCiContractRun())("covers every mandatory release input in the secret scan policy", async () => {
     const policy = JSON.parse(
       await readFile("config/security/secret-scan-policy.json", "utf8"),
     ) as { trackedRoots: string[] };