Build a newsletter system on Rails

Build a newsletter system as a brand-new Ruby on Rails application, with Avo 4 (https://avohq.io, docs at https://docs.avohq.io/4.0/) as the management UI. There is no existing app or schema to work from, so this scaffolds the whole thing. Delivery runs on Action Mailer inside this new app.

1. Run rails new with sensible defaults to create the app. Generate authentication with Rails' built-in authentication generator so there is a real login before anything else exists. Add the avo gem, bundle, run bin/rails generate avo:install, and mount Avo at /avo so the generated authentication guards it.
2. Design the data model from first principles rather than copying a fixed schema. Think through what running a list genuinely requires: who the people on the list are and the consent state that governs whether you may mail them, how those people get grouped so a send can target a slice of them, and the issues that get composed, scheduled, and dispatched. Decide which states belong in an enum on a record (a subscriber being subscribed, unsubscribed, or bounced; a campaign moving through draft, scheduled, sending, and sent) and which deserve their own table, and work out the associations between them. A campaign needs somewhere to record how many people it targeted and how many actually received it. Write down the entities, their states, and their relationships, then generate the migrations to match.
3. Generate an Avo resource for each model with bin/rails generate avo:resource (https://docs.avohq.io/4.0/resources.html). On the campaign resource, point self.title at the subject line, list the grouping association in self.includes so the index does not run N+1 queries, and match fields to the columns you created: a trix field for the body, a badge over the lifecycle status, a belongs_to to the group it targets, a date_time for the scheduled send, and number fields on the Show view for the targeted and delivered counts. On the subscriber resource, set self.search over name and email and put a badge on the consent status so the list reads at a glance.
4. Because this app is new, the delivery machinery does not exist yet, so build it: an Action Mailer mailer for a campaign, and a background job that batches and throttles the send, updates the delivered count as it goes, and honors suppressed addresses. Wire the verbs of running a list as Avo Actions (https://docs.avohq.io/4.0/actions.html) that call into that code: one that dispatches a campaign to its group, and one that sends a test copy to the signed-in user before a real send.
5. Add filters and scopes so the subscriber list can be narrowed to a group with no recent bounce, and the campaign list to what is still in draft versus already sent. Build an Avo dashboard (https://docs.avohq.io/4.0/dashboards.html) with metric cards for list size, subscribers gained recently, and campaigns sent, so the health of the list is visible on landing. Add an endpoint that receives your email provider's webhooks and flips a subscriber to unsubscribed or bounced, and surface that as filterable state on the resource.
6. Add Pundit authorization (https://docs.avohq.io/4.0/authorization.html) with two roles: an admin who can do everything, and an editor who can compose and schedule campaigns but cannot delete subscribers or export the list.
7. Seed the database with believable sample data: a few hundred subscribers spread across a couple of groups and consent states, and a handful of campaigns in different lifecycle stages, so every resource, filter, and dashboard card has something real to render.
8. Boot the app, sign in, open /avo, compose a short campaign, and send a test copy to yourself to confirm the mailer, the job, and the delivered count all move.