#3789 flaky: for_each_name_property_test lets the text around a sentinel equal the secret's value, so the untyped value search replaces both and the property fails by seed

Problem

src/domain/workflows/for_each_name_property_test.ts, the property 'a sentinel and a recorded value of the same secret give the same name', generates the text before and after the sentinel and the secret value independently. When the surrounding text equals the secret value (fast-check found before='ply', secret='[REDACTED-SECRET-1]', after='', index=0) the typed path answers 'plysensitive-0' while the untyped path's value search replaces every occurrence and answers 'sensitive-0sensitive-0'. The property fails for that seed and passes otherwise, so verification runs fail at random.

Seen in a verify-build run on an unrelated change (swamp-club#3732, commit 30a85fc7752f5b6b99ba416c41e23319dfeeedba): seed -2136255155, counterexample ['ply','ply','',0]. Six local runs of the file pass.

Expected

The generator keeps the surrounding text from containing the secret value (filter the tuple, or draw the secret from an alphabet the plain text cannot produce), or the property states the untyped over-replacement explicitly. The over-replacement itself is the value search the typed-secrets design deletes at the release flip, so the fix belongs in the test.