Previous plan/spec made honeypot a -5 weighted signal only. That is
insufficient to force 'spam' when the submission also has a RU phone
(+3), cyrillic name (+1), and meaningful text (+1) — a clean +5 cancels
-5, yielding 'unclear'. The honeypot test (test_honeypot_forces_spam_
even_with_phone) caught this.
Honeypot semantics: a filled hidden field is a bot by definition.
No combination of positive signals can make it a legitimate client.
Keeping the -5 weight on 'reasons' list for transparency, but adding
a hard override that sets label='spam' at the end of classify().
Caught by TDD on Task 7.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
- xn--80aafmakjldfe1b5h.xn--p1ai decodes to "алквзелчкоеиа.рф", not
"вашаняня.рф". Correct Punycode for "вашаняня.рф" is
xn--80aae0ca7d8bb.xn--p1ai. Updated plan Task 2 test and spec §9.
- DomainFormatter strip-path regex '#[/?#].*$#' had the '#' delimiter
colliding with the literal '#' inside the character class. Switched
to tilde delimiters: '~[/?#].*$~'.
Both caught by TDD RED/GREEN loop on Task 3.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
25 bite-sized TDD tasks covering composer/phpunit setup, pure-logic
classes (DomainFormatter, PhoneParser, Classifier, MessageFormatter)
with full test code, integration classes (Queue, Dispatcher, TelegramClient,
CF7Source, RetroImporter), admin UI, lifecycle hooks, and a manual
pilot on washanyanya.ru.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Vladimir Bryzgalov