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
@@ -49,8 +49,8 @@ impl DevelopSession {
    ///
    /// **Measured where the operation acts, not where the photographer
    /// looks.** The white balance node runs first in the chain, on camera
-    /// RGB, before the body's base curve and its matrix; the canvas shows
-    /// the pixel after all three. The probe used to be read off a display
+    /// RGB, before the camera matrix and the view transform; the canvas
+    /// shows the pixel after all three. The probe used to be read off a display
    /// render with the adjustments stripped, and the solve then treated an
    /// sRGB triple as if the gains multiplied it directly. On a JPEG the two
    /// spaces coincide, so it worked; on a raw file from any real body the