Stop describing a base curve the pipeline no longer has

D19 retired the per-body base curve, moved the matrix ahead of the edits and the film into the view transform's place, but a dozen doc comments still listed the curve among what a pixel passes through, or said the film skipped it. The detail stage's module doc still drew the matrix after the edits and the last detail pass encoding, which the view pass took over. The film crate's README gave the base curves as its reason for being data, and the ops README's list of hand-written nodes had neither the view transform nor three of the five kernels. FR-MRG-2 gave the base curve as why the merge cuts below the profile; the view transform is why now. The decision table still said colour defaults were a per-body curve, and FR-DEV-3j said only the default view transform skips a JPEG, where the node skips one whatever its sliders say. frame-budget.md records the view pass as unmeasured.
2026-09-27 19:42:41 -04:00
parent 31bcc3a462
commit affdaecaee
19 changed files with 107 additions and 61 deletions
@@ -518,7 +518,7 @@ pub enum OutputMode {
    ///
    /// What a merge stitches (FR-MRG-2). The shader is the linear tail with
    /// no operations, and the caller fills the reserved uniforms neutral —
-    /// unit white balance, identity matrix, base curve off — so what is
+    /// unit white balance, identity matrix, no view transform — so what is
    /// stored is the sensor's own numbers, demosaiced and undistorted. Only
    /// [`compose_camera_probe`] produces it — for a merge through
    /// [`compose_camera_linear`], and for the white balance picker under the