orbit_compose_stripo_email — autogenerated Stripo emailName drops to a date stamp, no more ISO-timestamp tail
Small but user-visible cleanup to how orbit_compose_stripo_email labels pushed emails in Stripo when you haven't supplied an email_name override. The auto-name used to read Orbit · <subject> · 2026-05-22T02-16-18-620Z — a full ISO timestamp with colons swapped for hyphens, useful for sub-second collision avoidance but unreadable in the Stripo email list. It now reads Orbit · <subject> · 2026-05-22. Scannable in the workspace, still distinguishable across days, and aligns with how program-variant labels (Welcome - Paid, M2 Phone Divert A - Starter) read in the same list. Scope is strictly the user-facing emailName written to Stripo — local workspace HTML filenames and the diagnostic probe scripts keep their full timestamps because the collision-avoidance reasoning still applies on disk. The email_name override parameter is unchanged, so callers passing program-variant names continue to land them verbatim.
What shipped
•Behaviour change — orbit_compose_stripo_email's autogenerated emailName now uses a YYYY-MM-DD date stamp instead of a full ISO timestamp. Before: Orbit · subject · 2026-05-22T02-16-18-620Z. After: Orbit · subject · 2026-05-22. The Stripo email list is the surface this affects — anyone reading down their list of pushed emails now sees a date they can parse at a glance instead of a 24-character timestamp tail. Heads-up if you'd built a Stripo Saved Filter or external script that pattern-matches on the old T..Z suffix: those will stop matching from this version forward.
•Unchanged — the email_name override parameter still wins when supplied and is still written to Stripo verbatim (minus the defensive square-bracket strip). Anyone already passing program-variant labels like email_name: "Welcome - Paid" sees no difference. The date-stamp change is purely the no-override default path.
•Unchanged — local workspace HTML filenames and the Stripo probe scripts keep their full ISO timestamps. The reasoning splits cleanly: on disk, multiple composes in the same minute need to not collide, so the millisecond precision earns its keep; in Stripo's UI, that precision was just noise.