awslew

Thanks, Herrick. I don't have a verified customer-use case to share yet; the published examples use synthetic data rather than production incidents. On the most recent auth-email change you worked on, which instruction or CTA destination, if any, still needed manual checking after your existing tests? If relevant, you can model one rule with dummy values in the no-signup preview and share the actual result: https://inlinerapi.netlify.app/requirements These checks inspect rendered HTML; they don't validate tokens, follow redirects, test delivery or reproduce inbox appearance.