Skip to content

build: no invoice for stock contact-form spam - #74

Merged
sh1pt-actions-fleet[bot] merged 1 commit into
mainfrom
fix/build-invoice-spam
Oct 28, 2026
Merged

sh1pt-actions-fleet[bot] merged 1 commit into
mainfrom
fix/build-invoice-spam

Conversation

@sh1pt-actions-fleet

Copy link
Copy Markdown
Contributor

Orders to /build/invoice whose idea is stock contact-form spam ("questions about pricing, availability, and the general process of working with you", etc.) get the honeypot answer: back to /build, no pay.agent invoice, no builder email. Triggered by INV-043/044 on 2026-10-28.

🤖 Generated with Claude Code

The 'questions about pricing, availability, and the general process' note
passed the honeypot and made two real pay.agent invoices (INV-043/044).
Orders whose idea matches known contact-form spam now go back to /build
with no invoice and no email, like a honeypot hit.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@sh1pt-actions-fleet
sh1pt-actions-fleet Bot merged commit c54e6be into main Oct 28, 2026
2 checks passed
@sh1pt-actions-fleet
sh1pt-actions-fleet Bot deleted the fix/build-invoice-spam branch October 28, 2026 22:39
sh1pt-actions-fleet Bot added a commit that referenced this pull request Oct 28, 2026
…guard (0.11.1) (#76)

#74 dropped any idea matching a stock-enquiry regex, so a real buyer who
opened with 'I have a few questions about pricing...' and then described an
app was silently sent back with no invoice. Now an order is spam only when
form-guard's substance() leaves nothing once the stock sentences and
pleasantries are removed (or it is selling SEO/backlinks).

Co-authored-by: Anthony Ettinger <anthony@profullstack.com>
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant