WIP: capture sharpening

Checkpoint committed by the coordinator, not by the authoring agent: the
session hit its API limit mid-task and left this work uncommitted. Committed
so it survives, NOT because it is finished - expect failing tests and
half-applied changes. The agent resumes from here.

ui/dr-ui/src/labels.rs

@@ -30,6 +30,13 @@ pub fn resolve(key: &str) -> String {
         "op.vibrance" => "Vibrance".into(),
         "op.saturation" => "Saturation".into(),
         "op.colour_mixer" => "Colour Mixer".into(),
+        // "Sharpening" rather than what `derive` would make of the id. The id
+        // says *capture* sharpening to separate it from the output sharpening
+        // an export applies (FR-EXP-4), which is a distinction about where in
+        // the pipeline it sits; in the develop panel there is only one, and
+        // "Capture Sharpen" would name a distinction the photographer cannot
+        // see from there.
+        "op.capture_sharpen" => "Sharpening".into(),
         "op.framing" => "Crop & Rotate".into(),
 
         // Parameters
@@ -121,6 +128,16 @@ mod tests {
     fn catalogued_keys_resolve_to_their_label() {
         assert_eq!(resolve("op.white_balance"), "White Balance");
         assert_eq!(resolve("param.highlights"), "Highlights");
+        // Catalogued precisely because `derive` would get it wrong: the id
+        // carries a distinction ("capture", as against an export's output
+        // sharpening) that belongs in the pipeline and not on a panel.
+        assert_eq!(resolve("op.capture_sharpen"), "Sharpening");
+        // Its parameters are the opposite case — the derived words are the
+        // right words, so they are left uncatalogued and shared with whatever
+        // asks for an amount or a radius next.
+        assert_eq!(resolve("param.amount"), "Amount");
+        assert_eq!(resolve("param.radius"), "Radius");
+        assert_eq!(resolve("param.threshold"), "Threshold");
     }
 
     #[test]