feat(reporting): require a reply-to email and a 200-char minimum on problem reports #183

Merged

JMR-dev merged 2 commits from feat-159-report-required-email into main

2026-07-03 00:20:15 +00:00

Author	SHA1	Message	Date
Jason Ross	2b38d06c6d	Merge main into feat-159-report-required-email	2026-07-02 19:09:01 -05:00
JMR-devandClaude Opus 4.8	2151bc6d7c	feat(reporting): require a reply-to email and a 200-char minimum on problem reports Adds friction to the "Report a Problem" form: a required email field (basic local-part@domain.tld validation), a required consent notice about being contacted at that address, and a 200-character minimum on the comment field with a live "x/200" counter that turns red (with the field outline) until the threshold is met. Submit stays disabled until both the comment and email are valid, mirroring and extending the existing SUBMITTING gate. The email rides along on DebugReport (userEmail) so it round-trips through the storage JSON and the exact payload that's previewed, copied, saved, and POSTed. The new ViewModel-level guard on submit() also fully integrates with the #161 success-confirmation dialog: invalid attempts never reach SUBMITTING/SUCCEEDED, so the dialog flow is unaffected. Closes #159 Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>	2026-07-02 18:52:21 -05:00

Author

SHA1

Message

Date

Jason Ross

2b38d06c6d

Merge main into feat-159-report-required-email

2026-07-02 19:09:01 -05:00

JMR-devandClaude Opus 4.8

2151bc6d7c

feat(reporting): require a reply-to email and a 200-char minimum on problem reports

Adds friction to the "Report a Problem" form: a required email field (basic
local-part@domain.tld validation), a required consent notice about being
contacted at that address, and a 200-character minimum on the comment field
with a live "x/200" counter that turns red (with the field outline) until the
threshold is met. Submit stays disabled until both the comment and email are
valid, mirroring and extending the existing SUBMITTING gate. The email rides
along on DebugReport (userEmail) so it round-trips through the storage JSON
and the exact payload that's previewed, copied, saved, and POSTed. The new
ViewModel-level guard on submit() also fully integrates with the #161
success-confirmation dialog: invalid attempts never reach SUBMITTING/SUCCEEDED,
so the dialog flow is unaffected.

Closes #159

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

2026-07-02 18:52:21 -05:00