USR369 direction 08/29/26, while doing Pec Fly: the way the 'Other' custom input works on Pec Fly is correct/desired behavior -- he wants this exact pattern used consistently throughout BOTH the Android app and the HTML page, everywhere a similar custom/other-style input exists. Called a major change. Not scoped in detail yet (which specific fields/exercises currently deviate from the Pec Fly pattern not yet inventoried) -- not started. Relates to K384's existing custom-value-dropdown standards ask (already filed as T-CUSTOMVAL-STD per msg 1095, still open, not yet built) -- this may be the same underlying request restated with a concrete reference example (Pec Fly) rather than a duplicate. Worth reconciling with T-CUSTOMVAL-STD rather than treating as brand new before building anything.