Camera white balance: implemented on both platforms, matrix row active

iOS implemented the white_balance and white_balance_tint entries of the
camera input's locked attribute on 2026-10-01 (phyphox-ios 0ebe2fa7),
following Android the same day, so the planned wording goes: the locked
note in spec/input.yml, the next.md paragraph (which also still mentioned
the dropped reference marks), the fixture comments, and the
camera-white-balance row, now tagged in both app test suites.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>

Author: Staacks

corpus/generated/camera-white-balance-lock.phyphox

@@ -1,10 +1,9 @@
 <phyphox xmlns="http://phyphox.org/xml" version="1.21" locale="en">
     <!-- Generated fixture: the value-less white_balance entry, which freezes the automatic white balance at the first start in the camera input's locked attribute
-         (file format 1.21, planned - see spec/input.yml, camera/locked, and
-         docs/file-format/input.md "White balance"). Both apps ignore unknown
-         locked entries, so this file loads before the feature exists; the
-         behaviour is the matrix row camera-white-balance. A parsing fixture,
-         not a maintained experiment. -->
+         (file format 1.21 - see spec/input.yml, camera/locked, and
+         docs/file-format/input.md "White balance"). The behaviour is the matrix
+         row camera-white-balance. A parsing fixture, not a maintained
+         experiment. -->
     <title>Corpus: camera white balance lock</title>
     <category>Corpus</category>
     <description>Generated coverage fixture for the value-less white_balance entry, which freezes the automatic white balance at the first start.</description>

corpus/generated/camera-white-balance-temperature.phyphox

@@ -1,10 +1,9 @@
 <phyphox xmlns="http://phyphox.org/xml" version="1.21" locale="en">
     <!-- Generated fixture: a white balance set by colour temperature in Kelvin and a tint as Duv in the camera input's locked attribute
-         (file format 1.21, planned - see spec/input.yml, camera/locked, and
-         docs/file-format/input.md "White balance"). Both apps ignore unknown
-         locked entries, so this file loads before the feature exists; the
-         behaviour is the matrix row camera-white-balance. A parsing fixture,
-         not a maintained experiment. -->
+         (file format 1.21 - see spec/input.yml, camera/locked, and
+         docs/file-format/input.md "White balance"). The behaviour is the matrix
+         row camera-white-balance. A parsing fixture, not a maintained
+         experiment. -->
     <title>Corpus: camera white balance temperature</title>
     <category>Corpus</category>
     <description>Generated coverage fixture for a white balance set by colour temperature in Kelvin and a tint as Duv.</description>

docs/reference/version-history/next.md

@@ -79,17 +79,16 @@ same day on both platforms:
   channels carry a spectrum each, paired with *pixelPosition* like *luminance* (see
   [Colour channels](../../file-format/input.md#colour-channels)).
 
-Specified 2026-10-01 ahead of the implementations (marked *planned* in the reference until both
-apps ship it):
+Specified 2026-10-01 ahead of the implementations and implemented from that specification the
+same day on both platforms:
 
 - **White balance in the camera's *locked* attribute:** `white_balance` alone freezes the
   automatic white balance when the measurement is first started; `white_balance=5600` balances
   for a correlated colour temperature in Kelvin; `white_balance_tint` shifts the white point off
   the Planckian locus as Duv. The format knows no named presets - the phones' presets are only
   approximations that differ per device. The camera-gui's preset picker becomes a control with
-  the same three choices, automatic, locked, or a temperature scale with tint, carrying the old
-  preset names as reference marks (see
-  [White balance](../../file-format/input.md#white-balance)).
+  the same three choices, automatic, locked, or a temperature scale with tint, and no named
+  presets (see [White balance](../../file-format/input.md#white-balance)).
 
 ## Changes on Android and iOS
 

spec/input.yml

@@ -909,9 +909,8 @@ elements:
           but they parse it in different places - iOS in the handler, Android
           further downstream. Worth a conformance test rather than trust.
           The white_balance and white_balance_tint entries were specified
-          2026-10-01 ahead of the implementations (planned; both apps ignore
-          unknown entry names, so files carrying them load today and the
-          entries simply have no effect until the apps follow). Implementation
+          2026-10-01 ahead of the implementations and implemented from that
+          specification the same day on both platforms. Implementation
           guidance, not contract: iOS converts temperature and Duv to a CIE xy
           white point and asks AVCaptureDevice for the matching gains, clamped
           to maxWhiteBalanceGain. Android uses the CCT colour-correction mode

test-matrix.yml

@@ -889,19 +889,18 @@ tests:
       exact value per pixel and a ramp across it as a flat spectrum, in
       both orientations, with the exposure factor applied.
 
-  # --- camera white balance (file format 1.21, specified 2026-10-01, planned) --
+  # --- camera white balance (file format 1.21, specified 2026-10-01) --
   # spec/input.yml (camera locked: white_balance, white_balance_tint) and
   # docs/file-format/input.md "White balance" are the design. Parsing is
   # covered by corpus-valid-load through corpus/generated/camera-white-
-  # balance-lock.phyphox and camera-white-balance-temperature.phyphox, but
-  # both apps ignore unknown locked entries, so those files load before the
-  # feature exists; this row carries the behaviour.
+  # balance-lock.phyphox and camera-white-balance-temperature.phyphox; this
+  # row carries the behaviour.
 
   - id: camera-white-balance
     area: file-format
     tier: T1
     platforms: [android, ios]
-    status: planned
+    status: active
     description: >-
       With locked="white_balance=T" and a neutral target lit by a source of
       colour temperature T, linearRed, linearGreen and linearBlue agree