developer_measure: the promote reads Attribute Name

The promote to detail read a hard-coded "volume", so any other
Attribute Name measured on primitives produced nothing at the detail
level and the primitive attribute was still deleted. It now reads the
Attribute Name, and a switch keeps a point measurement as is instead
of running a primitive promote that finds nothing. Help corrected: the
promotion is to the detail, not to points, and with Accumulate at
Throughout the detail value is the total. Same version.

Co-Authored-By: Claude Fable 5.1 <[email protected]>

 developer.md                                   |   2 +-
 otls/sop_lsgalante.developer_measure.1.0.hdalc | Bin 22644 -> 23215 bytes
 2 files changed, 1 insertion(+), 1 deletion(-)

diff --git a/developer.md b/developer.md
index 3e769f3..b9824ac 100644
--- a/developer.md
+++ b/developer.md
@@ -84,7 +84,7 @@ Names are the tab-menu labels without the "Developer" prefix; the file in `otls/
 - Gradient (Vector From Scalar): a unit vector along the slope of a scalar attribute, uphill or downhill, optionally along the surface and twisted about the normal.
 - ID
 - Lead
-- Measure
+- Measure: the Measure SOP; a primitive measurement is promoted to a detail attribute under the chosen name.
 - Metamax
 - Migrate 1.2 (Scalar Migrate, Vector Migrate): pushes an attribute's values along a per-point direction vector, by proximity or connectivity; the sender loses what the target gains.
 - Normalize (Scalar Normalize, Vector Normalize): rescales a float attribute so its values sum to a target, or makes a vector attribute unit length.
diff --git a/otls/sop_lsgalante.developer_measure.1.0.hdalc b/otls/sop_lsgalante.developer_measure.1.0.hdalc
index 716cf19..8188f75 100755
Binary files a/otls/sop_lsgalante.developer_measure.1.0.hdalc and b/otls/sop_lsgalante.developer_measure.1.0.hdalc differ