Skip to content

build: judge stock enquiries by what is left, via @profullstack/form-guard (0.11.1) - #76

Merged
sh1pt-actions-fleet[bot] merged 1 commit into
mainfrom
build-form-quarantine
Oct 28, 2026
Merged

sh1pt-actions-fleet[bot] merged 1 commit into
mainfrom
build-form-quarantine

Conversation

@sh1pt-actions-fleet

Copy link
Copy Markdown
Contributor

Follow-up to #74 (INV-043/044 spam, 2026-10-28).

#74 dropped any /build/invoice idea that matched a stock-enquiry regex, so a real buyer who opens with "I have a few questions about pricing..." and then describes their app was silently bounced to /build with no invoice.

  • Uses the house package @profullstack/form-guard 0.3.0 (feat: substance() and the pricing/availability/process template (0.3.0) profullstack/form-guard#4, which learned this template and added substance()).
  • Spam = selling SEO/backlinks, or a stock enquiry with < 20 chars left after substance(). Spam still gets the honeypot answer: no pay.agent invoice, no builder email.
  • test/build-spam.test.ts: the INV-043 text and the consultation note are spam; the same text followed by a real idea is not; short real ideas are not. 196 pass, tsc clean.

🤖 Generated with Claude Code

…guard (0.11.1)

#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: 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