How does the marketing page editor handle live forms via a token? [NEEDS YOUR INPUT]

This question concerns the public marketing website (lead-capture forms, demo requests, secure download flows) which is a separate surface from the core Okommerce platform and is not documented in the platform's system reference. The core CMS renders content pages, blocks, and lists; embedding *live, token-protected forms* on marketing pages (and the bot-prevention/token mechanics…

This question concerns the public marketing website (lead-capture forms, demo requests, secure download flows) which is a separate surface from the core Okommerce platform and is not documented in the platform's system reference. The core CMS renders content pages, blocks, and lists; embedding *live, token-protected forms* on marketing pages (and the bot-prevention/token mechanics behind them) belongs to the marketing-site project. To answer this accurately, supply how the marketing site implements form tokens (e.g. anti-bot token issued on page render, validated on submit) and I'll write it. Until then it's flagged rather than guessed.