@giveitsmaller/contracts 0.60.0 → 0.62.0

package/operation-capabilities/operation-capabilities.json

@@ -732,5 +732,5 @@
       "isAnimated": "maybe"
     }
   },
-  "schema_version": "2.188.0"
+  "schema_version": "2.191.0"
 }

package/operations/schemas/render_variants.yaml

@@ -20,9 +20,34 @@ operation:
   # Both halves were measured FALSE on 2026-07-28: the Lambda is deployed
   # (`gisl-stg-euw1-operation-render-variants`, image git-fe33902) and its event
   # source mapping has been `Enabled` on the queue since 2026-06-09. What is
-  # true is that it has never run — zero log streams, against a positive control
-  # showing non-zero for merge / compression-image / video-text-watermark in the
-  # same query. DEPLOYED and WIRED are not PROVEN, so this stays `planned`.
+  # true is that it has never run: lambdas measured CloudWatch `Invocations` for
+  # `gisl-stg-euw1-operation-render-variants` over a SIX-MONTH window on
+  # 2026-08-11 and got an EMPTY datapoint set — not a small number, zero, ever.
+  # DEPLOYED and WIRED are not PROVEN, so this stays `planned`.
+  #
+  # PROBE NOTE: that measurement supersedes the earlier "zero log streams"
+  # evidence this comment used to cite. `describe-log-streams` is NOT a valid
+  # activity probe and the fleet has been burned treating it as one; CloudWatch
+  # `Invocations` over a long window IS. Cite the metric, not the log group.
+  #
+  # AND THE UPGRADE DIRECTION IS GATED TOO. Standing policies 3 and 4 block a
+  # DOWNGRADE on absent evidence; they say nothing about an UPGRADE, and
+  # never-exercised is not a licence to flip TO `stable` either. This is the
+  # MIRROR IMAGE of the SVG case, not the same case: in both directions the
+  # honest answer to "we have never run it" is go and get the evidence. Flipping
+  # this to `stable` during a launch availability sweep would advertise to
+  # customers a worker that has never once executed. Hub ruling 2026-08-11; also
+  # on the launch checklist, because hub decision 12's "flips are safe while prod
+  # serves zero customers" protection EXPIRES WITH THE LAUNCH DATE — which is
+  # precisely when a launch sweep would touch this line. Deliberately not naming
+  # the date here: it moved THREE TIMES IN ONE DAY on 2026-08-11 and a date baked
+  # into prose rots into a false claim. Read it off the launch checklist.
+  #
+  # Deliberately citing no hub decision NUMBER either. The decision that moved
+  # the date was itself superseded within hours, and on 2026-08-12 the hub found
+  # five records reading as live that had been superseded — the supersession was
+  # written in the prose and never in the field. A record id is as perishable as
+  # the date it carries; cite the CHECKLIST, which is maintained.
   #
   # Deliberately restated as the GATE being waited on rather than a snapshot of
   # another repo's infrastructure: a gate cannot rot, a restated snapshot does —

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@giveitsmaller/contracts",
-  "version": "0.60.0",
+  "version": "0.62.0",
   "description": "Generated contract types for GISL (Give It Smaller)",
   "license": "Apache-2.0",
   "type": "module",